“Learn to code” is much less viable as a career choice if billions of Indians know how to code and are willing to do it for significantly less than the basic costs of living in Western countries.

American companies moving software jobs to India like they’ve moved manufacturing to China would be a particularly nightmarish scenario.

FOSSBYTES:

As per the new education policy approved by the Narendra Modi-led government, students in India will be taught coding as a subject from as early as class 6. Typically, students in the 6th standard are roughly around 10-11 yrs of age. The aim of teaching programming skills in schools is to help them acquire 21st-century skills.

This announcement was made in by Education Ministry officials at a press conference in the presence of Union Minister Prakash Javadekar.

The world is advancing highly in technology, and several job roles today requires coding skills in candidates. So keeping the future in mind, programming skills can ensure a greater exposure to technical knowledge in early stages and help students progress easily if they wish to take up a technical career ahead.

As long as H1-B visas are a thing, Americans doing software development are directly threatened by Indians. Companies often hire these people to work remotely, too. With remote work being the default in America now due to the coronavirus hoax, a lot of companies are going to start crunching the numbers and realize that there isn’t any significant difference in hiring someone who lives down the road and someone who lives on the other side of the planet.

Indians are cheaper than automation, robots and AI, and they feel entitled to America’s wealth.

Today protests broke out outside @SenGaryPeters’s office protesting @SenatorDurbin’s bigotry against Indian immigrants.

Durbin needs to be constructive by negotiating with Senator Lee, instead of shamelessly grandstanding on the Senate floor.

Sen Peters needs to denounce Durbin pic.twitter.com/m0Jl0cWCMs

— Immigration Voice (@immivoice) July 23, 2020

There’s more than a billion Indians over there, dreaming the American dream.

They’re coming.

Pictured: “Tux,” the brand character of the Linux kernel.

It didn’t take long after Linus was forced out of the project for being white for the project to turn anti-white.

At this point, Linux is even more anti-white than Apple or Windows.

The Register:

In the light of the 2020 “global reckoning on race relations” the Linux kernel developers have stepped up with proposed new inclusive terminology guidelines for their coding community.

The proposal has come from Intel Principal Engineer Dan Williams and won support from other Linux maintainers including Chris Mason and Greg Kroah-Hartman.

Words to be avoided include “slave”, with suggested substitutions such as secondary, subordinate, replica or follower, and “blacklist”, for which the replacements could be blocklist or denylist. The proposal has allowed for exceptions when maintaining a userspace API or when updating a code for a specification that mandates those terms. The existing Linux kernel coding style, described here, and has made no mention of inclusive language.

The proposal is to add a new document, to be called Linux kernel inclusive technology, which will give the rationale for the changes. Referencing the fact that “the African slave trade was a brutal system of human misery deployed at global scale,” the document has acknowledged that “word choice decisions in a modern software project does next to nothing to compensate for that legacy.”

The goal, though, will be to “maximize availability and efficiency of the global developer community to participate in the Linux kernel developer process.”

“The revelation of 2020 was that black voices were heard on a global scale and the Linux kernel project has done its small part to answer that call as it wants black voices, among all voices, in its developer community,” the proposal read.

The proposal also noted that “non-inclusive terminology” has a “distracting effect” and “injures developer efficiency.” Of the anticipated backlash, Williams stated: “Of course it is around this point someone jumps in with an etymological argument about why people should not be offended. Etymological arguments do not scale. The scope and pace of Linux to reach new developers exceeds the ability of historical terminology defenders to describe ‘no, not that connotation’.”

For people that are supposed to be smart, these Linux developers are quite stupid. Or maybe they’re just malicious and hate white people.

These are some of the points they make:

1. “The African slave trade was a brutal system of human misery deployed at global scale”
2. “Word choice decisions in a modern software project does next to nothing to compensate for that legacy”
3. “The Linux kernel project has done its small part to answer that call as it wants black voices, among all voices, in its developer community”
4. “Of course it is around this point someone jumps in with an etymological argument about why people should not be offended. Etymological arguments do not scale.”

“The African slave trade was a brutal system of human misery deployed at global scale”

First of all, the African slave trade never ended. Africans still enslave Africans on a daily basis. Every day, black people do worse things to other blacks than white people ever did to blacks.

White people were also enslaved.

From Wikipedia:

Under Muslim rule, the Arab slave trades that included Caucasian captives were often fueled by raids into European territories or were taken as children in the form of a blood tax from the families of citizens of conquered territories to serve the empire for a variety of functions. In the mid-19th century, the term ‘white slavery’ was used to describe the Christian slaves that were sold into the Barbary slave trade.

…

The phrase “white slavery” was used by Charles Sumner in 1847 to describe the chattel slavery of Christians throughout the Barbary States and primarily in the Algiers, the capital of Ottoman Algeria. It also encompassed many forms of slavery, including the European concubines (Cariye) often found in Turkish harems.

Perhaps we should be rioting, too.

“Word choice decisions in a modern software project does next to nothing to compensate for that legacy”

The idea that we must “compensate” for the past, that software should compensate for the past, and that words in software can somehow compensate for the past are deeply retarded.

Black people are free to go back to Africa, but they stay in white people’s countries and actively try to get into white people’s countries because their own countries are hell holes.

Living in white people’s countries is a privilege, and we’ve been putting up with their violent behavior and ridiculously high criminality for far too long. They should be compensating us.

“The Linux kernel project […] wants black voices, among all voices, in its developer community”

The idea that blacks can somehow contribute something of value to the Linux kernel or software in general, and that they’re not doing it because they find words like “slave” and “master” in the code is preposterous.

I can count with the fingers of my hands the amount of blacks who can write something of value in a programming language, and I have the same amount of fingers as other humans on this planet.

But even if they could contribute and weren’t doing so because they feel offended, then who cares? It’s not as if we didn’t have white people to work on, you know, the things that white people have created!

I vehemently oppose people of color taking over what my people have created.

“Etymological arguments do not scale”

Why do we have to hear bugmen smugly tell us such things? Why do black feelings have to dictate the reality of white people do in white people’s countries and in white people’s industries? Why can’t blacks just go back to Africa if they don’t like it here?

Why does offending white people not matter?

Why do we not matter, not even in our own countries?

Linux is about to get nasty.

When I heard that Linus, the top maintainer of the Linux operating system, had finally cucked and allowed the SJW mob to bully him into accepting politically correct norms into the kernel development scene, I just thought “eh, that’s too bad, this guy used to be based.”

However, things are apparently not going to end there. First, Linus is not the only one being run out of the community – and those people are not taking it lightly.

If they go for the nuclear option – which is being discussed – this could have world-altering consequences.

As an open letter posted to the Linux Kermal Mail List, provided by LULZ.com, reads:

Date Thu, 20 Sep 2018 09:28:14 +0000
From unconditionedwitness@redchan …
Subject Re: A Plea to Unfuck our Codes of Conduct

Regarding those who are ejected from the Linux Kernel Community after this CoC:

Contributors can, at any time, rescind the license grant regarding their property via written notice to those whom they are rescinding the grant from (regarding their property (code)) .

The “CoC” is the “code of conduct” or “contributor’s covenant” that was adopted recently.

It was created by some kind of tranny freak.

Click to enlarge.

Moreover, it was created for explicitly political reasons.

It allows anyone to be expelled for any reason, regardless of their importance, seniority and the quality of their work, if they offend anyone.

And of course, the “people” responsible for enforcing this system will be creatures like “Coraline” above.

The GPL version 2 lacks a no-rescission clause (the GPL version 3 has such a clause: to attempt furnish defendants with an estoppel defense, the Linux Kernel is licensed under version 2, however, as are the past contributions).

When the defendants ignore the rescission and continue using the plaintiff’s code, the plaintiff can sue under the copyright statute.

Banned contributors _should_ do this (note: plaintiff is to register their copyright prior to filing suit, the copyright does not have to be registered at the time of the violation however)

Additionally when said banned contributors joined the Linux team, they were under the impression that it was a meritocracy: in-fact this belief was stated or ratified by those within the governing body regarding Linux when the contributors began their work (whatever that body was at that time, it could have been simply Linus, or Linus and a few associates).

The remuneration for the work was implied to be, or perhaps stated, to be fame as-well as a potential increase in the contributors stature, in addition to membership in the Linux Kernel club or association, or whatever it is that the Linux Kernel Community actually is (which a court may determine… it is something, suffice to say).

Thusly for work, consideration was promised by (Linus? Others? There are years of mailing list archives with which to determine).

And now that consideration has been clawed-back and the contributors image has been tarnished.

Basically, some of the smartest computer scientists in the world have been contributing to the Linux kernel for years, expecting in return nothing more than prestige and recognition for their work.

But now even that is being taken away by worthless human garbage for ideological reasons. Thus they would be fully and legally justified in taking back ownership of their contributed code.

That would obviously cripple the kernel, however – which is the point.

Thus the worker did work, however the other side of the implied, or perhaps written (email memorandums), understanding has been violated (once the contributor has been banned under the new non-meritocratic “CoC”).

Damages could be recovered under: breach of contract, quazi-contract, libel, false-light. (services rendered for the contractual claims, future lost income for the libel claims)

In addition to copyright claims. (statutory damages, profits)

For greatest effect, all rescission should be done at once in a bloc. (With other banned contributors).

Contributors: You were promised something, you laboured for that promise, and now the promise has become a lie. You have remedies available to you now, as-well as in the close future .

Additionally, regarding those who promoted the Code of Conduct to be used against the linux kernel contributors, knowing full well the effect it would have and desiring those effects; recovery for the ejected contributors via a tortious interference claim may be possible.

You might not understand the importance of this intuitively, since “Linux kernel development” sounds like something obscure and irrelevant to everyday life.

However, the overwhelming majority of all computers currently in operation are running on Linux. Most importantly, most web infrastructure relies on it, not to mention smartphones and some financial infrastructure.

If these devs go through with the process described in this open letter, it would make it illegal to use current versions of Linux without paying these devs copyright fees. In other words, all their code would either have to be taken out, which would cripple most of the world’s tech infrastructure, or everyone will need to start using some other OS – which doesn’t currently exist.

As LULZ.com notes:

If carried out, ramifications could include large parts of the internet being left vulnerable to exploits, and companies around the world might even inherit bundles of unwanted legal liabilities.

In other words, the consequences of this SJW hostile takeover of Linux could be economic damage numbering in the trillions.

Hey, it was all worth it, right?

Andrew mentioned earlier this week that this could well be a kike move to undermine Linux’s security, and there’s evidence that this is the case.

Several users on 4chan’s technology board speculate that Theo is targeted first because he famously resisted an Intel backdoor.

However, I highly doubt that their goal was to destroy Linux – that would be completely insane. They probably just wanted to inject a bunch of degenerates into the development team so that it would be easier to push for backdoors and other security loopholes.

Hopefully, seeing how the old guard Linux dev community seems to have their finger on the nuclear button, the SJW/kike offensive will have no choice but to capitulate and retreat.