I probably wouldn’t describe them as flawed, because the goal wasn’t and couldn’t ever be perfection, so then everything is flawed, but then is it really a flaw? It sounds like more of an issue of what’s useful in what type of situation.
I probably wouldn’t describe them as flawed, because the goal wasn’t and couldn’t ever be perfection, so then everything is flawed, but then is it really a flaw? It sounds like more of an issue of what’s useful in what type of situation.
You’re talking about the wrong thing. The Mozilla Foundation is and has been acting a fool in recent years. Firefox, the open source program, is doing mostly OK. Obviously the two are closely connected, but they’re definitely not the same thing, and this matters when discussing policy.
Now now. If Mozilla is breaking the law here, of course someone would report them for it. There’s no need to shoot the messenger when everything was predictable.
I appreciate your apprehension. Fortunately, you don’t need to speculate. Go try it and find out.
Lots of options available. YT is slowly cracking down on them. That’s OK, just keep your medium run media consumption plans flexible.
The point is that the post title was false (or intentionally very misleading, if you insist on creatively parsing it). Accuracy in post titles is important.
I’m not a professional code monkey although I’ve done a fair amount of coding, and every time I tried to do parsing myself, I later regretted it.
But telling people that they’re doing it wrong is rarely met with positivity. :-)
I think there’s an element of responsibility that some people feel when they respond. If you’re asking for a very niche solution that is likely to create other problems in the future, should anyone else look at your code or refactor it or rely on it, or should you forget how it works, perhaps people are going to be less inclined in helping you craft it.
If you still want to craft it, that’s okay, but you have to expect that some real percent of the answers are going to be those folk who know what the tried and true solution is, often because they’ve lived through the reality that you’re attempting to create and they’ve dealt with the aftermath of doing it special and different.
It’s not a question of what’s the better option. In reality we have a lot of software that already exists and works, and you can’t replace it all in bulk at the same time. So the question is whether the implementation of Rust makes logistical sense, given the difficulties of maintaining currently existing software while replacing some parts of it.
No seeds no stems no stress my guy. The Internet is a great place for complaining. Readers can downvote and move on, everyone gets what they want.
This one is very obvious. It’s not specific to the tech world. Companies know that changing jobs is stressful, that there’s value in remaining where you are, and quite obviously many people are willing to accept smaller raises so that they don’t have to go out and apply. For most jobs in the world, you can’t work remotely, and renting a different place or selling and buying property is time consuming, stressful, and expensive. In other words, this is common sense economic reasoning.
One side point is that if you can work mostly or entirely from home, that gets rid of some of the pressure to stay where you are, which in turn should create more mobility, which in turn should create more pay raises for employees who stay. But work from home is relatively the recent phenomenon, so old company pay scales are unlikely to properly account for it.
Another point, that the author completely overlooks, is that some people don’t contribute as much as the author thinks they contribute. If they know that, of course they don’t want to move to a place that does contribution-based pay. They could get hired on somewhere during a probational period of some kind, and their new bosses might think they’re not good enough, and now they are out two jobs. Of course the turnover on their second job makes their resume look weaker, so they’ll have more trouble finding a decent third job.
None of what I wrote is new information. It seems like the author of the article did that standard thing in tech circles. They decided to reinvent the wheel and write about it, and try to make it exciting when it’s not. Good for them for examining the problem, but they should be slightly embarrassed for publishing before doing basic research to see if someone had already addressed the question at hand.
The garbage is taking itself out
CS often requires working in teams, and working it teams is often more efficient if you have some shared approaches.
I think we should be precise. The badness began before generative AI. Generative AI makes things worse because now you are less sure when you’re looking at total junk, but the junk ratio itself doesn’t depend on that.
What you talking about as apathy, that’s not what’s happening. Google has 90% or more of the search market because it’s the default, because it pays to be the default, even when it’s worse than alternatives. The only people who are actually apathetic are the ones who know that alternative exist, are relatively easy to switch to, are superior, and still don’t. That’s not the majority of users.
In C you can do almost anything, including things that will fry the system. In Rust, it’s a lot harder to do that. (This makes sense if you consider when the languages were made and what were made for. It’s not an attack on or praise for either language.)
It’s unclear that AI is the right tool at all. It’s certainly possible to use some automated conversion libraries, and then have human programmers fill in the gaps.
I think that’s a matter of perspective. IMO it didn’t work, it was broken, that’s why we’re even talking about it.
Nope, sorry. That technical hurdle is easily solved. In reality, this is about advertising and snooping.
Capitalists hate capitalism. Competition is so irritating, because someone might undercut you. (And other people would cheat to win, just like you would, so you can’t ever relax.)