What is a practical use case where the lower precedence makes sense?
523 karma · joined October 25, 2019
What is a practical use case where the lower precedence makes sense?
This is a really weird take, considering Valve's push into Linux.
Not sure if you intended this to be this philosophical, but this is basically the slogan for modern life now.
At a web agency I used to work at this was definitely a thing we had to teach the juniors. Whatever you built now is going to end up in maintenance with a support team that doesn't have as deep of an understanding of the project. Being overly clever now is going to be a pain in the ass later.
"Keep It Simple, Stupid" is an important skill for a professional.
Yes, that is the rational thing to do. I don't think anybody disagrees with that. But that's not how a lot of people go throughout their day. There are a gazillion languages to pick up nowadays, and I think many experienced devs only have a casual interest in picking up a new one. If you've been interested in picking up a system language, I can easily see why you would steer away from Rust towards Zig.
And just to clarify here. You shouldn't judge an entire community based on their toxic minority. But as a community, you can't also ignore your toxic minority. Like it or not, they do represent you. And they do scare away potential newcomers who aren't already sold on the language.
You can make the case that if something like this turns you off from diving deeper into the language you probably weren't that motivated to begin with. But it is a noticable effect. This post isn't the first time I see it either. Rust has become a meme amongst my colleagues because things keep popping up with "Build with Rust" before mentioning anything of substance of the project. The phrase "Did you know Rust is memory safe?" is also a running joke in my IRL dev surroundings now.
Looking at my own country. There are multiple big companies with a "founder-mode" CEO that is a massive prick and wants to be a dictator.
I feel like having the US president try to run their entire country this way is also validating a lot of those CEO types.
Keep in mind. Learning a language usually also means you interact with the people in the ecosystem at some point.
But Rails was SSR by default, and most of the frontend was just Embedded Ruby (ERB) template files all over the place. And way back when, it was even relatively common to use Javascript supersets like CoffeeScript[1] and Opal[2]. The latter being Ruby that compiled to JS.
[1]: https://coffeescript.org/ [2]: https://opalrb.com/
As for your second point. A friend of mine's little sister asked him for help setting up the vintage camera she bought. And it was an early 00s digital point & shoot.
And contractually, any code I made was my employer's if I made it during office hours. Some even made a claim for code I would've written that during my employ that would be "competitive". Luckily, there was a massive difference in what I would do in my own time versus what they did.
Fun is desirable.
It doesn't sound that surprising, does it?
If I had to spend 650k on a single car, I wouldn't buy this.
If the dashboard was set up for a normal person and I could see this be a great sedan. But as it stands, it just seems horribly out of touch.
For all the issues people claim to have with iOS or Android, they really "just work" compared to the shit we had to deal with back in the day. And I don't even mean bugs, but UX just wasn't as sleek.
I can find a pdf of the TTRPG I'm playing that's hidden deep in an iCloud drive by simply opening spotlight an typing the approximate name. And the same works on my iPhone. Apps that create documents for me hide their file structure, because it's all abstracted away from me. It works, and I don't have to think about it as much.
You still have kids that start fiddling with tech, but only out of clear interest. Not as a necessity.