PHP: usually you only need routing, not the whole kitchen sink; check out slim.
Ask HN: Web frameworks – which less popular frameworks are you using and why?
41–50 of 148 posts
Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#42Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#43Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#44I made it because I don't like all the existing frameworks. That said, it uses Laminas Diactoros because not using that would be to reinvent the wheel.
Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#45I don't think I've ever had so much _fun_ writing a web app before :)
Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#46Out of curiosity, which is the best framework to learn in 2022? 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!
Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#47Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#48PHP - I found new love for 1) Nette https://nette.org/en/ 2) Phalcon https://phalcon.io/en-us If you agree, we should talk :)
Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#49From the author of the Sequel gem. It can do everything that Rails can, faster and lighter by order of magnitude, expandable (turn on only the plugins you need), and it does it all 'the Ruby way', not 'the Rails way'. That means simplicity, clarity and power. Generally, all software Jeremy Evans releases is of excellent quality and actively supported. Oh, and this Roda framework is in active use by the US government and is subject to regular security audits...
The definition of obscure but powerful and quite beautiful web framework.
Re: Ask HN: Web frameworks – which less popular frameworks are you using and why?
#50Working with Elm code is satisfying to me. It's generally easy to revisit code I last worked with months ago and get immediately fluent with it again. The "Elm Architecture" (model / update / view) with all external interaction done over "ports" is so clean (albeit with boilerplate). Integrating with JS libraries has to be done over ports (async one-way messaging) but it works well enough in practice. Vite provides a decent dev/build toolchain with hot-reloading of all Elm, JS, and CSS code. The Elm framework is very opinionated and has stopped evolving, but it's mostly a joy to work with.