Sabitlenmiş Tweet
アドリアン
6.1K posts
アドリアン
@Adev
Engineer | 💬 Engineering, Software, Sciences, History | 💼 : @CERN, @HumanBrainProj, Startups, @Woven_Toyota, @SKAO | ❤️: Happy husband and father of three
Switzerland Katılım Aralık 2009
291 Takip Edilen251 Takipçiler
You have no idea how much headache and torture the 𝕏 team and Elon have to endure with the EU
The EU really thinks they rule the world. Their entire regulatory attitude is: “Do exactly as we tell you to do, and nothing more.” It's purely a dictatorship disguised as a democracy
You try to comply with one lunatic policy just to get them off your back, and boom... here comes another one, and another one... It's not just for the EU, they've become a pain in the backside for the entire world
Then one day, they hit you with a massive fine and try to loot up to half of your global REVENUE. Not even your profit... your gross revenue
It's pure extortion. Straight-up economic terrorism dressed in a suit
English
@blelbach Yeah I also remember this time where 'Exascale' was the buzzword.
I also remember the joke associated: "We will need a dedicated nuclear powerplant for Exascale, [ahaha]"
Little they knew that 10y, the big A.I DS effectively requires an actual dedicated power plant closeby
English
I remember the good old days when the Department of Energy's goal was to run an (FP64) exaflop machine in 20MW.
We thought that was a lot of power!
English
@stimmtdochgarn1 @MatRopert Additionally, this is what Bjarne points out also here saying "Some senior Soft Eng prefers retiring than dealing with LLM generated code".
So yes, people open their mouth without knowing shit about the topic he is talking on.
Nothing new here, this is Twitter.
5/N, N=5
English
@stimmtdochgarn1 @MatRopert It does not mean they cant be used.
It means you will need humans (real humans) to guarantee they do not fucked up in the task.
Because you need that for responsibility and certification reasons.
4/N
English
Thread is full of reply guys yelling "oh yeah and who are you to say that?".
I'm not saying you can't attack anything Bjarne says, but better bring better than "AI is inevitable you luddites" and "you haven't tried AI model 2026.5.7" while having an empty software engineering CV.
Haider.@haider1
Creator of C++, Bjarne Stroustrup: AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate "senior developers are already retiring rather than deal with it" The problem is that even a small prompt change can shift the entire codebase in unpredictable ways
English
@HSVSphere @geocucu Swift kind of understood that 10y before everyone else with their protocol systems instead of using Monomorphization for everything.
Unfortunately it has been implemented half way.
English
@owainkenway Use Nix (I'm half kidding).
Spack dependency model is fucked up beyond saving and the cost to that is forever endless recompilations.
English
Sure I'll just recompile llvm from source for no reason, why not, I've got 35 minutes to kill.
English
Problem is I use spack so little that every time I am forced to use it, I end up being forced to use it by someone else's two layers of higher level abstractions over it (usually involving spack environments) and end up lost in a twisty maze of massively overcomplicated things.
English
@MatRopert Most environment with validation implies clear processes, V-Cycle with strict tracing between every requirements and every line of code associated with them and justification for it.
That's not something coding LLM are good at it today and Bjarne is right on that.
2/2
English
@MatRopert Bjarnes speaks about validation...Most moron answering in the fields have absolutely not clue of the processes associated with safety critical code and validation but still open their mouth.
1/2
English
@jfmaquine @haider1 You are the perfect example of a Moron that do not know much about software engineering or/and Academia and still open his mouth.
English
He is the perfect example of why academics should never influence the industry. C++ was a disaster. The “keep it simple” principle was thrown out the window. The severe lack of optimization in all our applications today owes a lot to people like him because he forced us to lose sight of the silicon.
What is the relation with LLMs? Just the next step in programming. The mentality of the people who develop LLMs is the same as the mentality of the people who wanted a higher-level language to do tasks we couldn’t do. So they told us. Now, he uses the same argument he used against C.
I love the irony.
Note: It might well be that LLMs are more C-friendly than C++. I wonder why… keep it simple, perhaps ;).
English
Creator of C++, Bjarne Stroustrup:
AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate
"senior developers are already retiring rather than deal with it"
The problem is that even a small prompt change can shift the entire codebase in unpredictable ways
English
@awesomekling How it feels when your process experienced his first SIGBUS because a funny Jo truncated the mmaped() file during a reading.
GIF
English
how it feels to mmap() the whole file instead of copying it into a malloc() buffer
English
@WolfgangTheurer "Your survived, despite of your best efforts"
(and the fact you encountered a BMW)
English
Le motard est encore en vie, c'est fou
Lord Bebo@MyLordBebo
🇨🇦 Crazy motorcycle crash left the cycle hanging on the traffic light… both survived.
Français
C'est absolument l'inverse. À la base l'acier inox était censé réduire les coûts, mais ça s'est révélé impossible à produire. Plutôt que de revoir le design, Musk a préféré garder l'aspect du CT en concevant une structure classique sur laquelle s'ajoute une "peau" en inox
Vae Vix 🇫🇷 🇦🇺 🇨🇭 🇬🇧@VaeVix
Mais il faut admettre que c'est ignoble à regarder. C'est une bagnole d'ingénieur où l'ingénieur a dit "ta gueule" au designer. Musk c'est pas Jobs ^^
Français
@acenergie @Emericdevigan Expliquez moi comment ajouter du solaire va nous aider à exporter.
Spécialement en considérant que l'excédent de capa photovoltaique fait effondrer les prix à chaque rayon de soleil.
Je suis tout ouie.
être pro ENRs n'empêche pas d'avoir un peu d’honnêté intellectuelle.
GIF
Français
@Adev @Emericdevigan Et c'est tant mieux, du coup on arrête de vendre à export ? il nous reste tous les autres postes de conso d'énergie à décarboner, on attends là aussi? bizarre comment l'argument "Climat" en béton, des électriciens institutionnels disparait là tout d'un coup, quand il s'agit d'ENR
Français
"Il faut imposer du stockage sur les nouvelles installations solaire"
Traduction : on a besoin de stockage. Pas de nouveau solaire
Donc construisez du stockage. Pas de solaire.
Et mettons l'argent public ailleurs.
GIF
Français
If you ever heard about Rakuten management practices in Japan, that should surprise absolutely nobody.
A Donkey under Ketamine would probably have better vision and leadership capabilities.
next.ink/brief_article/…
English
@exvillager V is a transpiler to C that relies on Fabrice Bellard's TCC for unoptimized build.
TCC can eats way more than 1M line/s on a modern machine.
So yes, this is doable.
English
Reading 830k lines of code from disk itself could take hundreds of milliseconds and plus compiler compiling and generating the optimised binary.
I still don't understand how it's possible that 830k lines of code gets compiled 0.6 seconds
The V Programming Language@v_language
The V repo now has 830k lines of code! Of those, 225k lines are tests. V still compiles itself in 0.6 seconds on M5!
English
Actually, both formats are bad and it is an insult to human intelligence that they are still so widespread in 2026.
JSON has still the excuse of design simplicity, Protobuf does not even has that for itself.
Gaurav@sarmag77
Makes sense. JSON has far more repeated/predictable bytes because every item duplicates the same keys, which is exactly the kind of redundancy LZ77-family compressors do well. Protobuf actually has less per field overhead on the wire, that's why it's smaller uncompressed in the first place. The remaining time gap depends on the data itself. Lots of unique high-entropy values (UUIDs, floats, random strings) and protobuf still wins compressed. Lots of repeated structure with small values and JSON closes the gap or beats it. Protobuf strips redundancy at encoding time, gzip strips redundancy at compression time. JSON leaves the redundancy in and lets gzip do the work. So you're trading CPU (compress/decompress on every hop) for a payload that started bloated vs. protobuf which is already close to the information-theoretic floor, especially as item count grows.
English