H1-Bs are usually paid MORE, not less, because of wage parity laws that have existed for DECADES. The application process has a 6 month delay just to determine the minimum wage that the government forces employers to pay.
That is reference to people who have applied for asylum after having come in on a tourist visa. Technically their status is legal, because they have a pending application. This is an attempt to make their status illegal, so they can be deported.
Its only racism when you then go and invite white south africans in. And make statements like "Why cant we have more people come in from countries like Norway"
(a) The WSJ article is talking about "immigrant visas" a.k.a. green cards, not H1-Bs.
(b) Even if we are talking about H1-Bs, it takes someone in India 10-15 years of waiting in line to get a green card. If someone were to buy a house in the interim, it doesn't seem so irrational to me.
Its easy to blame the victim and say they should have known.
(a) I responded to OP's comment about H1-Bs, not the article itself. Even then, presumably, they paused processing new visa and the people that have already obtained them may continue to stay. If they fail to renew GC during this time, I agree that is a dark issue.
(b) If I enter China on a temporary work permit visa, with a 15 year plan to obtain Chinese citizenship, no one will have sympathy for me if that plan is interrupted by legal, political, economic changes. Since I full well knew my current status and the risks of failing to obtain Chinese citizenship.
Just because there is a possibility in the distant future for permanence, doesn't mean you can safely backdate it to today.
> If I enter China on a temporary work permit visa, with a 15 year plan to obtain Chinese citizenship, no one will have sympathy for me if that plan is interrupted
I would have sympathy for you if it was interrupted by suddenly changing the requirements through no action of your own.
Like, if you commit a crime, are a belligerent drunk, or whatever and they don't renew your visa over that, I have no sympathy.
If you're unable to secure employment for an extended period of time, and they don't renew your visa, I also have less sympathy since that's part of the bargain you knew going in.
If you play by the rules, but they reject a visa renewal for a reason like "we have too many immigrants from $x country, so we're rejecting y% of renewals" , well that's legally within the government's rights to do, but I'll have sympathy for you and think that you're morally in the right and China's failing its duty to its foreign residents.
Likewise, this US one is a case of capricious rejection, the US government is not holding up its end of the deal you both thought you were agreeing to. Like, the deal with a work visa, even if it's not permanent, is "if you follow the rules and keep good steady employment, you can live here, but yes it's conditional on the work thing".
I have sympathy for this hypothetical you, and also I have sympathy for those holding american visas who are impacted.
I don't remember Elon ever stating something does something it's not actually doing. His future timelines are off but it's never his competence that's been a problem with anything relating to SpaceX. And calling SpaceX (the entire industry leader) anywhere near "incompetent" beggars belief.
WDon't believe everything you read in headlines written by people with no understanding of the space industry. If you want to read about the industry, read about it on industry specific sites (like spacenews.com) or from industry specific reporters (Eric Berger or Stephen Clark at ArsTechnica). Davenport at Washington Post is good too.
It is interesting to see most people lay the blame at the feet of developers.
The reality is that these are all business decisions:
1) Move to the cloud because the business likes the steady payout of subscriptions. Business customers love not having to hire IT teams and demand six 9s of uptime because it is someone else’s responsibility. But performance needs to just be acceptable to end users.
2) Customers refusing to upgrade on-premises software, that led to long maintenance cycles and endless patches
3) Developing once for the web vs. Multiple times for different platforms – each needing its own developers and testers.
No amount of expertise on the part of developers is going to address these fundamental forces.
> Customers refusing to upgrade on-premises software
After a certain period of time, that software worked just fine for those customers. Photoshop is a great example. Sure, you won’t get the flashiest features, but CS4 will still work for you on a Win7 machine without any additional fees paid.
Once I commit to buying a version of Software X, I'm happy with it. As a user I expect Software X to work as-installed for decades to come. I don't want new features. I don't want the UX to change on me all of a sudden. I don't want it to get slower. Bugfixes and security fixes are fine, as long as everything else remains the same. I wish more developers understood and respected this.
When it comes to native apps, in the 2000s, this was the common attitude of users. But it's much harder to implement from a business perspective! Both in terms of business models, and in terms of dev time - having a bunch of possibly-incompatible versions lying around is a lot of overhead.
On the web, where most technical users understood this is technically impossible, they were willing to allow businesses to act differently, keep the software always-updated, and charge per usage. And since that's much easier and more lucrative for companies, they all switched to that.
(Now everyone kind of accepts that model, which is why today's Photoshop works via subscription, but the "damage" was done and the web won.)
> Bugfixes and security fixes are fine, as long as everything else remains the same.
Devs absolutely do not enjoy backporting bug fixes to 5 different LTS versions of their software and then getting user complaints because there's inevitably an important customer who is six versions back. It's inefficient with expensive dev time and it's better for the business to use that time to create new features.
edanm is correct, a lot of this is historical caused by very loud and angry tech users around the turn of the millennium. Want to know why Chrome won? When telling that story people tend to focus on performance or security, but that's not really it. Chrome won because Larry Page overrode all the internal screaming about silent web-style auto update for desktop apps. Oh boy, a whole lot of people really hated that idea, in fact Google had to develop their own software update engine from scratch to make it happen. Page didn't care. He understood that the ability to release a new version of web apps every week without the user noticing was a huge competitive advantage for the web, IE also updated in the background as part of the OS, and he wanted Google's desktop apps to have that same advantage.
Meanwhile Firefox stuck with the old model of rare releases and letting users choose whether to upgrade or not. It was a disaster. Old Firefoxes constantly annoyed web devs by preventing them from using new features. Security patches got reverse engineered and exploited. Still, Firefox's passionate fanbase loudly rejected the Chrome approach because they felt it took away their control.
Eventually the Mozilla guys accepted that they were wrong, their fans were wrong and Larry Page was correct. But it took years and in that time Chrome had built up a huge reputational advantage.
This is the real reason I use linux and open source, I want stability and flexibility not inevitably enshittifying SaaS. I am not an OSS or FOSS die hard, and I even advocate for a return to selling software as a deliverable so making small applications is a viable small business. But SaaS is the only viable business model it seems.
You can have efficient web apps running on the cloud, it's just a server after all. The issue lies with developers developing on machines their users can't afford and not caring about performance and efficient code.
i think many developers would make these same decisions. it’s painful to have to maintain separate platform versions of the same software, dealing with servers takes away development time, etc
reply