vasametropolis
Apparently, the Zuck fucks
The design is still horrendous. I was hoping for a total do over.
To be fair, there’s huge demand for a Swift-like language in the space Go operates, since nobody will ever adopt Swift outside of Apple use cases. Rust is excellent, but garbage collection is not awful at all for most Go use cases. I think Go designers made a mistake by not introducing sum types sooner since there are many ergonomic issues that could be solved with them.
This may lead people to argue for JVM-based languages, but Go seems like a leaner and nicer package overall and compiling to static binaries so simply is still a major winning feature. That and I think Go still has performance advantages over JVM and C#.
In many ways I think Swift is better than Go as a language, but we effectively will never have that as an option people freely choose to use so it would be nice for Go to close some ground where it can and where it makes sense to do so. Go is what people already want to use as a starting point, so it makes sense for it to try and modernize a tad.
This is the perspective that is totally forgotten and missed by most engaging in the discussion. Not to diminish Larian’s achievement, but they literally busted out the old playbook. Credit where it’s due, but BG3 shouldn’t be controversial - it should be the standard because that’s what the standard used to be.
I wouldn’t undercut yourself so much - they have more experience but every situation is different. Inflation in July was largely due to increased mortgage payments (2.4% if you exclude mortgage increases from rate increases). So when the only knob they have can also cause a bigger issue, it’s fair to criticize that they are just going with the flow and praying. If you jump from 0.25 to 5 in such a short time frame, you just worsened inflation on mortgages while improving everything else to the point where it might all cancel out.
They are absolutely flying by the seat of their pants and throwing the average worker under the bus.