Bryan MacLee

540 posts

Bryan MacLee

Bryan MacLee

@BryanMaclee

My vocation is, truck driver specializing in the oil and gas industry. My avocation is writing code.

Vernal Ut Tham gia Mart 2022
170 Đang theo dõi76 Người theo dõi
Bryan MacLee
Bryan MacLee@BryanMaclee·
GPU's are entirely the wrong hardware architecture. Compilation is not a vectorized problem. Modern compilers spend most of their time doing things GPUs hate: dependency analysis, graph traversal, branch-heavy logic, pointer chasing, cache-sensitive data structures, and synchronization between passes. GPUs excel when you can run the same instruction across huge amounts of independent data. Compilers are usually the opposite. They are designed to handle highly irregular workloads with many sequential dependencies and unpredictable memory access. You might accelerate isolated passes on a GPU, but moving an entire compiler there would likely make it slower, more complex, and dramatically harder to maintain. CPUs are already extremely good at the kind of work compilers actually do.
English
0
0
1
28
pavi2410
pavi2410@PavitraGolchha·
@mitsuhiko What if Rust could compile on the GPU?
English
2
0
0
378
Haiyami Nguyen
Haiyami Nguyen@haiyami9x·
@BryanMaclee I know it could be, but mocking popular people is just so effective, can't help it 😉
English
1
0
0
378
dax
dax@thdxr·
@LukeParkerDev i don't have any shitty code to remove
English
4
0
116
5.3K
Luke Parker
Luke Parker@LukeParkerDev·
ill bless my timeline with this on a sunday. gemini 3.1 pro is the ONLY model I've seen REMOVE heaps of shitty code to refactor with a net-negative churn. do with that what you will.
Luke Parker tweet media
English
30
1
340
40.8K
Bryan MacLee
Bryan MacLee@BryanMaclee·
@thdxr this will mean nothing... in 3 - 4 months
English
0
0
0
166
Ryan Fleury
Ryan Fleury@rfleury·
@valigo Nobody listens to me about sum types…
English
7
0
135
8.5K
Valentin Ignatev
Valentin Ignatev@valigo·
Entire api surface of io_uring - the fastest way to do IO on Linux - is 3 syscalls and 3 structs. But one of the structs is actually a bunch of unions (on the pic), so the amount of invariants is big! That's why liburing, the go-to way to use io_uring, is ~4k lines of code
Valentin Ignatev tweet media
English
12
14
364
32.3K
Roman
Roman@romxdev·
The evolution of the full-stack developer: 2020: Equally bad at SQL and CSS 2026: Knows how to argue with an LLM until it finally outputs working code
English
4
1
21
814
ThePrimeagen
ThePrimeagen@ThePrimeagen·
Current meta
ThePrimeagen tweet media
Español
49
37
1.3K
48.5K
Bryan MacLee
Bryan MacLee@BryanMaclee·
though, perhaps, this is exactly what we need to move past npm. think about it. if suddenly there are millions of local node module forks thrust out into the wild. There will be security vulnerabilitys galore. In turn. People realize the better path is to use those llm accounts to unethically hack. They wont realize that all of their easy targets don't have any users and therefore no money to scam. And in all this noise, an opportunity to have REAL conversations about the future of programming, might just make itself known.
English
0
0
0
31
Bryan MacLee
Bryan MacLee@BryanMaclee·
@teej_dv 🤣🤣🤣 Didn't you tell it, no mistakes? Though, it's hard not to look at this as the result of compounded mistakes.
English
1
0
2
1.7K
teej dv 🔭
teej dv 🔭@teej_dv·
5.5 just edited a node_module file directly.... what?!
English
128
19
2.4K
247.2K
Tom Siwik
Tom Siwik@tomhacks·
Is your content boring? - snipe a viral post in your content niche and repost it (count likes of YOUR followers) Is your opinion boring? - snipe & quote viral post (count interactions) Are you boring? - reply /w banger and check if author starts a dialogue
English
3
0
5
169