Ok but isn’t that true of all software development? It’s not like anybody’s done a rigorous test of writing their entire codebase in Python vs Java. It’s all vibes based there. People create post-hoc justifications for why they use certain technologies but the reality is a lot more vibes than anything else.
When you start getting hate, you’ve made it. Up until then you’re a hypothetical that people like. Maybe they’ve built a side project with you or read the docs. You only get hate when people have used your tool and butted up against limitations. We saw this with Deno too where they went from beloved potential savior to realistic, limited tool. Hate is good. It means people rely on you
Both can be true? You can be doing really well and still have long term risk. Dethroning incumbents takes longer than people think and it’s possible that search growth goes 20%, 10%, -10%, -50%
A fun counter factual: try “proving” that famous scientists are their collaborators based on this methodology. Obviously Hardy and Littlewood are the same person. They’re both British mathematicians who use analysis and number theory and have similar sensibilities in politics and math.
I’ve proposed that someone open a restaurant of invasive species. You could make some decent dishes with lionfish, blackberries, golden oyster mushrooms, venison, etc
Agreed. I was skeptical of Deno and I think their package management story was a mistake. But the people were still trying to make JavaScript better and doing so out of genuine love for the language. I especially feel for the employees who put in several years of their life, with the resulting opportunity cost.
I'm not fully convinced that there's a tenable model for open source devtool companies. Usually there's some handwavy plan to do hosting or code quality that never comes to fruition. Hosting is a hard business and the 800 pound gorilla in the room of AWS is even harder to surmount. Otherwise, I'm not sure what business model you can look towards. Support maybe?
I wonder if it's almost like a new version of management consulting. You hire/invest in a bunch of smart 20-somethings who seem generally intelligent with the idea that they'll "disrupt" an industry with their from-first principles approach. Do the 23 year old McKinsey consultants particularly care about their work? No, but the McKinsey name is a fast way to gain clout and access to executives. Ditto the YC name
For what it’s worth Ruby’s JIT took several different implementations, definitely struggled with Rails compatibility and literally used some people’s PhD research. It wasn’t a trivial affair
That’d also be an interesting data point! What’s the upper limits of vibe coding? Can you vibe code rust? What about an entire programming language toolchain? How about an ecosystem? Can you make a parallel npm?
I really want to host a vibe coding competition and see what can actually be made with these systems. Like if we’re doing insane token spends, it better be in service of creating amazing stuff. Can we make an entirely new programming language? Can we make an OS?
The fundamental issue is that all of education and childhood accomplishments have become cynical, overly competitive games. Science fairs are now attempts for a child to piggyback off of a lab’s existing work and claim they discovered it. Sports are a vehicle to college admissions. Disability claims become another way to gain an academic advantage. It’s no surprise that the 30 under 30 are filled with scammers and criminals. It’s what we’re teaching students who want to get ahead.
I don’t think these are mutually exclusive takes. Bun is essentially taking Node and giving it a standard library and standard tooling. But you can still use regular node packages if you want. Whereas Deno def leaned into the clean break for a while
I like OCaml and have written the "why we chose XYZ language" posts. Most of the time the real answer is "we like it and it makes us feel good to use it". Like the answers aren't wrong per se but they're more post-facto justifications. And that's perfectly fine! I think we should normalize saying that tech stack choices are subjective and preference-based. We're not robots. The social and aesthetic parts of a stack matter to people
Never underestimate cultural momentum I guess. NBA players shot long 2 pointers for decades before people realized 3 > 2. Doctors refused to wash their hands before doing procedures. There’s so many things that seem obvious in retrospect but took a long time to become accepted
I gotta say, I feel pretty vindicated after hearing for years how Python’s tooling was just fine and you should just use virtualenv with pip and how JS must be worse, that when Python devs finally get a taste of npm/cargo/bundler in their ecosystem, they freaking love it. Because yes, npm has its issues but lock files and consistent installs are amazing