アドリアン
@adevress.bsky.social
Swiss knife HPC Engineer | 💬 Software, Engineering, Sciences | 💼 : @CERN, @EPFL, @BlueBrainPjt, @Woven_Toyota, @SKAO | ❤️: Happy husband and father of two.
Also on : 🐘@adev@hostux.social
Also on : 🐘@adev@hostux.social
Je pense que le monde peut actuellement brûler un cierge sur le fait que Google ait encore (partiellement) un semblant d'éthique et ne soit pas contrôlé par un Moron dictatorial comme Musk.
Car la situation serait bien plus préoccupante pour l'Europe actuellement
2/2
Car la situation serait bien plus préoccupante pour l'Europe actuellement
2/2
October 21, 2025 at 2:59 PM
Je pense que le monde peut actuellement brûler un cierge sur le fait que Google ait encore (partiellement) un semblant d'éthique et ne soit pas contrôlé par un Moron dictatorial comme Musk.
Car la situation serait bien plus préoccupante pour l'Europe actuellement
2/2
Car la situation serait bien plus préoccupante pour l'Europe actuellement
2/2
Honnêtement ce qui m'effraie le plus est la généralisation des prompts en lieu et place des search engine.
Ils sont les primo-portes d'accès à la connaissance en ligne.
Applique des filtres dessus et tu appliques des filtres sur 90% des résultats visibles en ligne.
1/2
Ils sont les primo-portes d'accès à la connaissance en ligne.
Applique des filtres dessus et tu appliques des filtres sur 90% des résultats visibles en ligne.
1/2
October 21, 2025 at 2:56 PM
Honnêtement ce qui m'effraie le plus est la généralisation des prompts en lieu et place des search engine.
Ils sont les primo-portes d'accès à la connaissance en ligne.
Applique des filtres dessus et tu appliques des filtres sur 90% des résultats visibles en ligne.
1/2
Ils sont les primo-portes d'accès à la connaissance en ligne.
Applique des filtres dessus et tu appliques des filtres sur 90% des résultats visibles en ligne.
1/2
Il y aura définitivement risque de manipulation des masses oui. Même avec des plateformes alternatives. Et Twitter est un très bon exemple.
Le phénomène d'écho chamber existe déjà, même sans LLM derrière.
Le phénomène d'écho chamber existe déjà, même sans LLM derrière.
October 21, 2025 at 2:54 PM
Il y aura définitivement risque de manipulation des masses oui. Même avec des plateformes alternatives. Et Twitter est un très bon exemple.
Le phénomène d'écho chamber existe déjà, même sans LLM derrière.
Le phénomène d'écho chamber existe déjà, même sans LLM derrière.
Honnêtement, ca serait probablement mieux que les shadowbans actuels.
Le faire de front motiverait certains à finalement converger vers une plateforme alternative.
Le faire de front motiverait certains à finalement converger vers une plateforme alternative.
October 21, 2025 at 2:47 PM
Honnêtement, ca serait probablement mieux que les shadowbans actuels.
Le faire de front motiverait certains à finalement converger vers une plateforme alternative.
Le faire de front motiverait certains à finalement converger vers une plateforme alternative.
"The art of .... being a Moron" - Donald Trump Jr.
April 11, 2025 at 11:46 AM
"The art of .... being a Moron" - Donald Trump Jr.
"The Kremlin complains about LePen conviction"
When Russia Putin's mafia is not happy about something. You know you did the right thing for your country.
When Russia Putin's mafia is not happy about something. You know you did the right thing for your country.
March 31, 2025 at 11:36 AM
"The Kremlin complains about LePen conviction"
When Russia Putin's mafia is not happy about something. You know you did the right thing for your country.
When Russia Putin's mafia is not happy about something. You know you did the right thing for your country.
Because she and her party stole 3.1M€ of public money with several schemes including non-existing jobs in EU parliament.
March 31, 2025 at 11:08 AM
Because she and her party stole 3.1M€ of public money with several schemes including non-existing jobs in EU parliament.
Bonus point, if you use UUIDv7: now you do not need to remember the birthday of your kids anymore: it's directly coded in the name.
a man with a mustache is smiling and looking at the camera while standing in front of a building .
ALT: a man with a mustache is smiling and looking at the camera while standing in front of a building .
media.tenor.com
March 22, 2025 at 8:01 PM
Bonus point, if you use UUIDv7: now you do not need to remember the birthday of your kids anymore: it's directly coded in the name.
Agree on both.
For type_traits, it makes sense when it was done in C++11 because it was the best we had.
Nowadays, most of them just feel terribly unnatural to use.
It could be (and probably should be) just a set of constexpr functions mapping on compiler builtins.
For type_traits, it makes sense when it was done in C++11 because it was the best we had.
Nowadays, most of them just feel terribly unnatural to use.
It could be (and probably should be) just a set of constexpr functions mapping on compiler builtins.
March 12, 2025 at 4:24 PM
Agree on both.
For type_traits, it makes sense when it was done in C++11 because it was the best we had.
Nowadays, most of them just feel terribly unnatural to use.
It could be (and probably should be) just a set of constexpr functions mapping on compiler builtins.
For type_traits, it makes sense when it was done in C++11 because it was the best we had.
Nowadays, most of them just feel terribly unnatural to use.
It could be (and probably should be) just a set of constexpr functions mapping on compiler builtins.
I have some others but a bit more controversial 🔥
March 12, 2025 at 8:22 AM
I have some others but a bit more controversial 🔥
(3) type_traits (And all other SFINAE tricks) - Should be replaced by some proper constexpr + concepts + static_reflection
(4) std::pair - should die for tuple
(5) std::tuple - should be heavily simplified and integrated at the language level
(6) volatile - should die entirely
2/2
(4) std::pair - should die for tuple
(5) std::tuple - should be heavily simplified and integrated at the language level
(6) volatile - should die entirely
2/2
March 12, 2025 at 8:22 AM
(3) type_traits (And all other SFINAE tricks) - Should be replaced by some proper constexpr + concepts + static_reflection
(4) std::pair - should die for tuple
(5) std::tuple - should be heavily simplified and integrated at the language level
(6) volatile - should die entirely
2/2
(4) std::pair - should die for tuple
(5) std::tuple - should be heavily simplified and integrated at the language level
(6) volatile - should die entirely
2/2
The question is not for me but I can't resist to answer 😁 :
(1) iostream - They should just die for the sake of the language.
(2) C compatible casts and consorts - Should be banned by default when C++26 or more is enabled. Provide an option to tolerate them.
1/2
(1) iostream - They should just die for the sake of the language.
(2) C compatible casts and consorts - Should be banned by default when C++26 or more is enabled. Provide an option to tolerate them.
1/2
March 12, 2025 at 8:16 AM
The question is not for me but I can't resist to answer 😁 :
(1) iostream - They should just die for the sake of the language.
(2) C compatible casts and consorts - Should be banned by default when C++26 or more is enabled. Provide an option to tolerate them.
1/2
(1) iostream - They should just die for the sake of the language.
(2) C compatible casts and consorts - Should be banned by default when C++26 or more is enabled. Provide an option to tolerate them.
1/2
Do you still have the source code somewhere? 🙂
I would be happy to archive it on a public repo.
The doom src code is a beautiful example of how a code can resist (or not) the test of time.
I would be curious to see which one of the C or C++ version can still compile in 10, 20y from now.
I would be happy to archive it on a public repo.
The doom src code is a beautiful example of how a code can resist (or not) the test of time.
I would be curious to see which one of the C or C++ version can still compile in 10, 20y from now.
February 21, 2025 at 7:55 PM
Do you still have the source code somewhere? 🙂
I would be happy to archive it on a public repo.
The doom src code is a beautiful example of how a code can resist (or not) the test of time.
I would be curious to see which one of the C or C++ version can still compile in 10, 20y from now.
I would be happy to archive it on a public repo.
The doom src code is a beautiful example of how a code can resist (or not) the test of time.
I would be curious to see which one of the C or C++ version can still compile in 10, 20y from now.