I personally use Svelte(Kit), as it's simple and straightforward. I was planning on learning React, but the fact that it's owned by Meta really holds me back.
Next.js would be great if it weren't because of all the conflict of interests that make it have artificial limitations and the shady "features" it has and it were not driven by a marketing company.
Being owned by Meta (or Facebook at the time) was a selling feature for me when settling on it. The main reason being that they use it heavily internally, and have a vested interest in its success as a result. They've built it to meet their needs, dogfood features internally, and feel the same pain as everyone else when it comes to breaking changes and backwards compatibility.
This gave me a lot of confidence in React compared to other frameworks at the time I was evaluating it. It turned out to be a great choice now 8+ years later, and I feel the same way today.
Still? :) Don't get me wrong, I used to use CakePHP as my primary framework 10-15 years ago and loved it, but even then it was starting to lose traction as competition heated up in the PHP space.
How's your experience with CakePHP these days?
Also I am surprised to not see that many people replying with Laravel on this thread.
VanillaJS/Angular for frontend, .NET Core/Node for backend.
It shouldn't matter too much if a framework is being backed by Meta. If there's enough support, documentation and easy-to-find-answers for it, then it's probably a good choice. Just make sure the code is readable and the framework's concepts are simple and easy to understand.
Struts and JSPs with some hand-crafted JS and CSS (no JS frameworks). At least that's what I was using back when I did any semblance of front-end web development. Yes, I'm old and no I don't do it anymore! But I do work with a lot of folks on my team who use React for our web UI.
astrojs (with some React) for presentation website, nextjs for anything else. For backend, I use Django if the project is complex or Go frameworks for micros.
None. I write my own frontend, backend, db engine, libraries. Not completely of course, like I would still rely on Express and other heavy lifting when doing a node backend. If I need some special feature in the frontend I hunt for a library I can easily copy to my libs/ directory, but half the libraries that are used I wrote myself.
Gatsby built and served Netlify. I love how its trivial to make hundreds to thousands of static pages with various react components and templates (mind you static doesn't necessarily mean you can't load outside data with an API)
With just a few Gatsby plugins & some tinkering, you can get a workflow that produces sites where each page has a 100 across the board on lighthouse
Are you building a highly interaction frontend application? I mean an actual application? Or is it static with some interactive components? CSS can go far these days. And you can always add little interactivity with a script tag on the page.
It’s built by the team that created the popular react router library, which has over a billion downloads since it was published;
It brought the joy of programming back for me, but more importantly it solves lots of typical headaches in react and helps me ship faster and with right amount of abstraction and levers to pull
If you’ve used react router, all that knowledge transfers over, if you have a react SPA with react router, very little to learn
Great for Frontend UI teams, but, it’s simple enough in my observation that several SRE & traditionally pure backend teams who’ve never built UIs at my company have adopted it for building their own internal tools & UIs
Deployable on all major platforms that I know, whether it’s serverless or not
I use the remix with expressjs template at work and for personal projects
I started using remix a while back and man, it feels really refreshing in the javascript ecosystem. It feels like they really have hit all the sweet spots that you are used to if you come from an older framework like rails/laravel/django.
Even frameworks like Nuxt or similar kinda solves the same issue but they always seem more front end focused and kinda leaves the database layer up to the developer. I love that Remix takes a stance here and helps you get going.
You have everything you need to get started quickly and the performance is great. It's also really easy to extend functionality with packages and seems like there is very few things that you'll miss.
64 comments
[ 1.9 ms ] story [ 122 ms ] threadMay I ask why? React starts there, but it will probably survive Meta. Its a great framework, IMO.
For me it is an absolute no.
This gave me a lot of confidence in React compared to other frameworks at the time I was evaluating it. It turned out to be a great choice now 8+ years later, and I feel the same way today.
Middleware::from_fn was a life saver in the current version, middleware was kind of annoying before that was added.
Would prefer something more like graphul but haven't given it a shot yet.
How's your experience with CakePHP these days?
Also I am surprised to not see that many people replying with Laravel on this thread.
It shouldn't matter too much if a framework is being backed by Meta. If there's enough support, documentation and easy-to-find-answers for it, then it's probably a good choice. Just make sure the code is readable and the framework's concepts are simple and easy to understand.
But that’s only frontend, what middleware/backend do you like to pair them with?
Symfony with PHP
With just a few Gatsby plugins & some tinkering, you can get a workflow that produces sites where each page has a 100 across the board on lighthouse
I’ve used it for nearly 2 years in production
Highly recommend this video if want a good primer on the problem it solves: https://youtu.be/95B8mnhzoCM?si=EzKwMLbJW2602PJI
It’s built by the team that created the popular react router library, which has over a billion downloads since it was published;
It brought the joy of programming back for me, but more importantly it solves lots of typical headaches in react and helps me ship faster and with right amount of abstraction and levers to pull
If you’ve used react router, all that knowledge transfers over, if you have a react SPA with react router, very little to learn
Great for Frontend UI teams, but, it’s simple enough in my observation that several SRE & traditionally pure backend teams who’ve never built UIs at my company have adopted it for building their own internal tools & UIs
Deployable on all major platforms that I know, whether it’s serverless or not
I use the remix with expressjs template at work and for personal projects
Even frameworks like Nuxt or similar kinda solves the same issue but they always seem more front end focused and kinda leaves the database layer up to the developer. I love that Remix takes a stance here and helps you get going.
You have everything you need to get started quickly and the performance is great. It's also really easy to extend functionality with packages and seems like there is very few things that you'll miss.