vite-handlerbar-htmx VS ffts

We've made a starter template with minimal dependencies available at https://github.com/stormkit-io/monorepo-template-react. Instead of opting for frameworks like next.js, you have the flexibility to use this template, which is platform-agnostic.We have another template built with htmx, outlined in detail at https://stormkit.io/blog/building-dynamic-web-applications-w.... You can find the corresponding template at https://github.com/stormkit-io/vite-handlerbar-htmx. I mainy work with Ruby and Go. I have some Nodejs projects like discord bot and whenever I update my dependencies something breaks. I find that managing dependencies in ruby and go is comparatively smoother for me.

You might as well assume (c) whenever you use a library provided free of charge. Be prepared to either fix the bugs yourself or make sure there are alternatives you can use as a replacement. Even if the author is responsive now, there's no guarantee you'll get help once your code is in production a few months later. The library might even be archived at that point.

Lets say you've used FFTS, the Fastest Fourier Transform in the South [0]. Performance is spectacular, but now it's no longer supported and you find a bug. The code is impressive: Thousands of lines of code that dynamically generate SIMD instructions. But it's impossible to understand. You have chosen a library you cannot repair yourself. This is fine when there's alternatives, and there are for FFTs, and they are easy to swap out. If you can't easily swap out one library with another, you better make sure that you can repair it yourself.

[0] https://github.com/anthonix/ffts

I quite like ffts. Compared to fftw, it has a similar interface, a more permissive license, and as far as I can tell, it has fairly comparable performance.