Go for what works for you, a popular stack may not necessarily be best for you unless you, at least, have experience with the technologies. My current default stack.
Frontend: Vuejs (pwa)
Backend: Go (exposes json api endpoints for frontend)
DB: mariadb / sqlite
Ask HN: What stack should I use to build my basic web app as of 3/29/18
11–20 of 58 posts
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#12Basic? You need good documentation, and Philip Greenspun's book is now available for free[1]! So go with that, although you might want to swap out Oracle with MySQL -- it's from the same company anyway! AOLServer is still fine.[2]
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#13[deleted]
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#14Go for what works for you, a popular stack may not necessarily be best for you unless you, at least, have experience with the technologies. My current default stack. Frontend: Vuejs (pwa) Backend: Go (exposes json api endpoints for frontend) DB: mariadb / sqlite
> Backend: Go (exposes json api endpoints for frontend)
Do you use Swagger or sth. like that to auto-generate the boilerplate from an API spec?
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#15I use a basic LAMP stack (CentOS, Apache, MariaDB, PHP 7). No frameworks. Some of my projects are quite large (tables with billions of rows, and over a million users). It might not be fashionable, but it works, it's fast (for development, and for end-users), it's well documented, and it's been tested for decades. I have no plans to change, and my new projects in development are using the same.
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#16http://djangoframework.com is overall one of the best documented + most stable web frameworks out there.
Besides the actual functionality, that you can also get from smaller libraries, you want a framework because it gives you standard go-to solutions for many common questions you encounter when making a basic, relational database backed application (database access, database migrations, templating, forms, validation, caching, translation, etc.)
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#17http://djangoframework.com is overall one of the best documented + most stable web frameworks out there. Besides the actual functionality, that you can also get from smaller libraries, you want a framework because it gives you standard go-to solutions for many common questions you encounter when making a basic, relational database backed application (database access, database migrations, templating, forms, validation…
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#18Earlier quoted context omitted.
This would be my answer every month ( after you this time ;))
Mine too :) Most of my applications are built using Perl and the excellent CGI::Application module/framework. I've used Dancer a couple of times, but that tends to be for smaller applications, and it has to be said that the last remaining dancer application I used in production was replaced by a port to golang this morning. Partly for a fun learning experience, and partly to simplify deployment. For new projects, if…
Golang for components that need the speed, Perl for the rest.
Mojolicious is my preferred Perl framework.
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#19http://djangoframework.com is overall one of the best documented + most stable web frameworks out there. Besides the actual functionality, that you can also get from smaller libraries, you want a framework because it gives you standard go-to solutions for many common questions you encounter when making a basic, relational database backed application (database access, database migrations, templating, forms, validation…
I've used Django and I liked it but it really was quite slow.
Re: Ask HN: What stack should I use to build my basic web app as of 3/29/18
#20Earlier quoted context omitted.
This would be my answer every month ( after you this time ;))
Mine too :) Most of my applications are built using Perl and the excellent CGI::Application module/framework. I've used Dancer a couple of times, but that tends to be for smaller applications, and it has to be said that the last remaining dancer application I used in production was replaced by a port to golang this morning. Partly for a fun learning experience, and partly to simplify deployment. For new projects, if…
What happened to Slaughter?
Except for perhaps an unfortunate name it was an interesting project. I can see that all links to it doesn't work anymore..