3 ms·

I wouldn’t worry about the popular hipster stacks, but rather shoot for something productive and preferably slow moving. There is a reason things like Django or

by moksly 7y ago

I wouldn’t worry about the popular hipster stacks, but rather shoot for something productive and preferably slow moving. There is a reason things like Django or Ruby on Rails help people actually get things out the door. They come with a lot of batteries included, and while it may not be the hip (or even smartest) way to do things, that doesn’t really matter nearly as much as getting shit done. stacks like Flask or anything JS backend really, will make you write tons and tons of code that other frameworks will give you for free. At the end of the day, not a single one of your users are going to care about you tech-stack. I work in the public sector, and we have a lot of legacy stuff. One of our most popular web apps, that always scores really high in user saturation when we review/audit, runs ASP web-forms. That’s some really old shit, and you really shouldn’t pick that up in 2019, but the point is that no one who uses it cares.

shanev 7y ago
Is there a better term for "hipster stack"? Rails and Django were most certainly considered hipster when they first came out.
- 91edec 7y ago
  > Is there a better term for "hipster stack"? Javascript eco system.
  - y4mi 7y ago
    You made me laugh, but it is unfair. vue, (p)react and angular all have a better frontend development experience than you'd have with Django/rails. It just increases your tech stack from one component by at least 3 (webpack, nodejs, frontend-lib like vue/(p)react/angular ) And that is sometimes more than it's worth.
    - moksly 7y ago
      > vue, (p)react and angular all have a better frontend development experience than you'd have with Django/rails. I don’t know much about RoR, but I think Django has a pretty great front-end experience. In general I think the classic MVC approaches are highly underrated. Well maybe not so much now that React, Vue and Angular are all doing components that you can incorporate in your standard MVC, but I’ve always found the SPAs and it’s MvvM architecture needlessly complicated unless you desperately needed offline functionality. It’s gotten quite popular of course, and great things can be build with it, but it’s so complicated that it makes a one-person project into something you often need at least two specialists to do well.
- nxpnsv 7y ago
  Yeah, that was before they we’re cool and other devs probably hadn’t heard of them yet...

by moksly 7y ago

shanev 7y ago

Is there a better term for "hipster stack"? Rails and Django were most certainly considered hipster when they first came out.

91edec 7y ago
> Is there a better term for "hipster stack"? Javascript eco system.
- y4mi 7y ago
  You made me laugh, but it is unfair. vue, (p)react and angular all have a better frontend development experience than you'd have with Django/rails. It just increases your tech stack from one component by at least 3 (webpack, nodejs, frontend-lib like vue/(p)react/angular ) And that is sometimes more than it's worth.
  - moksly 7y ago
    > vue, (p)react and angular all have a better frontend development experience than you'd have with Django/rails. I don’t know much about RoR, but I think Django has a pretty great front-end experience. In general I think the classic MVC approaches are highly underrated. Well maybe not so much now that React, Vue and Angular are all doing components that you can incorporate in your standard MVC, but I’ve always found the SPAs and it’s MvvM architecture needlessly complicated unless you desperately needed offline functionality. It’s gotten quite popular of course, and great things can be build with it, but it’s so complicated that it makes a one-person project into something you often need at least two specialists to do well.
nxpnsv 7y ago
Yeah, that was before they we’re cool and other devs probably hadn’t heard of them yet...