Jay Mason

@jarredsumner @ThePrimeagen That just dodged the question. He’s asking, if mythos is so good, why didn’t you just fix the code base with it?

@ThePrimeagen here is a screenshot of some of the bun v1.3.14 release notes. many more bugfixes like this can’t rule out skill issue, but manual memory management combined with GC-managed memory is hard. could keep fixing one-off, or we could make it harder for these bugs to happen

with the zig to rust ecosystem due to segfaults... why didn't bun's team just tell mythos to fix the segfaults? "fix memory errors, no mistakes, and make it secure"

@TeamIDElab @ThePrimeagen Dude cmon; that’s such a dubious claim

@ThePrimeagen I think its great that the people are being convinced to hate AI while the people in power will keep and use it to continue to control the same populace that hates it

dude... this is brutal

@jarredsumner To me this comes off as 1. An attempt to punish zig for not allowing ai contributions and 2. A PR stunt for agentic coding. I doubt this port would have happened if it were not for the acquisition.

The people dunking on Bun’s Rust port are having a hard time coming up with a strong technical argument.

@suburbanfraud @hamptonism Are you just saying that or have you actually built a company? Product has never been the hard part; it’s market fit, customer acquisition, and capital.

There is a serious problem with this new generation. Former Google CEO encouraged students to embrace Ai at the 2026 University of Arizona Commencement Ceremony, and was met with a stadium full of boo’s. You heard that right, these kids are embracing the permanent underclass.

@mindmansions @ThePrimeagen False analogy; llms are stochastic. You can make that analogy if llms were deterministic.

@ThePrimeagen All the AI companies are moving away from Code Editors, they are literally saying you don't have to look at your code anymore. Same thing that happened when people move away from reading and caring too much about Assembly.

We have reached a point in 2026 that a week understood codebase is rare and is likely more valuable that all the "gains" bros got from AI

@draegor_ @ThePrimeagen I found Claude

@ThePrimeagen Bro, the point is, IA is a tool and helps you achieve more. You are sad because other people can do the same thing that you can? Because in theory, you should be able to do more than them. All this talk about how stupid AI is, this is more about ego, don’t you think?

@mitchellh The general sentiment in this comment section is negative. They're totally missing the nuance of your argument in the pr. This used to be an engineering field, not a stochastic slop fest.

Going forward, AI assistance must be disclosed for Ghostty contributions: github.com/ghostty-org/gh…

@hubermanlab @NIH They didn't look at the studies that show how IQ and age after 18 are inversely related.

I’m confused. For years people complained about excessively stringent paylines @NIH reduced budgets for labs & general clunkiness of the system but now they don’t want an audit of budget allocation to reduce non-research excesses because the audit is done by guys in their 20s?

@ThePrimeagen @elementaal20 There it is!

@elementaal20 nah, Jesus

I can relate to this so much I cannot explain the trepidation I have going to every single conference. I am under the full belief that I will never relapse of any kind, but I still feel the weight Then to double on that, pornography. 16 years and going strong, but man would it eat my life if I did

@elonmusk Ran into major bias in Grok-was like pulling teeth to get it to a very basic logical form. I would advise training the model to defer to logic rather than 'scientific consensus' in it's truth decrement hierarchy. If max truth seeking then pattern matching logic is top priority.

Guess who this is? 🤣🤣

@TristanSnell Oh great that must mean we are going after all the other people that attended Bilderberg

BREAKING: Elon Musk has SECRET MEETING with Iran's ambassador to the UN to discuss US-Iran relations. The Logan Act prohibits private citizens from engaging in foreign policy undercutting the US govt. Musk is NOT a govt official. If reports are true, this was a FEDERAL FELONY.

@FluentInFinance Don’t zoom out too much, you’ll see the rise and fall of empires.

In 2020 the stock market crashed 35% In 2008 the stock market crashed 55% In 1987 the stock market crashed 35% In 1973 the stock market crashed 50% In 1929 the stock market crashed 90% But it recovered to a new all-time high each time Don't let short-term fear control your long-term decisions ZOOM OUT

@housecor One benefit they missed is that if you create a service layer that implements a third party package, when/if that third party package is updated and there is a new api; you are only updating a few files in the service layer rather than n component files.

One of my clients is using an odd React pattern: They put only JSX in components. All logic is placed in a custom hook with matching name. Example: Product.tsx // Just JSX useProduct.tsx // Product logic I talked them out of this pattern using the justifications below. Benefit: The component file is simple. It’s just JSX. Downsides: 1. Reduces locality of behavior. Code with high locality of behavior is generally easier to read. 2. Have to frequently jump between at least two files to work with the component and fully understand it. 3. More code. Must export all state and functions from the hook, then reimport and destructure the properties returned from the hook in the component. 4. In many cases, the hook contains code it doesn’t use. It merely exports code so the component can import it. 5. Have to repeat many component props in custom hook since most component props are read in the custom hook. 6. Unused code can’t be detected via Knip, since the component consumes all the hook’s props. 7. Encourages creating a monolithic custom hook instead of abstracting small, focused, well-named custom as when needed. A monolithic hook doesn’t help break down complexity. It’s like a function named “function”. 8. React encourages grouping related JS, and JSX in the same file, since they’re fundamentally intertwined. The component is the concern. When the component gets too big, we can extract *components*. When logic gets complex, we can extract hooks. What I suggest instead: 1. Put logic in the component by default. 2. JSX too long or needs to be reused? Extract a component. 3. Logic too intimidating or needs to be reused? Extract well-named, focused custom hooks.

@pilcrowonpaper No

If you’re doing this function create() { return { a: () => {} } } just use classes