Every developer has at least once in their career stumbled upon the scenario where a program would not print something as they initially thought. A few years ago, you would search for an answer on StackOverflow and find a page stating the dreaded
Consider this scenario: you re building a website that has a classic navbar at the top, this navbar has a button that reflects the user authentication status, showing a "Profile" button if the user is authenticated and showing a "Login" button in case the user is unauthenticated.
Playtomic is probably the biggest application for booking tennis/padel courts in Europe. Every club that I go to is on Playtomic and that makes it very easy to book a court or look for upcoming matches. The app is great, which I guess is why it s so popular.
In a previous [0] post I ve discussed why I ditched sea-query and why sql is almost always the best way to not re-learn something new from the beginning that will inevitably end up slowing you down or simply not working at all in the long run.
Query builders and ORMs have been around for as long as I can remember, each serving different purposes. ORMs, for example, allow you to focus on application logic without worrying about SQL or database intricacies. However, this convenience comes at a cost—using an ORM almost always means losing control over what’s happening in your database. That’s a trade-off I’ve never been willing to make in…
Askama implements a template rendering engine based on Jinja. It generates Rust code from your templates at compile time based on a user-defined struct to hold the template s context.
Lately I ve been working on Ulry, after tiressly trying to make Next.js work for me, I realised it wasn t the right fit (I m not alone). I decided to make a U-turn and go all in with Rust and SSR.