Ask HN: Best web framework in 2018
31–40 of 41 posts
Re: Ask HN: Best web framework in 2018
#32However, I'd like to highlight ASP.net Core + Angular + Visual Studio here. Microsoft appeasement towards Open Source and cross-platform made this a solid choice. As web apps grow steadily in complexity, a modern strongly typed language like C# (and TypeScript) might be helpful for architectural patterns. And, last but not least, the tooling around the Visual Studio product family is maybe best in class.
I am saying all this as someone who has not touched any Microsoft product for years.
Re: Ask HN: Best web framework in 2018
#33React/Redux +.NET CORE backend,Postgres for the DB is one of the best choices i use
How is React superior to Angular in your use cases?
Re: Ask HN: Best web framework in 2018
#34React/Redux +.NET CORE backend,Postgres for the DB is one of the best choices i use
I've always had the feeling that Angular is the better choice for .Net, since it's TypeScript by default and far more opinionated than React (as well as .net core mvc is an opinionated framework). How is React superior to Angular in your use cases?
Re: Ask HN: Best web framework in 2018
#35Write your application in Python/Django. Your concern should be getting to market fast, not which tech should I choose.
Re: Ask HN: Best web framework in 2018
#36LAMP
Re: Ask HN: Best web framework in 2018
#37Stick with what you know for the parts that don't absolutely require another solution; not all (parts of) pages will be so interactive. Then branch out a bit where needed, e.g. to handle socket connections well. Maybe not all of that needs to be handled by the same service?
If you move the semi-realtime stuff into a separate project, it will be a lot smaller in scope, hence less risky to experiment with. Regardless, I wouldn't stray too far. If you'll be writing Javascript anyway, NodeJS could still be fine, but don't needlessly bring in a third language. Do try Channels, but don't overlook other Python solutions. Tornado is a workhorse that doesn't get nearly enough credit in my opinion.
Re: Ask HN: Best web framework in 2018
#38I'd say rails because the nodejs + PHP codebases I've seen aged poorly, but the rails one are still clean. The problem with node is that things move too fast. What was beautiful in JS 4 years ago now looks like legacy mainframe fortran. Laravel (a popular php framework) is nice at one point in time, but even 0.x.0 migrations will break you application and force you to work for hours...
I came from Rails to Laravel. It has a similar feel and in some ways is more fun to work with.
Part of that is the great community and lots of make your life easier features. Especially Laravel Forge and Envoyer. Forge makes spinning up servers easy and secure and deployments a breeze. Envoyer adds zero down time deployments.
These are both paid SaaS but they fund the development of the framework and provide way more value than the monthly cost.
Laracasts is also great for getting up to speed with Laravel.
Re: Ask HN: Best web framework in 2018
#39A product’s success has nothing to do with which language or framework you choose. They are there to help you develop something that works as per your needs.
You mentioned your product deals with chat messaging. So I would suggest using something like NodeJS + SQL for the backend. NodeJS for its ability to handle high volume of events. SQL for managing the chat history of each person in a relational way.
My two cents worth :)
Re: Ask HN: Best web framework in 2018
#40If your startup is for consumers and you don't have a good estimate of your growth or you don't know how fast your app will need to scale, then make sure you can hire people who know quickly. Your hiring skill will be more important than your tech.
Also, if the complexity of your app is low or medium, consider your first implementation as a prototype that - given growth happens - can be replaced with a faster stack relatively simple.
If high concurrency is needed, you'll bump into frameworks focusing on async I/O. Java and C++ implementations are the leader here. (see techempower benchmarks for more information).
If you can commit to a datastore (and you rarely make a mistake by choosing PostgresQL), then replacing your prototype down the road is easier.