iiinova — where your digital self keeps evolving

Emanuele (Ema) @ematipico.xyz · 07/10/2026

I doubt the GIMP team decompiled Adobe

010

Emanuele (Ema) @ematipico.xyz · 07/10/2026

I wish they were! It was 200KB versus 9MB! 😬 Totally agree about the rest

100

Emanuele (Ema) @ematipico.xyz · 07/10/2026

I 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!

110

Emanuele (Ema) @ematipico.xyz · 07/10/2026

Neither 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

100

Emanuele (Ema) @ematipico.xyz · 07/10/2026

I 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

100

Emanuele (Ema) @ematipico.xyz · 07/10/2026

What'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.

920

Emanuele (Ema) @ematipico.xyz · 06/10/2026

I'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!

1150

Emanuele (Ema) @ematipico.xyz · 06/10/2026

When was the last release? Months ago? It's alive!

100

Emanuele (Ema) @ematipico.xyz · 06/10/2026

Yeah. That's what I've been doing in one of my projects: I briefly look at the PR and if it's slop, I close it straight away. Fortunately there are instances where I don't even need to look at the code.

110

Emanuele (Ema) @ematipico.xyz · 06/10/2026

To give a counter point, isn't a PR a form of proposal, and a way to open a discussion too? Assuming there's no issue to start with

120

Emanuele (Ema) @ematipico.xyz · 06/10/2026

Well put. Funnily enough, it's a problem that only React apps have.

120

Emanuele (Ema) @ematipico.xyz · 06/10/2026

Great response to why you shouldn't use CSS-in-JS.

040

Emanuele (Ema) @ematipico.xyz · 05/10/2026

No they don't. OP must open an issue and follow up, that's how maintainers get a "good signal" that the PR is worth reviewing. If thet don't get any comment or signal, they don't review the PR.

010

Emanuele (Ema) @ematipico.xyz · 05/10/2026

That's the gimmick though. You don't get real contributors anymore, but only kids playing with the new toy, or bots. There's no real interest in fixing the bug. Not sure if you're a maintainer, but that's what we have *now*

140

Emanuele (Ema) @ematipico.xyz · 04/10/2026

I have to admit, @pi.dev is amazing. I just created a plugin to launch sub-agents using Herder panels.

010

Emanuele (Ema) @ematipico.xyz · 04/10/2026

I refuse to admit that putting a limit to a password is going to increase revenue, or decrease costs. (This is sarcasm...)

000

Emanuele (Ema) @ematipico.xyz · 04/10/2026

It seems they reached out to help the Node.js team

100

Emanuele (Ema) @ematipico.xyz · 03/10/2026

Yeah, true. Many of them, unless they are heavy tech orientated companies, always want to see something in return

000

Emanuele (Ema) @ematipico.xyz · 03/10/2026

Give it some thought, because I think your project is very good, and by restricting the donation channels (in terms of visibility) you're closing the door to many more possible backers. The tax part is a mood killer, I understand that, however the OC team is great and offer great support

110

Emanuele (Ema) @ematipico.xyz · 03/10/2026

In my past experiences, I've had companies refusing GitHub because it requires an account, given a headache to the finance departments. OpenCollective gives less restrictions to companies that have less GitHub visibility.

100

Emanuele (Ema) @ematipico.xyz · 03/10/2026

Ah. Counter proposal then: make Open Collective more evident from the new page. I landed on that page and site for the first time, and my attention was caught by GitHub sponsorship only. Maybe it's intentional because you value GitHub more. Fair. My advice is to make Open Collective as evident

110

Emanuele (Ema) @ematipico.xyz · 03/10/2026

Suggestion: you might want to consider adding Open Collective to your channels to collect sponsorships. Companies prefer it to GitHub for many reasons. As proof, Astro receives many donations, and the majority come from Open Collective. Sure, they need a fee, but it's worth the cost.

140

Emanuele (Ema) @ematipico.xyz · 02/10/2026

You're not the only one my friend!

000

Emanuele (Ema) @ematipico.xyz · 02/10/2026

Biome doesn't have a TOML parser yet, we can't support one. If and once there's one, the option will be on the table to discuss

010

Emanuele (Ema) @ematipico.xyz · 02/10/2026

Yeah I'm aware of the Norway problem 😅 (and the rest)

001

Emanuele (Ema) @ematipico.xyz · 02/10/2026

Ironically, I also don't like that style. It's the worst

000

Emanuele (Ema) @ematipico.xyz · 02/10/2026

I love this feedback, thank you! 😊 BTW, _if_ it gets supported, Biome will use its own YAML parser

130

Emanuele (Ema) @ematipico.xyz · 02/10/2026

What are your thoughts about supporting biome.yaml as @biomejs.dev configuration file?

900

Emanuele (Ema) @ematipico.xyz · 30/09/2026

HTML formatter is up to 4x faster, thanks to @codspeed.io We're almost ready for the next minor.

0111

Emanuele (Ema) @ematipico.xyz · 30/09/2026

The motivation: "If nowadays people just send automated PRs, at this point I prefer to automate them myself so I can overview things"

041

Emanuele (Ema) @ematipico.xyz · 30/09/2026

The flue project has an interesting take. It doesn't accept PRs (except for a few). PRs are transformed into discussions and then iterated by an agent and supervised by the owner of the project.

110

Emanuele (Ema) @ematipico.xyz · 27/09/2026

The AI is trained with data in the open. Which means the majority of apps out there use this crap.

120

Emanuele (Ema) @ematipico.xyz · 25/09/2026

I've seen Biome stickers 👀 let's spread the gospel! 🤣

240

Reposted by Emanuele (Ema)

James @43081j.com · 24/09/2026

Today we're launching ai-policy.dev! A collaboration of me, @danielroe.dev and @matteogabriele.npmx.social - this provides a few human curated AI contribution policies you can choose from. Our hope is that this will help you better define your stance and what kind of contributions you accept 🙏

ai-policy.dev

AI Contribution Policies

Ready-to-use AI contribution policies for open source projects.

1313540

Emanuele (Ema) @ematipico.xyz · 25/09/2026

A radical move would be to use a platform that shares your values. GitHub's values are gone. The social factor is now a shadow of the past, and AI is all over.

231

Emanuele (Ema) @ematipico.xyz · 24/09/2026

Damn, that's sooooo bad!

100

Emanuele (Ema) @ematipico.xyz · 23/09/2026

That's fucked up on so many levels. Is this reality? Someone give me the meme

321

Emanuele (Ema) @ematipico.xyz · 23/09/2026

They could have added support for python and cargo via additional packages.

030

Emanuele (Ema) @ematipico.xyz · 23/09/2026

I bet they don't even know their agent generated that badge.

010

Emanuele (Ema) @ematipico.xyz · 23/09/2026

The @biomejs.dev analyser has reached FIVE lifetimes! If it's not a record, we're getting there

010

Emanuele (Ema) @ematipico.xyz · 22/09/2026

It's not needed. None of that is needed. Ruff and OXC do just fine without it (they use AST). It's preferable to me, because you get all the information about the code, and you create a better debugging harness.

100

Emanuele (Ema) @ematipico.xyz · 22/09/2026

I hate to be that guy: that's Astro's old logo.

130