4 ms·
Unless there are any unusual requirements, if I were starting a web project today I would use these technologies: - Angular/Bootstrap on the front end -
by johan_larson 11y ago
Unless there are any unusual requirements, if I were starting a web project today I would use these technologies:
- Angular/Bootstrap on the front end
- Java/Spring Boot on the server
- PostgreSQL on the data tier
- deploy on AWS
All of these are distinctly conservative choices at this point, but using tried-and-true technologies has real advantages. They raise no red flags with bosses or prospective investors. They are well supported and will be for a long time. And it is easy to find knowledgeable people if you need to scale up staff.
Since you are a Rails guy, you might want to substitute Rails for Spring Boot. It's a respected system, and you already know it. Win.
If I had the latitude to take one risk in choosing the tech stack, I would swap out the Java/Spring Boot for Haskell/Yesod, since I grow increasingly frustrated with Java's verbosity. But this choice definitely has downsides: I know Java _much_ better than Haskell, and Haskell is rare enough that if I needed more than a couple of developers, I'd need to either hire them remotely or develop them from scratch.
Similarly, you might want to take a chance on one off-beat component if it catches your eye. But just one.
- Daishiman 11y agoI would really hold off on Angular. The development path of that project seems to indicate a dead end. And as far as technologies go for a new project that's supposed to start quickly, it has some tremendously complex abstractions while having issues with debugging. This is all a pet peeve of mine, but I think the kind of two-way data binding that Angular proposes will be seen in the long run as a mistake. The fact that you can't just understand what's going on behind the hood without reading tons of documentation in the middle is very troublesome.
- deathtrader666 11y ago+1 I'd run away from Angular, into Ember-land!
- johan_larson 11y agoDead end? What makes you say that?
- Daishiman 11y agoThe fact that the very developers of Angular have stated that Angular 2.0 will not be backward-compatible with Angular 1.0, and the reason why Angular 2.0 is being made is because the operating assumptions of browser capabilities when Ng 1 was made have changed radically.