11–20 of 148 posts
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.
I used to think my distaste for new and upcoming Javascript frameworks is a sign of getting old and not being as adaptable as I used to. But nowadays my thinking has shifted to seeing it as a instant loss of productivity with little upside.
Just like musicians don't switch instruments every time they see something shiny. Neither should we, or at least without feeling guilty about it. Mastery takes time.
Backend app boiler plate [dependencies] already setup for anyone wanting to build backends in kotlin
git clone https://gitlab.com/asad-awadia/kotlin-server-app.git
On the back end, for small projects, using a full-fledged framework is usually overkill. Writing a simple API that reads and write normalized data is quite trivial, and when one is writing everything it's easier to understand what's going on.
By this I mean that some behaviors come from the framework and can sometimes surprise you. For example, in Backbone, change events on the model are triggered not when an instance is updated, but only if the new version is different from the old. This makes sense, but the problem is that the comparison is only done on a shallow level. When updating deep properties, no change event is triggered. This took me some time to figure out.
Light frameworks have fewer unexpected behaviors, by virtue of being small.
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…
Still, I’d recommend it for small projects where you need binding.
[1] https://github.com/sebastianconcept/Mapless [2] https://github.com/sebastianconcept/lobster-ui
For SPAs I still use Backbone.js... Yes, I know, 2014 called and it wants its framework back. But... I like it. It's lightweight and doesn't impose any particular style or philosophy. It's well suited to small projects. On the back end, for small projects, using a full-fledged framework is usually overkill. Writing a simple API that reads and write normalized data is quite trivial, and when one is writing everything…
PHP: CakePHP This was the very first framework I learned when I first learned PHP, and it has always just been so incredibly _easy_ to accomplish most common MVC tasks that I've stuck with it. I've become quite the expert in the framework over the years, even managing to make it bend quirky ways that it was not meant to in service of business goals. That has made me an extremely valuable resource for companies using…