@ematipico.xyz
Senior Software engineer at @cloudflare.social . @biomejs.dev creator and lead - @astro.build core and TSC. Follow the 🦀
@ematipico.xyzThe reimplantation is completely fine if the ecosystem is a stale state. Look at those validation libs. They were stuck. Now we have new, powerful ones!
@ematipico.xyzRight. This reminds me I need a good night of sleep.
@ematipico.xyzIt happened like today or yesterday. No, nothing worth highlighting other than the race at making things faster. If they are faster
@ematipico.xyzIt's been merged recently, so it will probably hit production soon
@ematipico.xyzI would throw Deno in the bucket too. I think the pressure of both competitors helped
@ematipico.xyzBun just landed a formatter in their code base. It's a slopfork of oxfmt. Oxfmt uses a fork of @biomejs.dev
Biome uses the same IR of Prettier, and printer heuristics. However Biome adds stuff that Prettier doesn't have.
Happy to see that Biome, in a sense, is shaping the next gen of formatters
@ematipico.xyzThere's also the fact that there's no breakthrough in this mess. Everything is just a port of what already exists. Open source is supposed to be exciting because you get to see, create and try new things.
@ematipico.xyzLet's wish him all the best
@ematipico.xyzNo, it's not easy. I've done this with Biome (from Rome). I wasn't alone, a team was there to help me. It took us months. We had to rebuild a new identity. I couldn't have done it alone. I'm glad I found people that believed in the mission and helped to create a new community.
@ematipico.xyzI called this the same day celld was open sourced! Unfortunately the Deno company didn't succeed, but the runtime is there up for grabs!
@ematipico.xyz@ematipico.xyzI doubt the GIMP team decompiled Adobe
@ematipico.xyzI wish they were! It was 200KB versus 9MB! 😬 Totally agree about the rest
@ematipico.xyzI suppose you guys also have a strong testing infrastructure that provides confidence. I don't want to diminish your awesomeness, though! It's still a great achievement!
@ematipico.xyzNeither do I, but I just experienced that (I was adopting a framework that uses TW). What "effort"? In the end, what I see is that both the employer and the customer pay the final price
@ematipico.xyzI have had a completely different experience. Page weight increases massively, especially for pages with a lot of HTML. Sure, compression helps, but it doesn't give me any win. It's still too big compared to classic CSS
@ematipico.xyzWhat's so great about Tailwind? Please don't tell me "styles that work everywhere"; I don't buy it. It ends up shipping an HTML page full of classes, which increases the page weight that customers have to download. That means more money, more bandwidth, and slower load times.
@ematipico.xyzI'm really happy to see that @astro.build donations haven't been stopped, and they increased a bit since the TATC (the company behind Astro) was acquired back in January.
Thank you for all the donations, the project is thriving!
@ematipico.xyzWhen was the last release? Months ago? It's alive!
