31–40 of 148 posts
Rust: Warp. I like Warp because it's akin to a layer on top of Hyper (for HTTP) and Tokio (for async), and can go down into these deeper layers as you wish. I'm using Warp now because I'm trying all the Rust web frameworks. I like Rust Actix for larger production projects that favor a more-long-term ecosystem. I like Rust Rocket for its user-friendly ideas and superb tutorials for onboarding.
Zola is a single-executable static web-framework like Jekyll.
a) Python-Django? b) Ruby? c) Other?
I already know python, and I would like to learn a framework to build MVC's for startups!
Javascript: SvelteJS Using it for some personal projects with Vite and it is a breath of fresh air. I use React for work during the day, but coding in Svelte just brings me joy.
1) Nette https://nette.org/en/
2) Phalcon https://phalcon.io/en-us
If you agree, we should talk :)
It was mired in controversy a while back but now it's one of the most feature complete frameworks available. I've been following the book zero2prod.com which implements an API service via actix-web as a way to learn Rust and backend web development in general, which is nice.
JS - I still have a tiny bit of MooTools in production because I have found some more complex animations nearly impossible to port to pure css without resorting to horrible hacks. It really had an amazing animation “Fx” toolkit, but given it’s nature of prototype pollution, it design as essentially a patch to the language rather than a framework, you really should not use it these days.
Remix seems to use an approach similar to Hotwire Turbo Frames and a syntax of React JSX. This allows creating composable pages and loading partials in a page while still being able to create React components.
The main use case for me is web3 where almost all libraries are in Javascript. And I want to have the least friction for this move. It basically encapsulates the server and client side of an HTTP request in a single component and handles the json parsing operations under the hood.
You can argue that it might not necessary and a template engine can come much handier. I believe NestJS handles that but if you need the React JSX and reusable components it can be quite practical.
Javascript: SvelteJS Using it for some personal projects with Vite and it is a breath of fresh air. I use React for work during the day, but coding in Svelte just brings me joy.
Obviously, it comes with constraints. You can't really swap out parts/libraries if you find a better one to suit some need. And you can't really stray too far from the beaten path; you have to do things The Ember Way. But the consistency and organization made for a really nice developer experience.
Also, I found the community really friendly and welcoming, which has not been my experience in the wider JS world.
I've tried FastAPI recently, as the idea matured, I came to regret the decison. It's not bad, in fact it was very pleasant to get started with, yet I found myself missing and reinventing the wheel as compared to django. I develop with Django since 2015 (1.6 or so), to me it is the goto for any web related project. I used to think my distaste for new and upcoming Javascript frameworks is a sign of getting old and not…
I couldnt agree more with this statement. FastAPI was good for the prototype. Then when you want to go and do something a bit more complicated, it becomes a hinderance more than a help.