> The agency's Bureau of Industry and Security said in a statement Tuesday that it's also planning to warn the public about "the potential consequences of allowing US AI chips to be used for training and inference of Chinese AI models."
The A.I. war is intense, and you can clearly see who is s** their pants here.
This is just beyond stupid. Sanctions as in "not letting them use our advantage" might make some sense, but "not letting us use their advantage" is just another level of retardity.
The superior languages on your list just reflect your personal preferences. There are not perfect languages, just appropriate languages for given application.
I don't like MS, either. BUT, let's be clear. No one is to obligated to work for free on OSS, not even big companies like MS. They have the right to constraint them to work on their own platforms. If you don't like it, you should fork the previous unconstrained versions or develop your own C/C++ add-on rather than complaining that MS stopped supporting your favorite extension.
"It's not illegal for them to do this bad thing" is such a common defense of companies doing bad things, as if it was the legality and not the ethics that was being discussed. I don't get it.
If Microsoft is gonna keep trying to enshitty their apps with unmasked for AI pop-ups that will always come back and even go so far to throw ads in at an OS level: yes, I will feel at least a bit entitled to some "free work" for taking hours of my time.
I sure do wish my industry didn't need windows. I'd happily go to Linux and never look back.
Personally, I don't get why there are so many standards for the web platform. Can't we just provide a minumum set of APIs that developers can build their own UI on top of just like what we do for the desktop?
i think they could if they started with "show users content they like" instead of "keep users staring at the app for as long as possible". both result in more engagement and more ad dollars, but optimizing for the latter becomes a race to the bottom with increasingly extreme, polarizing, emotion-inducing content.
the blatant algorithm manipulation around elections and politics is just the icing on the cake. sure, china is probably doing this too, but they're either being more subtle or playing a longer game. meta et al may have come out ahead for a few quarters but what's that worth if user count is declining long term?
It's pretty simple, the Tiktok algorithm recognizes the value of long term user satisfaction of it's users, and all the American Tech Algorithms are blind to anything long term, and plus the "user" is not the customer in the American tech product, the advertiser is, American social media is a product for the advertisers and not for the users. This is clear as day.
From time to time it will show you content adjacent to what you watch. After three or so viewings your feed will add the content you watched/engaged with regularly.
Press "not interested" twice (or sometimes once), and content will disappear.
American social media effectively ignores any input from users.
so much this. tiktok can easily be trained to provide you pretty much exact content you desire from it while no other social media platform (is willing) can do the same
> no other social media platform (is willing) can do the same
Are we sure? My experience with Instagram is the opposite, whenever you linger a bit on a reel you'll start to get more of that content
It's a pain because you have to constantly press "not interested" to curate your feed, I'd pretty much prefer to have content feeds, so that I can watch anything without having it go in my (im)permanent record
Is it? There is a lot of uphill battle on using DotNet librairies that are mainly developed with C# in mind. So all the nice things about F# like currying, no nulls etc go out the door because you're interacting with C# code. Rust is a first class citizen in its own ecosystem, so you never have to compromise on the strictness of your codebase
In practical terms it's mostly source-generators-based functionality and nullability that are an issue. F# 9 gains the ability to transparently understand nullable annotations emitted in C# by Roslyn and expresses them as `T | null` unions, or just as T if the T is non-nullable. Currying and other F#-specific features are simply syntax, there is no inherent limitation for defining a simple curried expression that ends up calling into a method implemented in a different .NET language.
The bigger issues are non-technical where it's just very few companies use F# in production. As for the technical ones - there are not that many and most of them are known (like mentioned above - code generation related, so the criticism usually mentions the same limited set every time, like code-first model definition in EF Core).
I don't know why I should switch from PyTorch to Tinygrad as a researcher and practitioner. In terms of kernel fusion, there is torch.compile. Not to say there is a large ecosystem behind PyTorch and almost every paper today is published with a PyTorch implementation. Probably what Tinygrad shines is bare-metal platforms?
