It's pretty easy, these are private companies and not democratic institutions that build consensus within their communities. It is better to assume bad faith upon corporate actors because they don't typically advocate for things that help humanity, mostly only themselves.
It's a way for web developers to easily work in the linux sphere without getting burdened too heavily. Not saying that as a dig to web devs, I'm a web deb but that's all it really appears to me. Popular dude in web dev community made it slightly easier for other web devs to do a thing.
Because there are some H1B workers that come over as translators or other non-tech professions. Like if you need a translator that speaks Swahili for some NGO it's way easier to hire a native Swahili speaker than possibly finding a qualified American that also speaks Swahili.
I do find it interesting that these trillion dollar companies can't find domestic workers, at their level of wealth they should simply be forced to pay for the education of Americans to create a funnel of workers rather than exporting this societal need to other nations.
There are a bunch of H1Bs working as teachers in my medium sized midwestern city, making around $50k. Then there are a bunch in the healthcare sectors making from $50k to $500k. I actually feel like they are legitimate reasons they are there, very difficult to get good healthcare workers in the midwest since no one good wants to go there.
There are lots of places that are hours to days drive away from those two. Midwest is a big place, so what are you talking about? I guess you could say the talent is concentrated in a few places, but lots of places in the midwest with terrible hospitals.
I am sure the issue of talent being concentrated in a few places is a problem everywhere but it’s definitely more of a problem in the midwest; the quality of doctors and other healthcare workers there are noticeably worse than the east coast.
There is a big problem with ethnic nepotism and ghost jobs. I have been struggling to get younger people in my network hired anywhere despite solid resumes. Continuing to issue H1Bs in the current job market was bananas.
Yeah, it's hard for this to feel like a community endeavor when it's a single company deciding to act on behalf of the community while never taking input or building a consensus around the issue with said community.
Hard to not be cynical about the whole thing, especially when it's a private VC backed company doing this and not say the OpenJS Foundation.
We need to forgo unions and straight up legislate forms of workplace democracy. People do not have meaningful control over a massive part of their lives and if democracy is good enough for state governments, it's good enough for private enterprise.
Have you looked into biome? We recently switched at work. It’s fine and fast. If you overly rely on 3rd party plugins it might be hard but it covered our use case fine for a network based react app.
Even minor styling rule changes would result in a huge PR across our frontend so I tend to avoid any change in tooling. But using old tools is not the end of the world. I only upgrade ESLint because I had to upgrade something else.
Was there? By 2016 it felt like nearly 80% of frontend development was happening in react. Even startups in central FL in 2015 were all in on react then. That's barely 4ish years from first introduction. That's quite fast in software adoption.
Definitely feels more geographically based then. I worked at Humana and Comcast, they were both on the react train by late 2015/2016. This was northeast area.
