Chicos, no tuiteéis muy alto que está la web de Renfe durmiendo.

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.

A good read and unfortunately rings true for too many EU-HQ'd companies: "the expectation that in Europe the transition from individual contributor to a managerial track is the "natural" career progression" For a standout tech company you want SOME eng > managers eg in €€

Matt from Merlyn led a session during last week's Region 4 Digital Learning Conference in Houston, TX! 🤠

See how both teachers and students are using Merlyn in the classroom.

I spent 10 years building Android apps natively. Compose, XML layouts, Material Design since version 1. The one thing that always frustrated me? Asking AI tools for help and getting Material Design 2 with random teal everywhere. So I built the Material Design 3 Skill for Claude. 30 components. Compose, Flutter, Web. Full MD3 Expressive support. Built-in audit scoring to check if your UI is actually following the spec. It's free. It's open source. And it finally makes AI understand what modern Android UI should look like. Try it github.com/hamen/material-3-… What's the worst AI-generated UI you've ever seen?

Os pongo en contexto: mi padre tiene demencia pero aún sale solo a la calle llevando un dispositivo GPS. Salió esta tarde, a las 20:00 aún no había vuelto. La APP desde la que puedo ver si localización no abre en el móvil. Escribo al servicio técnico pidiendo

This is awful. Stand with @Cloudflare in Italy. I wish they win the legal battle. Censorship doesn't belong in 🇪🇺 Europe.

Q1 2026: -10 conferences -US → London 🇬🇧 -1,000 conversations and live demos The energy when teachers see Merlyn live = everything. We’re just getting started. 🚀

Companies are building internal leaderboards to track who burns the most AI tokens. They're calling it "tokenmaxxing." Management is gamifying LLM usage like it's a step-count challenge on a company Fitbit. I've seen this movie before. We learned nothing

Well taken care of and always nearby 🐯 Merlyn making appearances in lectures at Tartu University.

–O sea, que Skynet vencerá porque las máquinas se harán más inteligentes. –No, no. No hará falta porque los humanos seréis cada vez más gilipollas. Nuestro líder es una Nespresso.

St. Joseph’s National School is the first school to have Merlyn Origin in every classroom in Ireland. 🇮🇪 “Merlyn will help teachers and children work around the classroom and they will not be tied down to their computers.” — Dr. Roz Morris Thank you to Joe Rafus, Ian, and Principal Dr. Roz Morris for helping lead this milestone!

Destructuring has been a popular feature in Kotlin, but since it's been based on position, it comes with some risks. But with Kotlin 2.3.20, you can eliminate many of those risks! Here's what I mean... Since destructuring is based on position, the order of your variables needs to match the order of the components (such as the data class constructor properties). If you accidentally swap around a few of them, you could end up with some surprises, and it's easy to do, especially when several of the components have the same type! But with Kotlin 2.3.20, you can now enable an experimental feature to use name-based destructuring instead! When activated in "complete" mode, the syntax we've been using up until now will match based on name rather than position. This means you can get them out of order, and it still works. If you use a name that doesn't match, you'll get a compiler error. But for those cases where you actually wanted a different name, you can use a new syntax to assign the component to a different name: val (title, cost = price, author) = book Prefer to use the classic, position-based destructuring? You can use brackets instead of parentheses, like this: val [author, cost, title] = book The bracket syntax brings along some connotations of collections, which seems fitting, since position-based destructuring could still be helpful for things like Pair and List. It's still experimental, and there's a full migration path planned out, but you can activate it today with a compiler argument. What do you think about this feature Do you like the new syntax? Have you run into issues with position-based destructuring in the past? #Kotlin #AndroidDev

Unveiling our new startup Advanced Machine Intelligence (AMI Labs). We just completed our seed round: $1.03B / 890M€, one the largest seeds ever, probably the largest for a European company. We're hiring! [the background image is the Veil Nebula - a picture I took from my backyard, most appropriate for an unveiling] More details here: techcrunch.com/2026/03/09/ya…