This is mostly due to not trust busting enough in society. If there were actual competitive markets, not monopolies/oligarchies/monopsonies/cartels, the business world would be completely different.
I tend to disagree. While there are definitely monopolies/oligopoly for every domain, I'm actually constantly impressed with the very long tail of other providers available in that area.
Whenever I am looking for a new solution to a need at work, I would go to sites like g2.com to look at the lists of the most popular ones, and would then typically skim reviews of the top ~10, and more fully evaluate the top ~3. But there are often hundreds of alternatives that I haven't given a chance to, and I know that it's my <s>laziness</s> need to manage my limited time that's promoting this oligopoly, rather than any particular issue with all of those other providers down the list.
I don't see how legislation can help here, other than picking a provider for me. If anything, this is actually a place where I feel that AI tools, and particularly ChatGPT's Deep Research can research a lot more of the alternatives than I as a human would have time for. But that of course has its own set of issues, and I really don't know what the solution is. We no longer live in that world where you just use that provider who lives down the street.
Legislation can help in a variety of ways, like taxing digital goods to provide work grants for open source developers. The federal government could create a public payment processor.
There are many things that can be done to help the public flourish, it's very easy if you open up your imagination.
Close enough. I missed 2 vesting periods. But the severance and rapidly having a job made up for one and I got refreshers my third year that I hadn’t counted on.
I left debt free, sold my old home for exactly twice what I had built for 8 years earlier, downsized to a condo half the price I sold it for (and 1/3 the size) and I was debt free with savings.
I’m now a staff consultant working full time at a 3rd party AWS consulting firm with a lot less stress and still remote. They were the last to fall. But AWS made their ProServe department return to office at the beginning of this year.
It's extremely worrying on how they had to use a private "foundation" rather than using existing, more democratic, organizations like OpenJS foundation.
Don't expect user input, don't expect changes that go against their wants over the community's needs, and don't expect things to get better.
Really feels like react has held back frontend development. The idea that everything on the web should be written in react is baffling but I'm sure people thought similar thoughts when jquery or angular were popular.
Forget the underlying language, the real shift was this idea that every website should be a single page application, which we are now moving away from again but seemingly everyone has forgotten how to do it, so it's being done "the React way".
This could be because of developer fatigue and the trend of forcing backend devs to do fullstack.
Its very hard to keep up with the frequent changes to programming models, new frameworks, CSS libraries (why the heck are they soo many?!) when you also have to design O(Log n) backends, IaC, Observability, LLMOps, etc.
I have come to a compromise and have started advocating for React/Redux/TS/NextJS as the default CRUD application stack so that I can focus on solving real CS problems in the backend that I’m passionate about.
But react is where developer fatigue is most endemic. Since it only does one thing, that typically means you have to import a dozen other libraries that are mostly "flavors of the month" captured in time. You can easily tell when a react project was started based solely on it's dependencies. This is bad because it typically means no two react projects will use the same dependencies.
These dependencies are the root of the issue.
FWIW, I've only ever professionally work with react on the frontend. For nearly 10 years too. My first job I was doing react.createElement() before classes were shortly introduced afterwards.
It's time that we move on to something better, and the react foundation being controlled by private entities while not being an actual democratic foundation is a good omen of what to expect.
> Since it only does one thing, that typically means you have to import a dozen other libraries that are mostly "flavors of the month" captured in time.
By weird happenstance I got a job writing in a half-dead, compiles-to-JS language 5 years ago. There's one way to handle state in it. My view on the libraries you need to handle everything-but-view in React has been "I'll come back to these when the dust settles" and it just never settles.
None of these have usage numbers that rival react, at least not in the US. I wish it were so because many react libraries can easily support other view libraries with minor modifications to decouple it from react.
reply