From your own citation: "Counterfactual simulations based on our model suggest that immigration increased the overall welfare of US natives, and raised workers’ incomes by 0.2% to 0.3%."
So they found that H-1B, etc increased native worker incomes overall.
So they mentioned some distributional issues ...
"wages for [high-skilled] US computer scientists would have been 2.6% to 5.1% higher in 2001"
Oh that kind of blows a little bit. But let's put this in perspective. 2.6%-5.1% higher in 2001 would be the difference between 100k and 103-105k. Sure I would love to have had that dough... but this 1) fails to demonstrate a substantial savings to firms 2) completely burns your argument workers making $0k.. they're doing quite fucking well. (100k was close to the average for mid-level software engineers in my neighborhood in 2001). This is not standard of living altering stuff.
And overall the economy did better with immigration.
> Most tech workers wouldn't take a $40k job because they realize that's a gross undervaluing of their skillsets.
What do you define as "undervaluing?" What sets this number? What makes $80k a fair wage vs $40k? Well the ultimate is the market. It is absolutely true that the mere act of bringing in more labor via H-1B will lower wages. I will not dispute that, that's basic microecon.
But how do you determine what your "labor is worth?" Because your labor is worth whatever that market price is, there is no "hope" to it. If a population is refusing to work for offers of $40k, because that "undervalues" their skills then that implies that the market has jobs that are correctly greater valued. If this were not the case then these people should just stop and take the $40k job, why continue applying for something that doesn't exist?
Of course not everything is smooth. The lag in filling these positions is what contributes to frictional unemployment. This is a good chunk of what makes up the unemployment figures. The fact remains, and what you just ignored... the unemployment rate in all industries, but especially IT and most engineering disciplines is the lowest it has been in years.
The Disney issue ultimately displaced not much more than 100 workers which is less than 0.2% of their tech and IT workforce, if that is the worst of the "bad news", it doesn't diminish my point.
Again, there is no disputing that a foreign worker program will lower certain wages in the short-term, possibly longer. There is plenty of evidence that this has not affected employment on higher skilled jobs.
The other weird thing that is always mentioned by H-1B foes is how shitty these Indian workers with no experience are (it was mentioned multiple times in the article you linked). So how does that square? If these workers are truly that crap, then why would anyone be surprised that Disney or anyone would want to get rid of expensive workers that can be replaced by these crap workers. Why should Disney or anyone pay top dollar for someone that can be replaced with the human equivalent of a shell script. If these crap workers really don't work out (and yes this has happened), well then the market isn't really harmed then is it?
What about automation and consolidation of services. Both have had tremendous effects on the IT industry. There were well paying jobs for "Computer Operators" a few short years ago.. now there are literally a handful and they pay barely above minimum wage. The influx of H-1B holders had little to do with this.
Finally, I'm not going to argue this, this is just a question: What do you feel gives you more entitlement to a job that an immigrant will willingly bring themselves over here and do for less?
The lack of perspective and basic reasoning on this is staggering.
> shitty wages, hours, and work environment.
A "shitty" wage is better than being unemployed and making 0k. Perhaps not if we were talking about at or near minimum wage. But we're not. We're talking nearly double the median income of the location in question and well beyond the poverty line.
If there were really this untapped market of native talent to replace H1-B imports, that are on average making $80k (actually $100k for tech), then that immense pool of workers can settle for $70k, $60k, $50k, $40k, $30k... and why wouldn't these companies take them at some low price between $100k and minimum wage? Why would these companies insist on hiring H1-Bs at a $100k a head if there was this large population of native, qualified, unemployed workers making $0 that would be lucky to get a measly $40k (to throw a number on it).
"Legions of smart lawyers" also sounds expensive. You don't need a legion of smart lawyers to hire from this large, unemployed, qualified, bonafide American talent pool that you insist exists.
The mental gymnastics H1-B paranoiacs go through does not fail to impress. During the first dot-com bust and post-recession at least it had a whiff of plausibility. But tech employment is at all time highs, it's beyond ludicrous.
And another thing that doesn't add up, the average for non H1-Bs in that pdf was close to $200k. And the unemployment rate in Texas is lower than the national average which is already low. In tech heavy cities like Austin it is even lower (near 2%!). So I have seen no strong evidence that H1-Bs are pushing American tech workers out of the middle class, the opposite in fact.
If you really know someone in tech that is unemployed and making nothing, then either they are not qualified or they have some other limitation making them unemployable. There are plenty of job listings at all levels across the US that are not open to H1-B sponsorship and some that are open just to US citizens (and do not require an existing clearance). Scapegoating H1-B programs in this economy isn't even offensive, it's just sad.
that doesn't change the economics at all.
the money paid to the worker through a middle-man has no bearing on the labor market as seen by the company and their bottom-line. You could send your paycheck into the incinerator every month... it makes no difference.
as you say the $80k is the rate to avoid hiring a US employee. maybe that's lower than what it would be with no h1-b, but then what are these displaced american workers doing for more than $80k?
epoll (and even kqueue) is not aio and was never intended as such. While epoll had some early snafus, those have long been fixed (offering ET and LT) and it works well for its intended purpose (io readiness). This (io_uring) is more for a thing like Windows overlapped IO and "unix" (incl FreeBSD) aio. AIO on linux is yet a separate set of syscalls (io_*) and has since day one in the 2.5 days been pretty much a useless joke, very limited in scope (O_DIRECT only).
kqueue is neither epoll nor aio but a common queueing interface for events, which includes io readiness and aio completion as separate types. Linux prefers to split these as different types of fds. FWIW, this wasn't due to obliviousness of the existing design - https://yarchive.net/comp/linux/event_queues.html.
Honestly your comment sounds very like a regurgitated old and somewhat outdated Bryan Cantrill rant.
I read your comment history... something about TRS-80s. So probably older than 40 and American. I am truly amazed that someone could live that long with economic means to post here and not know what a bank wire is!
Just google it though. It's the most common way to send moderate sums of money in the world. And yes, pretty much any retail bank or credit union will offer wiring, probably for a fee.
I mean it is pretty true that most frontend developers do not have the inclination to go trodding into a C++ code base making syscalls without a wrapper. Even taken uncharitably seriously, that is all the comment was insinuating. Everything else is added by you the reader.
And anyway I'm fine with exclusively frontend devs staying out of systems stuff. Anyone that wants to read OS kernel and compiler source code has tons of choices. Most I've talked to find it dry and boring. They don't belong there... that's fine.
I mean, I think that was a bit of a joke. It's ironic that you rail against this dude for "code that's hard to understand" in reply to a long-form prose article about understanding the code and how it got there..
We'll probably have to agree to disagree.. but that blog post doesn't really resonate for me... especially the end where it talks about keep it to your "own language." I've never had patience for identity politics especially in the case of a god-damn programming language.
Code blue is not literally used everywhere... many places in the US use a number these days like 99 for "Blue" and then other memorable two digit numbers for more specific, less emergent needs like respiratory support or rapid response. Same thing.
> didn't guarantee it'd call you at the specified timeout, the contract was that it'd invoke the callback no sooner than the specified timeout!
This is the contract for sleep on just about every general purpose OS preemptive or cooperative, and what would be assumed in the original article.
> I know this operation will take this many microseconds, can't I just sleep until it is done and the results are waiting for me?"
I mean now we're just conflating so many things. What you describe here is the essence of a hard real-time OS. It's quite orthogonal to the issue of ensuring low power. Since there are plenty of systems that require both.
> Plenty of old school engineers
I can assure you there are plenty of old school engineers that can get an MCU to run for months on a couple AA batteries. They're not spinning a 20MHz CPU in a busy-loop most of the time.
Nothing in the generic spec for a "sleep" function specifies you can't drop to a low power state if there is nothing to do. To varying degrees that is how sleep functions work on general purpose OSes. The CPU doesn't just spin for extended periods of time when there is nothing to do (it may spin for short waits). A "schedule a task to be called in 'n' hundreds of microseconds" is effectively a "sleep" function, the use of an explicit callback (PC) vs implicitly saving the PC of the thread is a mere implementation detail.
MSP-430 is not an OS, it is a microcontroller, so your comment makes absolutely no sense. Ironically one of the most popular open source MSP-430 OSes is FreeRTOS.. which of course has vTaskDelay.
Like name an OS (RTOS or otherwise) that does not have an API to sleep for millisecond periods? Not saying none exist, but, it's probably easier to name the exceptions.
> Do colleges exist to promote education and intellectual curiosity or to train workers?
When college cost in the US what it did in the 1960s this sort of little bit false-dichotomy, little bit navel gazing question was at least fairly harmless. Now it's just fucking ridiculous even for most public schools.
>> Haiku is an OS that basically no one uses for any purpose.
> By your logic, since macOS has ~1/10 the install base of Windows,
Does not follow. MacOS use relative to Windows is not at all a fair comparison. Firstly "everybody" uses Windows, so 1/10 of huge number is still a huge number. Second, except for gaming and some particular areas like EDA, MacOS has a general software library with a broad-base of technical and non-technical users throughout the world. Haiku OS cannot claim to have anything like that.
Not a great idea. Upvotes don't really tell you shit about testing, quality, or trust. I mean how many votes does acroread have (hint: a lot). The votes is merely to give arch some idea of how popular an AUR package is so that it can be absorbed officially.I have had a few of my AUR packages scooped up this way. Voting may indirectly indicate that the package is useful, but it doesn't say the thing doesn't contain malware nor does it indicate that the script is poorly written for other reasons. I orphaned a few quite popular AUR entries with high vote counts. The counts don't magically go away, and at that point anybody on the internet is free to adopt it.
So they found that H-1B, etc increased native worker incomes overall.
So they mentioned some distributional issues ... "wages for [high-skilled] US computer scientists would have been 2.6% to 5.1% higher in 2001"
Oh that kind of blows a little bit. But let's put this in perspective. 2.6%-5.1% higher in 2001 would be the difference between 100k and 103-105k. Sure I would love to have had that dough... but this 1) fails to demonstrate a substantial savings to firms 2) completely burns your argument workers making $0k.. they're doing quite fucking well. (100k was close to the average for mid-level software engineers in my neighborhood in 2001). This is not standard of living altering stuff.
And overall the economy did better with immigration.
> Most tech workers wouldn't take a $40k job because they realize that's a gross undervaluing of their skillsets.
What do you define as "undervaluing?" What sets this number? What makes $80k a fair wage vs $40k? Well the ultimate is the market. It is absolutely true that the mere act of bringing in more labor via H-1B will lower wages. I will not dispute that, that's basic microecon.
But how do you determine what your "labor is worth?" Because your labor is worth whatever that market price is, there is no "hope" to it. If a population is refusing to work for offers of $40k, because that "undervalues" their skills then that implies that the market has jobs that are correctly greater valued. If this were not the case then these people should just stop and take the $40k job, why continue applying for something that doesn't exist?
Of course not everything is smooth. The lag in filling these positions is what contributes to frictional unemployment. This is a good chunk of what makes up the unemployment figures. The fact remains, and what you just ignored... the unemployment rate in all industries, but especially IT and most engineering disciplines is the lowest it has been in years.
The Disney issue ultimately displaced not much more than 100 workers which is less than 0.2% of their tech and IT workforce, if that is the worst of the "bad news", it doesn't diminish my point.
Again, there is no disputing that a foreign worker program will lower certain wages in the short-term, possibly longer. There is plenty of evidence that this has not affected employment on higher skilled jobs.
The other weird thing that is always mentioned by H-1B foes is how shitty these Indian workers with no experience are (it was mentioned multiple times in the article you linked). So how does that square? If these workers are truly that crap, then why would anyone be surprised that Disney or anyone would want to get rid of expensive workers that can be replaced by these crap workers. Why should Disney or anyone pay top dollar for someone that can be replaced with the human equivalent of a shell script. If these crap workers really don't work out (and yes this has happened), well then the market isn't really harmed then is it?
What about automation and consolidation of services. Both have had tremendous effects on the IT industry. There were well paying jobs for "Computer Operators" a few short years ago.. now there are literally a handful and they pay barely above minimum wage. The influx of H-1B holders had little to do with this.
Finally, I'm not going to argue this, this is just a question: What do you feel gives you more entitlement to a job that an immigrant will willingly bring themselves over here and do for less?