Clément Grégoire

Mostly moved to the place where the sky is blue.
Performance, GPU APIs, multithreading and game engines specialist @siliceum.

Does reverse engineering for fun.

[Clément Grégoire @lectem]

@Ced_haurus On peut meme pas opt-out préventivement...

[Clément Grégoire @lectem]

What the actual fuck @claudeai

[Clément Grégoire @lectem]

To the fucktard designer at @SamsungMobile or @Android who decided that opening an update dialog under my fingers AT 15% battery WITH A BUTTON AT THE KEYBOARD LOCATION WITHOUT ANY FUCKING CONFIRMATION DIALOG OR GRACE PERIOD:

YOU SHOULD BE FIRED AND EAT MY PHONE

[Clément Grégoire @lectem]

Fuck you very much @Samsung.

I've been postponing the oneui6.1 update for a while, and the dialog asking if I want to do it just popped WHILE I WAS TYPING TEXT.

Result: I pressed "update" unknowingly because the button appeared right under my finger.

I could have lost much

[Clément Grégoire @lectem]

@vkrajacic To be honest dynamic libraries have their uses, but they're hell on Linux. At least on windows it's easy to use/replace 😂

[Clément Grégoire @lectem]

@blelbach So doesn't std::simd. Or half of the std library additions since c++17.
Yet std::hive would be more useful than most of those.

[yoh @yohhoy]

C++26 Shipped a SIMD Library Nobody Asked For https://t.co/IWwmSC3j0z

[Clément Grégoire @lectem]

@rfleury @matiasgoldberg Did you start the kernel part?
Cause you'll have to parse (barely documented) text based files instead of proper APIs, for which the content may change whenever. At least you can read the kernel source to figure stuff out but that's not better than what the tool chains have.

[Clément Grégoire @lectem]

Yearly report you should not be using GCP. It's not the first mishap with governments, ask Australia.

[Joel 🇦🇺 @ptr_to_joel]

is gcp actually cooked

[Clément Grégoire @lectem]

@ForrestTheWoods I ended up using zigcc which is the only easily accessed toolchain targeting an old glibc. The fact we still need these kind of things (or go musl, which has its own issue) is sad.

[Clément Grégoire @lectem]

@jedisct1 Removing the perl requirement when? Insane we still need this to build in 2026

[Clément Grégoire @lectem]

@pandadiestro Circa 2022 😂
https://t.co/O99nRWY49j

[Clément Grégoire @lectem]

I mean, this is only one of the most used libraries in the world, no worries.
And it still relies on fucking Perl.

[Clément Grégoire @lectem]

@molecularmusing @SheriefFYI @jbevain Yeah it's something I do a lot too, it could be cached but I guess that some rules could be easily invalidated. Not surprising they didn't optimize it but yeah.

[Clément Grégoire @lectem]

@zooko @debasishg Wait until they discover what page tables and VADs are. Nothing is free.

[Clément Grégoire @lectem]

@zacbowden Had to check twice that today isn't April's 1st

[Clément Grégoire @lectem]

@MatRopert Like, people forget to await, pile up bad continuations, mishandle promises, forget about them, use await as ducktape. And then lifecycle issues appear, nothing is really ordered properly because. There are always event based systems at some point, which do not mix well with that

[Clément Grégoire @lectem]

@MatRopert I have mixed feelings about this. In theory coroutines (just as fibers) are a silver bullet. In practice I've seen enough crappy async/await usage in other languages (mostly JS-based) that I really fear what the lambda dev / LLM will write. Going to be a suspension point hell.

[Clément Grégoire @lectem]

@supahvee1234 Agreed too 😊

[Clément Grégoire @lectem]

@supahvee1234 Yeah that "put it in the stdlib" and "it's a QoI issue" mindset has been and will keep killing the lang.
It's not like we didn't have so many precedents (move, forward, atomic,...).
Welp