3 ms·
I think you're incorrect. It's good for the motivated engineer, because instead of running off and creating architecture astronautical wonders of over-engineer
by lelanthran 3y ago
I think you're incorrect.
It's good for the motivated engineer, because instead of running off and creating architecture astronautical wonders of over-engineering, they are getting down to business and making progress to a goal.
Your bottom-tier engineers aren't going to be any better in Go than they are going to be in Java.
- kaba0 3y agoCopy pasting code definitely helps you grow as an engineer.. also, the more often you write err != nil, the better the code will be, right?
- lelanthran 3y agoI didn't assert either of those things.
- bsaul 3y agoGenerics , although kept simple, definitely reduced the amount of copy pasting in go. I actually think go generic’s system is the best i’ve seen because they managed to provide enough features to remove the stupid parts of the language, while not changing the general feeling and encourage devs to build abstraction monsters.
- littlestymaar 3y ago> instead of running off and creating architecture astronautical wonders of over-engineering Maybe in theory, in practice you get people writing their own implementation of generics with codegen and Canadian aboriginal syllabics…
- philosopher1234 3y agoDid that happen more than once?
- littlestymaar 3y agoThat particular example of course no, but people writing overengineered beasts to overcome go's limitation happens all the time. Another famous example is how k8s, dealt with the lack of generics: https://medium.com/@arschles/go-experience-report-generics-in-kubernetes-25da87430301 https://medium.com/@arschles/go-experience-report-generics-i...
- lelanthran 3y ago> That particular example of course no, but people writing overengineered beasts to overcome go's limitation happens all the time. "happens"??? Yeah, it happened all the time, but for the last 14 months or so Go has had a serviceable implementation[1] of generics. So, sure, you could argue that projects used to implement hacky workarounds for generics, but that argument gets less relevant as time goes on. That argument is irrelevant to anyone starting a project today in Go. Probably also irrelevant to the type of microservices projects that I mostly see in Go, because any hack workaround can be replaced gradually by the language generics. [1] Unless you are referring to some deficiency of the generics implementation in Go that I am ignorant of.
- littlestymaar 3y agoGenerics is just one famous example, but go is so opinionated about everything, that there are countless others, from error handling to package management or concurrency primitives. It turns out that if you refuse to give the users things you think are heretical, the users will walk around your arbitrary limitations, and the result will just be worse for everyone.
- lelanthran 3y ago> It turns out that if you refuse to give the users things you think are heretical, the users will walk around your arbitrary limitations, and the result will just be worse for everyone You are correct, no "but..." qualifier. It's a trade-off, and the language curators have to balance the frequncy of user's hacks against cognitive load for all users. You have to draw the line somewhere when adding language features and it is totally reasonable for a language that advertises itself as a low cognitive-load language to limit itself to a subset of features that useful for it's target users and ignore the rest of PL features. Just compare how awful it is in other languages to start an async routine and read it's results when it is complete, to go where you just read a channel you passed to the routine. That single thing alone shows that Go's creators want to deliver stuff to users who value producing solutions over language lawyering. Whatever you can do for almost all programs written in C++ or Rust will be more readable in Go with little noticeable performance degradation.
- c_crank 3y agoA walled garden prevents you from doing a lot of things, not just over architecting. It inhibits the top tier engineers as much as the bottom tier ones.
- lelanthran 3y ago> A walled garden prevents you from doing a lot of things, not just over architecting. It inhibits the top tier engineers as much as the bottom tier ones. Up to a point, depending on the limitation. After all, writing raw assembly removes almost all limitations and yet people still argue for introducing limitations in higher level languages. Static typing is a limitation, and yet more people argue for it than against it. Structured control is a limitation, and yet people prefer that to raw `goto`s. Lack raw memory access is a limitation, and yet people argue against raw memory access in favour of alternatives (such as byte arrays). Top-tier engineers don't feel constrained by static typing, structured program controls, raw memory access or any one of the multitudes of limitations that popular languages define as their "walled garden". There's no clear line marking the boundary between a constraint that is helpful and one that is not. It's more of a gradual spectrum with assembly on one side and Lisp on the other, and all other languages somewhere in between. I'm largely in agreement that a language that prevents the programmer doing stupid things also prevents them doing clever things, but I feel that certain particular limitations improve the maintainability and readability of code. Those languages that have a kitchen-sink approach to features are notoriously for being difficult to maintain. Most large C++ projects, for example, literally have a defined subset of C++ that they will approve in PRs, and they are still considered difficult to maintain. IMHO (really emphasising the "humble" in that acronym), and as someone who's playing around designing a language (again!), a good language these days should be defined by what it doesn't let you do, not what it lets you do. Lets you pick one of three different ways to declare a function? Bad Language! No cookie for you A function declaration always looks the same no matter where it appears? Good! That's a limitation I actually want!
- c_crank 3y agoWhat you're getting at is the presence and lack of features leads to an idiomatic version of how one should code in a language. Go has very few features, leading to one obvious way to code. Python has some well implemented features and a lot of clunky and badly implemented ones, leading to the same pressure for one way to code. C++ has far too many that overlap in confusing ways, leading to no clear way to code. The thing about Java is that idiomatic Java should be like the Java standard library, instead of being like J2EE and Spring Boot.