> AI, I asked you to check the docs for the latest version of the API, yet you didn't. Why?
> You are completely right! That was my miss, I have no excuse. I've now looked at the docs and implemented it.
Now imagine how triggered you'd be when the AI decides to get you a vegan burger because the chicken wrap is on the second page and it know you're a health conscious person.
Why? Their justification seems reasonable to me. If other teams depend on your enum then you could end up in two really bad cases. First is that you end up having to fix a ton of code just to update your enum, which has it's own headaches. Second is another team's build starts to fail when they update dependencies. Horrible churn to cause for your org. Better to just have them design around non_exhaustive.
> you could end up in two really bad cases. First is that you end up having to fix a ton of code just to update your enum, which has it's own headaches. Second is another team's build starts to fail when they update dependencies
If you really don’t care about compiler warnings, what’s the actual point of using Rust?
The first one is not a "really bad case", but the intention of having a strict enum. You want to be force to update, in order to not miss any places, where the change could cause an error. That's the very benefit of it.
Second case is the same. The other team needs to definitely know, that their assumptions expressed in their current code are broken and need to be adjusted.
We just need to stop to take whatever shit Google is doing as the one bar to measure all others, and need to understand that they may be different requirements than a typical business. We are not Google.
Those are horrible cases if you're anything more than a hobbyist.
I don't want to update every place someone matches on my enum, when it's something not even in my project, just to get my PR to merge. Three teams use it? Fine. Ten? More? Not fine. You are adding cases into someone else's code just to unblock your own work.
The second case is actually not the same at all. Realistically, they will just pin your dependency to an older version. Now they can't benefit from new features and security fixes without going in and adding in a new case. Massive waste of time for them.
And of course I'm not just taking whatever Google says at face value. I read their justification, and it makes total sense for anyone that works on a non-trivial project. It follows how any stable public API is supposed to be designed.
> I don't want to update every place someone matches on my enum, when it's something not even in my project, just to get my PR to merge. Three teams use it? Fine. Ten? More? Not fine. You are adding cases into someone else's code just to unblock your own work.
Then don't upgrade your dependency onto the other crate.
Anything more than a hobbyist will have properly pinned versions, and not just sling around version ranges loosely. At the very least will not update lock file just like that, without considering, that there may be consequences.
A wheelchair is also a tool! A very efficient one too! People claim they've 2x'd their energy efficiency by not ever walking or standing, and they are much more happy now that they don't need to suffer the pain of walking! I'm thinking of amputating my feet just to make footoids seethe more!
A car is exactly what you describe, and even the fitness nuts use them.
It is actually a great example. Slobs use them just to avoid a 5 minute walk, even though walking is cheaper and faster. Reasonable people will take their into account their time, money, health and circumstances to choose whether to walk or to drive. And some crazies think cars are evil and will walk for hours and put themselves in danger instead of driving.
Same idea with AI. One one side, some people will turn off their brain and let the AI take control, on the other side, others will spend hours searching what a simple prompt can get them in seconds. Reasonable people are in the middle.
Yeah it was Anthropic. I actually opened the article, which I almost never do, to see which company's chat bot it was. This is one of the reasons I don't use them. They are obviously spying on their users.
I've always been more afraid of these types of models than LLMs. These are what enable mass surveillance at scale and autonomous real time combat drones. Now they are spreading and being optimized. Gg.
Lol this feels trite to say, but tech bros are not ideologically homogenous. You and the author are mixing up different people commonly identified as tech bros.
The stigma is pure cope. Most nerdy types I know wasted a ton of time on some stupid hobby. If not video games, it was some other dumb geek thing like anime, comic books, or furries.
reply