lukeed has several extremely popular npm packages/libs which share a lot in common: - their twitter following is used to boost newly released packages - they

lukeed has several extremely popular npm packages/libs which share a lot in common: - their twitter following is used to boost newly released packages - they were released as alternatives to existing packages/libs with the flashy promise of being smaller, less complicated, faster - negative feedback is rebuffed as "an attack" - they're all very green - they lack features and stability of the more mature packages they aim to supplant - once released and popular, they cease getting frequent updates Now, yes this is a generalization. It doesn't apply to all of their packages, and not at the same point in time. But there is a pattern there. Some quick diving into the author's Github account, and their more popular repos shows the pattern. It's also clear that this was a choice made by a Svelte contributor to use their own package for "official" support in Svelte Kit. When it comes to polka itself, I just don't get why a maturing framework like Svelte would choose something whose only real advantage lies in micro-benchmarking porn [1]. Speculation aside, I'm surprised the Svelte team didn't look at that choice through a lens of higher scrutiny. Koa would have been an infinitely better choice in my personal opinion, and there are several community-driven setups [2][3] for it. [1] https://github.com/lukeed/polka#benchmarks https://github.com/lukeed/polka#benchmarks [2] https://github.com/kaladivo/svelte-kit-koa-boilerplate https://github.com/kaladivo/svelte-kit-koa-boilerplate [3] https://blog.logrocket.com/sapper-svelte-tutorial-2021/ https://blog.logrocket.com/sapper-svelte-tutorial-2021/