So it looks like I'm juggling 2 libraries, I like to be creative and front-endy sometimes and other times I prefer solving backend problems.

In the last couple of months I have gone from no open source projects to two.

I started didi to solve the problem of bundles in a world where HTTP2 prefers smaller and more requests, many people say to me, but we don't use HTTP2, but did you know for example nginx automatically upgrades to HTTP2 and so your bundles are slower than plain old ESM which didi converts.

The new project reactive-css-properties is smaller and already feature complete. But I have some sweet plans to make it even better thanks to Houdini, il tell you about that soon. Anyway reactive-css-properties will likely come under an umbrella alias: re.css which is a lot easier to say! I just finished the new logo today, take a look.

The goal of this project is to kill off "flash of unstyled content" for good, make all frontend Frameworks more efficient at handling CSS. Superchage CSS and at the same time JS and in general change the way we build for the web today. No easy task but iv got something like 400 downloads in the first week and good feedback from friends and family so that's a good start right.

How am I going to maintain them both? I'm not super human but I can plan. I use issues a lot in Didi and do everything by the book. re.css will need to catch up but it's close to the point where it will need proper management not working off master anymore. I will work on what I feel like instead of feeling creative and working on didi or technical and working on re.css. It's worth noting that didi is much more long term and BIG and needs a lot more contributors so pacing myself is the best thing I can do.

Anyway that has been my year so far trying to help the community in big ambitious ways.

Hope your all well.
Adam