I think it really depends which language you want to write. There are good options available in most of the major languages, but they vary in capabilities. Ruby on Rails is certainly a solid...
I think it really depends which language you want to write. There are good options available in most of the major languages, but they vary in capabilities. Ruby on Rails is certainly a solid choice, so if you're interested in it and have already started getting into it, I think it's totally reasonable to just continue. But as a couple other options:
If you're interested in Python, the main choices are probably between Django (which comes with almost everything included), and Flask (which comes with almost nothing included). They're both great in different ways. Tildes uses Pyramid, which is a bit more in the middle—it's more complex to use, but includes a lot of nice capabilities and extensibility.
If you're looking for something more "interesting" (and picking based on "interesting" isn't necessarily a good choice if you just want to get things done), I see a lot of positive talk about Phoenix, which uses the Elixir language, an extension of Erlang.
Django (Python), Ruby on Rails (Ruby) and Laravel (PHP) are the three major web frameworks right now. You'll be quickly up to speed on any of them. Personally, I'd say Python has more of a future...
Django (Python), Ruby on Rails (Ruby) and Laravel (PHP) are the three major web frameworks right now. You'll be quickly up to speed on any of them.
Personally, I'd say Python has more of a future than Ruby given its massive uptake in the ML/AI community; so if you're just starting I'd recommend Django over ROR.
TypeScript has a brighter future than either of them, but it also doesn't have any decent web framework support.
Does node not count as a significant web framework? Regardless of what you think of it many major companies, from Goldman Sachs to Netflix and Uber use node in production.
Does node not count as a significant web framework? Regardless of what you think of it many major companies, from Goldman Sachs to Netflix and Uber use node in production.
Node does not count as a web framework any more than uwsgi does. I use node plenty but I dislike the JS community's fascination with calling it a web framework on the level of Django. Same for...
Node does not count as a web framework any more than uwsgi does.
I use node plenty but I dislike the JS community's fascination with calling it a web framework on the level of Django. Same for Express, which sits slightly higher.
I'd say Node totally counts a significant web framework; and I can only see it continue exploding in popularity as so many more companies choose to go the serverless/lambda route with a...
I'd say Node totally counts a significant web framework; and I can only see it continue exploding in popularity as so many more companies choose to go the serverless/lambda route with a microservice-oriented architecture; which Node lends itself very well to.
.NET Core is pretty nice. The configurable inversion of control service container and dependency-injection into controllers is much nicer and cleaner than working with ASP.NET of ye' olde days,...
.NET Core is pretty nice. The configurable inversion of control service container and dependency-injection into controllers is much nicer and cleaner than working with ASP.NET of ye' olde days, and the dotnet CLI tool is dare I say, even good. There's a lot of verbosey confusing MS stuff still, like their approaches to authentication and authorization, the documentation is still less good than competitors, but it's come into its own with .NET Core 2 and 3. Like @reese I'm surprised you didn't just spring for that.
I've gotten back into the groove of developing with Laravel 6, which is my preferred framework at the moment. PHP 7.x is a significant step forward from what the language used to be, and the coverage of developer documentation, framework flexibility, and package support for services (Stripe, Elastic, Algolia, AWS, etc etc) is up there with the very best. You won't find yourself struggling at all.
I sadly don't have the time to spend all day learning new frameworks, but I'd be looking in the direction of Go and Rust for what's upcoming, too.
There are a lot of choices and I haven't kept up with them. But here is a basic question to consider: how much code do you want to run in the browser versus on the web server? There are frameworks...
There are a lot of choices and I haven't kept up with them. But here is a basic question to consider: how much code do you want to run in the browser versus on the web server? There are frameworks that handle either one or the other, and there are also frameworks that do both. Some people like to use different languages in the browser versus on the server, and some like to use the same language and share some common code between them.
Some people like to structure things so that the web app makes RPC calls to servers and the web app itself is just a static website (with a lot of generated JavaScript). If you do that, GraphQL seems to be a modern way to structure the RPC layer.
On the other hand, if your static website doesn't contain any interesting text then search engines aren't going to find much of anything to index, so there is something to be said for minimizing the amount of JavaScript if your website is primarily about providing publicly accessible text. But if the website is hidden behind a login then it doesn't matter.
I think it really depends which language you want to write. There are good options available in most of the major languages, but they vary in capabilities. Ruby on Rails is certainly a solid choice, so if you're interested in it and have already started getting into it, I think it's totally reasonable to just continue. But as a couple other options:
If you're interested in Python, the main choices are probably between Django (which comes with almost everything included), and Flask (which comes with almost nothing included). They're both great in different ways. Tildes uses Pyramid, which is a bit more in the middle—it's more complex to use, but includes a lot of nice capabilities and extensibility.
If you're looking for something more "interesting" (and picking based on "interesting" isn't necessarily a good choice if you just want to get things done), I see a lot of positive talk about Phoenix, which uses the Elixir language, an extension of Erlang.
Django (Python), Ruby on Rails (Ruby) and Laravel (PHP) are the three major web frameworks right now. You'll be quickly up to speed on any of them.
Personally, I'd say Python has more of a future than Ruby given its massive uptake in the ML/AI community; so if you're just starting I'd recommend Django over ROR.
TypeScript has a brighter future than either of them, but it also doesn't have any decent web framework support.
Does node not count as a significant web framework? Regardless of what you think of it many major companies, from Goldman Sachs to Netflix and Uber use node in production.
Node does not count as a web framework any more than uwsgi does.
I use node plenty but I dislike the JS community's fascination with calling it a web framework on the level of Django. Same for Express, which sits slightly higher.
I'd say Node totally counts a significant web framework; and I can only see it continue exploding in popularity as so many more companies choose to go the serverless/lambda route with a microservice-oriented architecture; which Node lends itself very well to.
.NET Core is pretty nice. The configurable inversion of control service container and dependency-injection into controllers is much nicer and cleaner than working with ASP.NET of ye' olde days, and the dotnet CLI tool is dare I say, even good. There's a lot of verbosey confusing MS stuff still, like their approaches to authentication and authorization, the documentation is still less good than competitors, but it's come into its own with .NET Core 2 and 3. Like @reese I'm surprised you didn't just spring for that.
I've gotten back into the groove of developing with Laravel 6, which is my preferred framework at the moment. PHP 7.x is a significant step forward from what the language used to be, and the coverage of developer documentation, framework flexibility, and package support for services (Stripe, Elastic, Algolia, AWS, etc etc) is up there with the very best. You won't find yourself struggling at all.
I sadly don't have the time to spend all day learning new frameworks, but I'd be looking in the direction of Go and Rust for what's upcoming, too.
There are a lot of choices and I haven't kept up with them. But here is a basic question to consider: how much code do you want to run in the browser versus on the web server? There are frameworks that handle either one or the other, and there are also frameworks that do both. Some people like to use different languages in the browser versus on the server, and some like to use the same language and share some common code between them.
Some people like to structure things so that the web app makes RPC calls to servers and the web app itself is just a static website (with a lot of generated JavaScript). If you do that, GraphQL seems to be a modern way to structure the RPC layer.
On the other hand, if your static website doesn't contain any interesting text then search engines aren't going to find much of anything to index, so there is something to be said for minimizing the amount of JavaScript if your website is primarily about providing publicly accessible text. But if the website is hidden behind a login then it doesn't matter.