Yep having enums like Rust, which are actually discriminated unions known from functional languages, would have made it obviously better. Since this includes Option and Result types, it is directly connected to proper null and error handing too. Go decided to do everything with just tuples, which are a lot less practical for this purpose. However I still think it a far better approach than the exceptions and try catch system that most older programming languages have.
I wish go have some feature from zig then it will be the best. enum is one, error handling is another one which I think zig done well. tag union also something I miss on go.
Coming many years of C# and far more, but especially after diving deep into Rust for a long time, I now also decided to explore Go and I must say I like it far more than I have ever thought. I literally just explored it this week. The Duck Typing approach with interfaces is also really interesting. 🦆 The simplicity is actually great. And let's all just agree that classic OOP was not the best invention by humanity. Although both languages have different approaches in how they handle things, both Go and Rust evolved around the same period and both have looked for interesting approaches of doing things in new ways.
@@silaspy-ff2ne Apparently we cannot generalize devs based on their programming languages. 🙃 But apart from that I have always used several languages so I have seen quite a lot actually. It may be good to note however that C# has not been just typical object oriented design exclusively. It has always been adding lots of functional and composition oriented stuff. Just think about linq, lamba expressions and extension methods.
They have favored a little copy paste over letting people waste time in too complicated abstraction. And it was hard to find a way that didn't slow down the compiler or runtime, while fitting in with the rest of the language
It's going to be so amazing when people quit saying dumb sh1t like gigachad or based. We used to use real words and not all talk like ignorant teenage girls.
What the go team absolutely got wrong is the date format reference layout, I mean what the heck. That said, go has everything to get the job done and it's not feature bloated.
@silaspy-ff2ne rust more readable than c++ only if you already have 3 years experience 😂 But I do agree that Zig is verbose. Complex zig code can be very messy with most files having 100 lines at the top dedicated to import and redeclaring stuff to shorter names.😢
@@MelkeyDev haha i don't know man, coming from node js, i think 'standard' library. and i pick if i should pick one, it's net/http, and man the update just fits my needs, slowly cure my addiction to library and framework😂
If you are referring to dotnet, it’s a good example of feature bloat that newer languages would prefer to avoid. For every modern feature, there are at least four that should effectively be deprecated. If they weren’t still in use in everything from .Net Framework 2.0 forward.
Despite Golang being Turing complete, personally to me it looks like a rather web framework - very fast and optioned, and very well in its area, but still filled with flaws like weak type system, lack of expressiveness so on - which do not allow the Go to be indeed simple and great _language_. IMO, of course.
@@MosiurRahman-dl5ts var num int; _, err := fmt.Scanln(num) // should be &num, we'll have a runtime error, not a compile-time error; if you consider this a strong type system, then ok
@@MosiurRahman-dl5ts var num int; _, err := fmt.Scanln(num) // should be &num, we'll have a runtime error, not a compile-time error; if you consider this a strong type system, then ok - As to your question "Have you ever completed any Go projects?" - unfortunately no. Would like to, and I took several training courses, read some books, solved a hundred or two drills, and wrote some web APIs. But after previous experience in JS/TS, Python, Dart, and PHP (and a bit of Rust now) I wasn't able to overcome myself and begin to write in Go due to all its... Let's just say, due to Go's "fancy" language design in literally every aspect.
@@MosiurRahman-dl5ts man, you need to back up your words with facts. Golang is strongly typed ( in the strictness sense), but does not have a *strong* type system. It's based on structural typing (similar to typescript, but stricter). For me a strong type system refers to a type systems with more capabilities rather than being strict, like all strongly typed languages. For instance, other type systems allow tagged union types ( or other ADTs) or allow inference, or pattern match on types. Having the empty interface as a type is the opposite of strong
Hope you all enjoyed the video. Make sure to hit subscribe - so close to 20k. Let me know what videos you guys wanna see next!
it was a mistake not to have proper enums :'(
nil is also a problem. It's not awful, but it's not great either. Sadly the same can be said for most languages.
Yep having enums like Rust, which are actually discriminated unions known from functional languages, would have made it obviously better.
Since this includes Option and Result types, it is directly connected to proper null and error handing too.
Go decided to do everything with just tuples, which are a lot less practical for this purpose.
However I still think it a far better approach than the exceptions and try catch system that most older programming languages have.
enums and pattern matching
I wish go have some feature from zig then it will be the best. enum is one, error handling is another one which I think zig done well. tag union also something I miss on go.
@@sgwong513yop, but I still love go
Coming many years of C# and far more, but especially after diving deep into Rust for a long time, I now also decided to explore Go and I must say I like it far more than I have ever thought. I literally just explored it this week.
The Duck Typing approach with interfaces is also really interesting. 🦆
The simplicity is actually great. And let's all just agree that classic OOP was not the best invention by humanity.
Although both languages have different approaches in how they handle things, both Go and Rust evolved around the same period and both have looked for interesting approaches of doing things in new ways.
@@silaspy-ff2ne Apparently we cannot generalize devs based on their programming languages. 🙃
But apart from that I have always used several languages so I have seen quite a lot actually.
It may be good to note however that C# has not been just typical object oriented design exclusively. It has always been adding lots of functional and composition oriented stuff. Just think about linq, lamba expressions and extension methods.
Is there a reason for Go not having generics until pretty recently? That seems to be why it doesn't have a lot of built in data structures I guess.
They have favored a little copy paste over letting people waste time in too complicated abstraction. And it was hard to find a way that didn't slow down the compiler or runtime, while fitting in with the rest of the language
The Go mascot may be goofy but I havent seen one Go coder that wasnt a gigachad
thanks
It's going to be so amazing when people quit saying dumb sh1t like gigachad or based. We used to use real words and not all talk like ignorant teenage girls.
Hey
I'm not sure what u mean by proper enums. Can u explain?
I enjoyed the video a lot. I would love seeing such summary content. I loved your minimalist and simple explanation.
I will make more like this then :)
Thank you.
I don't understand Go nor English.
But I watched the whole video anyway.
Good thing you know enough English to comment
What language do you speak?
Indonesia @@Soulis98
I learn programming @throwaway6008
Rob is such a GOD-level programmer
Well worth watching the original presentation by Rob.
Couldnt agree more! His talks are the best
Where did u get those gopher plushies in the background?
When you get recognised by the Golang elites they mail you them
This is such a nice video
Nice!
Language features aside, let’s be serious for a minute: that’s a goddamn outstanding jacket
He actually rocks it LOL
great vid melkey
Thank you Parrot!
What the go team absolutely got wrong is the date format reference layout, I mean what the heck. That said, go has everything to get the job done and it's not feature bloated.
Jan -> 1 -> Month
2 -> 2 -> Day-of-Month
15 = 3PM -> 15/3 -> hour
04 -> 4 -> minute
05 -> 5 -> second
2006 -> 6 -> year
-0700 -> 7 -> time-zone
@@Yoshidzo Thanks, I hate it.
it aint perfect!
Go being built with Ken Thompson and Rob Pike is like having the gods writing any language.
They should build a JS and Rust replacement :P
What you're seeking for might be HTMX (reduce drastically client-side JS) and Zig ("simpler" system language than Rust)
@silaspy-ff2ne
rust more readable than c++ only if you already have 3 years experience 😂
But I do agree that Zig is verbose. Complex zig code can be very messy with most files having 100 lines at the top dedicated to import and redeclaring stuff to shorter names.😢
Go watch the original talk, it's great.
give it a GO!! now pick one of your favorite "feature" of go. just one.
Which one is your favorite
@@MelkeyDev haha i don't know man, coming from node js, i think 'standard' library. and i pick if i should pick one, it's net/http, and man the update just fits my needs, slowly cure my addiction to library and framework😂
Only if golang could be able to be used to create android apps
Is purposeful Go have no OOP?
Go has the good part of OOP: structs with methods bound to them, everything else is not realy needed
It has methods and interfaces, those are the good things about OOP. If you desire inheritance, you should reconsider.
Man, I'd like Go if it had a better type system.
what's wrong with it?
I think that's the very best typing system I've used in my life, personally
Go's STD is anemic compared to C# and I really like go. You have to compare to the best std not the laguages that bearly have any (Rust, JS/TS)
If you are referring to dotnet, it’s a good example of feature bloat that newer languages would prefer to avoid. For every modern feature, there are at least four that should effectively be deprecated. If they weren’t still in use in everything from .Net Framework 2.0 forward.
The standard lib in Go is the best in my opinion
“less skillful people out there” lol. i love go but this statement can be improved
LOL OOPS
The bone-cracking transition sound effects need to stop.
You dont like it?
Despite Golang being Turing complete, personally to me it looks like a rather web framework - very fast and optioned, and very well in its area, but still filled with flaws like weak type system, lack of expressiveness so on - which do not allow the Go to be indeed simple and great _language_. IMO, of course.
i use it for integrating few systems, network stuff, i have no idea what are you talking about.
Have you ever completed any Go projects?
Cause all I see here is misinformation (go actually have strong type system) and skill issue.
@@MosiurRahman-dl5ts var num int; _, err := fmt.Scanln(num) // should be &num, we'll have a runtime error, not a compile-time error; if you consider this a strong type system, then ok
@@MosiurRahman-dl5ts var num int; _, err := fmt.Scanln(num) // should be &num, we'll have a runtime error, not a compile-time error; if you consider this a strong type system, then ok
- As to your question "Have you ever completed any Go projects?" - unfortunately no. Would like to, and I took several training courses, read some books, solved a hundred or two drills, and wrote some web APIs. But after previous experience in JS/TS, Python, Dart, and PHP (and a bit of Rust now) I wasn't able to overcome myself and begin to write in Go due to all its... Let's just say, due to Go's "fancy" language design in literally every aspect.
@@MosiurRahman-dl5ts man, you need to back up your words with facts. Golang is strongly typed ( in the strictness sense), but does not have a *strong* type system. It's based on structural typing (similar to typescript, but stricter). For me a strong type system refers to a type systems with more capabilities rather than being strict, like all strongly typed languages. For instance, other type systems allow tagged union types ( or other ADTs) or allow inference, or pattern match on types. Having the empty interface as a type is the opposite of strong