531–540 of 869 posts
Earlier quoted context omitted.
Isn't this a sign of a problem ? where important domains with hard problems pay few .. while some dubious applications are throwing money on css plumbers ?
It's a sign that people inherently want to work on those hard problems.
Earlier quoted context omitted.
> No one is paying the implementers of those languages Lol what? Yes they are. I literally work with a whole team of them! Teams at Goole, Apple, Mozilla, etc etc as well.
https://discuss.python.org/t/official-list-of-core-developer... >In my latest talk, I computed that we have 2 developers paid at full time to maintain Python: I am full time, Barry, Brett, Eric, Steve and Guido have 1 day per week if I understood correctly. Now from what I understand situation is way better, but still - that's what it looked like just three years ago, when Python already had millions of people writin…
Earlier quoted context omitted.
Isn't this a sign of a problem ? where important domains with hard problems pay few .. while some dubious applications are throwing money on css plumbers ?
There's a strike happening here in Ontario schools by janitors and education assistants and early childhood educators, because they want more than a 2% raise on their $40-$50k year jobs ($30k USD, and look at inflation #s...). The government is going to use a special "shouldn't be used" clause in the Canadian charter or rights and freedoms to force a contract on them and ban a strike and forbid collective bargaining…
Earlier quoted context omitted.
As someone who has been writing C++ at Google, this exactly. Despite all the tooling, guidelines and "internal magic", C++ is still an abomination. And no it has nothing to do with memory management, I actually do like C. I love how Eric Raymond describes it as "anti-compact", because, well, it really is. C++ as a whole should be deprecated -- and no new projects should use C++ (unless for some very odd and specific…
> C++ as a whole should be deprecated -- and no new projects should use C++ (unless for some very odd and specific reason). It's quite a bit easier than Rust and no other popular language has its most important features (cross platform, interfaces with syscalls and other libraries easily, manual memory management possible, likely to be supported for a long time).
Earlier quoted context omitted.
No one is paying the implementers of those languages
> No one is paying the implementers of those languages Lol what? Yes they are. I literally work with a whole team of them! Teams at Goole, Apple, Mozilla, etc etc as well.
Earlier quoted context omitted.
Interesting; could this be because you've been using outdated C++ ? (legacy codebases started before C++98 tend to be particularly painful) FWIW, I prefer the power of C++ over Rust's hand-holding; but can also see its appeal for someone that's not as confident over the minutia.
Not the person you asked, but for me (coming from C++20, with lambdas, async, etc), the big win is that the borrow checker automates away boring PR comments about "you used std::unique_ptr in a non-idiomatic way that is technically safe, and it bleeds memory unsafety into some random API, so write this level N+1 magic instead". It also checks that all my threaded code is data race free. On the downside, it's support…
Earlier quoted context omitted.
> labor shortages that salary can't solve. Some positions are simply not economically viable in certain markets Your two sentences are opposite of each other? If someone can't afford to pay employees market rate, they need to rethink viability of the business not say that they can't find someone.
> If someone can't afford to pay employees market rate, they need to rethink viability of the business not say that they can't find someone. Your statement is pretty much what I'm saying, with the added "in certain markets" clause. That a market can't support such jobs doesn't preclude it from being a labor shortage. Think of it this way: A given business has a certain job that was economically viable, and they could…
I don't know about fair, but I find it misleading. When I hear "labor shortage", my intuition is that just having more people around (Advertise job offers better? Give more work permits?) would solve it, not that the market is such that this type of work doesn't make financial sense anymore.
"Labor shortage" sounds like some macroeconomic temporary situation to which businesses shouldn't need to adapt to beyond temporary measures, while what you're describing seems like a failure from a business to adapt to a new stable situation.
Footnote: I've heard the same nonsense about not enough COBOL programmers (I've reluctantly done quite a bit of COBOL over the years) with companies desperate to hire and will pay $$$ for the privilege of retaining them, but when I talk to these desperate companies willing to pay top rates for a decent COBOL developer, I find out they are offering less than I was making 20 years ago and choke when I say "to get me to move, you'd need to pay at least 10% more than what I currently make."
I was a C++ programmer for 25 years. Last 3 years, I'm using Rust language in my daily job and for all my hobby projects. I will not return to work in C++ again. No money can make me to change my decision. Nowadays, programming is a pure joy for me again. This was not the case when I had to work with C++.