And this wouldn't have happened if we had tried to get them to buy our hardware rather than trying to gatekeep. Protectionism never works in the long term.
US companies should now be more worried about Chinese companies flooding the market with their, hopefully, very affordable GPU's. The scale at which they can manufacture stuff is unmatched anywhere else. Nvidia can kiss goodbye to their 75%+ profit margins.
Almost everyone knew that these sanctions would backfire within a few years. You can't really put sanctions that have noticeable negative effects on bigger economies. They only work for small to medium economies. I believe sanctions on any economy in top 10 would fail.
You seem to misunderstand what Protectionism is.
This is not an example of it not working. If anything, it is any example of it working. Because Protectionism is about protecting your industry from foreign competition - exactly what China decided to do.
Look at how China does it. They'll happily sell us everything we want - more than enough of it, cheap enough, to put all of our own manufacturers out of business.
Same thing with Trump not helping Ukraine and berating NATO. He thought he held all the cards, but now Ukraine has a thriving battle-tested drone industry, UK and France have stepped in to replace the US with advanced missiles and anti-missile systems, stepping up their own production and transferring IP to Ukraine.
Now, the US is left out in the cold with little influence left, themselves now the ones with an anti-missile shortage.
This is a really funny sounding post. They sound like they just found out that increasing your automation gives you increased capabilities at faster speeds. They also sound like they just realized AI makes hard things easier.
But what really kills me is the idea that these companies are using Python for production inference. I mean really? Have you seen how bloated and slow Python is? Do global locks really sound like a strategy for fast dynamic computation?
Most of the fastest inference and training code in production today is written in Python. There are no global locks on the GPU except the ones you put there
It's not that they "just found out" - what they are saying is that while they were previously dogfooding because it's good practice, now that their models are so much stronger they are using them because it helps accelerate.
If you look at how many years the whole NVIDIA and CUDA ecosystem has been evolving, it's certainly impressive how they've just stood up and optimized this CUDA-free 100,000 node cluster in just a few months.
The colors refer to variations in wavelength (light ~ sound) adjusted to human perception of soundwaves (https://tinyurl.com/3bzy7a7s). It helps muffle ambient sound that might distract your brain. Studies show they have effects: brown = executive function/memory, pink = sleep/concentration, green = calming, white = productivity/annoying.
Dark noise isn't an accepted term, it's a marketing term for a tweaked version of brown noise
How are you holding it? You'll get wildly different real-world results from different inference providers, for one. For two there's the harness and what you do with it. In general you'll need to provide more direction to lightweight models, better guardrails, more planning, tighter goals.
> > GitHub Actions: 12 hours affected in the last 30 days (98.31% uptime).
Which 12 hours? One block of 12 hours? Twelve blocks of 1 hours? Important hours or unimportant ones? Which hours are important to whom?
The audience for the status page is everybody, and everybody will want things their way. There is no pleasing everybody. That's why there's color. If you see a lot of red, that's bad. If there's not that much red, it's not that bad.
1) Flock developed a nationwide network to track innocent people, tried to get in as many places as possible, and handed law enforcement agencies carte blanche access with virtually no oversight. Their whole schtick was being the mass surveillance company, and striking fear into people's hearts, in order to prevent crime. Despite being founded in 2017, they quickly reached hundreds of thousands of cameras installed.
2) The US Executive branch formed concentration camps and a private army, and started using this nationwide mass surveillance network to track down any brown people with a Spanish accent to lock them up in dangerous squalid conditions and/or deport them with no trial. This is an immediate, nation-wide harm being done to millions of Americans, and this new company is enabling it.
Watch your next demo day meeting... Some people will get tons of reacts, comments; some people get nothing. At least in person you get the obligatory smattering of claps after the talk. When there's nothing at all, it feels like you did something wrong.
For those struggling with the idea of staying relevant as a human programmer, think about other jobs first. What jobs are there today that humans work on, despite technology making humans obsolete?
Mostly humans are replaced at physical labor (although even then not entirely). Human computers and punchcard operators, switchboard and telegraph operators, typesetters/letterpress/linotype operators, draftsmen, photo retouchers, film developers and projectionists, pneumatic tube operators, record-pressing/mastering engineers, the horse-drawn transportation industry, handloom weavers and embroiderers, coopers, wheelwrights, blacksmiths, key cutters, bookkeepers, payroll clerks, proofreaders... This is just a tiny list.
Technology replaces the least efficient parts first, and humans remain to do things that're harder or more expensive to automate safely or reliably. A human who used to build something by hand, transitions to a human who operates a machine to build, then designs or prepares work for the machine, and finally maintains the machine that does it all. For many automated jobs, people now perform maintenance, operations, or design work, that could be done by machine, but we either require or prefer a human do it.
For those remaining jobs, you often still need special skills. But it's no longer a herculean task to perform the work, and the jobs are more specialized and less skilled in general. We still need those jobs, or those automated things simply wouldn't function. Someone has to build them, someone has to maintain them, and someone has to operate them, and each of those requires skill.
So human programmers, systems engineers, designers, architects, operators, etc, will all be very necessary over the next 50 years. You will still need to know the languages, compilers, networks, computers, etc work. You just won't be manually typesetting anymore, or manually weaving the digital cloth. Someone will need to get into the guts of the machine from time to time.
Or, we could introduce a software building code, the way we have codes for every other kind of safety-impacting product. But apparently software is never unsafe, we never need to protect people from software systems, and definitely shouldn't pass a law requiring those systems be protected adequately, with legal consequences for not doing so.
Even though software has been around for a while now, it does still seem to be evolving rapidly enough that a fixed code is a bad idea. Remember password change requirements that were terrible, but stuck around for 20 years before being removed from the relevant voluntary code (I think something from NIST)?
NIST creates the standards that businesses must follow when doing business with the Federal Government. Without those standards, the government's operations would be even more unreliable and haphazard than they are today.
A long time ago they mandated a single password policy, because having thousands of agencies all with different password policies was crazy. At the time, they (and the industry) thought it was a good policy. Some people suspected otherwise, but there was no proof to show that a change was necessary. So academic research was undertaken to find whether the policy was helping. The research showed that it was more harmful than helpful.
Academia proposed a solution, NIST considered it, and then adopted it, in 2017. The language they used in 2017 was "flexible", so nobody really had to change. Finally in 2025 they made the language mandatory. Now the affected companies will be forced to abandon their crappy password policies, specifically because they aren't allowed to keep them anymore, if they want those lucrative contracts.
This should not just apply to the Federal Government. The same reasons FedGov needs these standards applies to every single one of us. The tech lobby has successfully fought this for years, and politicians are scared of introducing something that might negatively impact public citizens (and thus risk the politician's job). But they can't deny that FedGov needs these standards.
This is a pretty normal process. The electrical code, building code, fire code, etc, all take time to change. But the changes do happen, and we all reap the benefits. With no code at all, we would be experiencing a lot more death, injury, financial loss, and inconvenience.
And btw, there is a lot of technology that has not evolved much in 40 years. We don't need to make everything absolutely perfect, and every aspect 100% set in stone, in order to have a code. Every other code is updated regularly. Software code can change too. (Or are software people too incompetent to figure it out? I might agree with that...)
It's a failure story of regulation because the regulation was bad, and took forever to get changed.
I don't mind if government software has to use Dual_EC_DRBG - let the government hack itself. I do care if you get prison time for using a secure random number generator.
reply