A newly discovered species of wasp has been named after Oscar Piastri, the 'Gwesped piastrii' 🐝👀
Found in Burmese amber in northern Myanmar, the researchers chose to honour Oscar for his achievements in Formula 1 as the amber reminded them of McLaren papaya
#F1
Andrew is relentlessly building the world’s most powerful systems programming language (and toolchain).
He has my full support and trust (and frankly, sheer gratitude for holding firm on quality).
Props to @jetbrains for putting together a terrific interview.
sou a maior fã de raivas controladas e conscientes
*ARREMESSA UMA COISINHA*
*coloca calmamente o volante de um zilhão e meio de dólares ao lado*
*ARREMESSA OUTRA COISINHA
now where is the project hail mary cut that has the ariane launch clip… i saw that beautiful piece of engineering in the trailer pls do not withhold her from me
It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all.
There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message.
A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this.
On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting!
There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting.
I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first.
I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.
We made a fake repo with fake bounties, and the bots are applying fake PRs, so we know who is fake, and we can ban them from the Coolify repo.
IQ over 1000
Vercel will be officially sponsoring https://t.co/QF7eOed81b. That's a given. We as a community and industry owe @adamwathan and team a lot. Tailwind is foundational web infrastructure at this point (it fixed CSS 😉). I've also reached out to Adam to explore how we can make this a longer-term commitment.
The all new Affinity is here!
Design, edit photos and layout your work, all in one app — for free 💥
Download Affinity now on macOS or Windows: https://t.co/ezAfO0T3Ih