Twitxy Saved

Eugene Ostroukhov

Verified account This account is verified. Learn more

@eeuoss

GPU tools @ Apple. Distributed systems before that. Side project: UchenML, an ML framework for hardware that has no business running models.
Silicon Valley uchenml.tech Joined July 2008
647 Following 3K Followers 11K Posts

Latest posts 5

Pinned post

Eugene Ostroukhov Verified account @eeuoss
This is suffering-as-virtue thinking, straight out of Orthodox and Catholic tradition: “you have to suffer to earn it.”

AI, webpack, esbuild: it’s all just software. Use whatever solves your problem. If your goal is to build a website, build the website. You don’t owe anyone penance to prove you’re worthy.
Valentin Ignatev Verified account @valigo 8h
Without understanding, there cannot be improvement.

Before AI, you had something like this:
1) You need to set something up. Let's say webpack
2) You go through pain and suffering yourself and you hate it.
3) At this point, some people start thinking "holy shit this shouldn't be this bad"
4) Some people from step 3 start digging deeper and really understand what is happening.
5) Some people from step 4 see how much unnecessary complexity webpack has that can be entirely removed and they lock in
6) You get something esbuild which is orders of magnitude better than anything before.

Even before AI not many people would go through steps 3-6 in the first place. With AI, people won't even go through the step 2.

Again, without understanding, there can not be improvement.
View quoted post on X
1 replies 1 reposts 10 likes 707 views View on X
Eugene Ostroukhov Verified account @eeuoss
Interesting. My kneejerk reaction is that this is bad - I’d prefer separation of concerns and let the build system manage the concurrency. But I can totally see smaller projects not leveraging all the cores and compiling too slowly.
I think it is time to break up compilers, they seem to be doing too much.
gingerBill @TheGingerBill 2d
Wait… it wasn’t before?! Odin’s frontend and the LLVM backend have both been multithreaded for years.

How was this never a concern, especially when Rust’s frontend was not that fast either?!
View quoted post on X