> Group projects were also a common complaint. You were randomly assigned a group, but it was often unclear if the participants were even doing the course - many people were in completely ghost groups.
I see that nothing has changed in 20 years. Even when attended the courses physically in person, group project usually had 1 or 2 people doing all the work and the rest nowhere to be found, or just hanging out. :p
The syntax looks like rust, but esp w/the memory management model (reference counting), it’s going to have more overhead than rust when it’s running, more like Swift or at worse, Python.
> waiting for an animation to complete before the app will start acknowledging my keystrokes.
Or you find out you can input as the animation happens, but when the animation finishes, you’ve lost where your input ended up and don’t know if you can backspace/delete and retype.
Just reporting what I’ve experienced. No need to go with the ad hominem attack. I happen to lead a team with a major Rust infra project and I stand by the experience with usage across all the LLM models.
1. Amount of Rust training data isn’t as much as Go.
2. Golang syntax and style is very verbose yet simple. There’s not as many options nor programming language to domain mapping needed as in Rust. Leads to needing less sophisticated LLM to spit out Golang than Rust successfully and efficiently.
As a Costco member and customer, I’d actually trust the leadership more than most companies. Use the tariff money and keep that $1.50 hotdog ~ enough avg Americans can use that break for lunch, even if not the healthiest.
https://benson-guides.blogspot.com/
fung [dot] benson [at] gmail [dot] com