61–70 of 85 posts
Frontend: React (via create-react-app), good old Bootstrap Backend: backend as a service like Firebase or Horizon/Rethinkdb. Vendor lock-in is a big concern here but you can get your prototype done so fast with those tools.
Using BaaS things is more like for the prototype/MVP like projects in my opinion.
Edited: though I see title has "basic" word in it, so it's fine.
If you are looking at building basic webapps, I will really recommend Meteor. It is very intuitive, flexible and Javascript across the whole stack. It can easily integrate with Vue and React, which are again JS friendly.
Django is very neat and you can learn how to code within a week looking at the sourcecode of Wagtail.io ... I did it that way.
PHP is very straightforward and pretty much every issue that you run into would perhaps have a solution ready for you on StackOverflow.
1. I would go with VueJS for frontend - see example https://vuejs.org/examples/tree-view.html Definitely can recommend handling of complex state through redux/vuex. For backend: Go with anything that you are proficient with. If you aren't familiar with anything I recommend starting with RubyOnRails/Sinatra/Django/web2py/Phoenix. 2. Yes - http://bestof.js.org/ See also http://stateofjs.com/2016/introduction/ ,
I don't know, but unfortunately the answer will be completely different in October 2018.
CSS ICON: http://cssicon.space - Generate CSS icon.
INITIALIZR: http://initializr.com - Generator HTML5 templates (Classic/Responsive/Bootstrap)
BUDDY GO: https://buddy.works/buddy-go - Git hosting on your server.
LAYERSTYLES: http://layerstyles.org/ - Crate CSS from Photoshop Layer Style.
FFFFALLBACK: http://ffffallback.com - It bascially scans the page’s CSS and creates a clone page where you can test and analyze different fallback fonts.
Are you an experienced web programmer and already know how to manage migrations, CDN, REST apis, etc ? If not, I would still go with Rails. Its massively productive, batteries included... and forces you to learn some practices that you can later take to other frameworks (migrations, asset pipeline, etc). I dont know of any other framework that forces you to adopt these. On HN, you will find a lot of rhetoric against…
I'm always keep in an eye out for a Rails replacement, and a good database story is the first thing that I look for.
So, since your question says "basic" I'll leave it at that.
I would say mithril.js for the frontend and Flask for the backend is pretty good, but that's just my favorites. There are plenty of other good ones, and neither of those are particularly popular.
I would say mithril.js for the frontend and Flask for the backend is pretty good, but that's just my favorites. There are plenty of other good ones, and neither of those are particularly popular.
I use flask for a personal project of mine, but instead of Mithril for the frontend, I use http://riotjs.com/ . I find it much more readable for someone who has been working with HTML/CSS for quite some time.
Do you like HTML-like templating and a lot of sugar? Riot is the way to go. Do you like minimal magic, JS-style templates, and/or Lisp? Mithril is the frontend for you.
Otherwise:
If you like Python, Django.
If you like Ruby, Rails.
Otherwise: Flip a coin.
Heads? Rails.
Tails? Django.
A lot of very smart people will tell you that PHP is as good an option as Rails or Django. The problem with PHP is that while the upside for PHP is, as they're observing, just as good as the Rails/Django upside, the downside is way worse.
Counterintuitively: I think you should really know what you're doing as a developer before you decide on PHP. PHP isn't by itself going to teach you to be a better developer. Python will.
Avoid Javascript frameworks until you really understand what you're doing. Also, know ahead of time that "really understanding what you're doing" might result in you continuing to avoid complicated Javascript. A trap I can tell you about from recent experience. :)
Probably don't build front-end web applications in Go.