3 ms·
Agree, except for that last part. At this stage OP won't know which backend language/tech will be best suited to whichever idea ends up taking off. So, best t
by tomComb 6y ago
Agree, except for that last part.
At this stage OP won't know which backend language/tech will be best suited to whichever idea ends up taking off.
So, best to just use whichever is most popular (and with the best trajectory) since popularity leads to other advantages. Choosing rails now, for example, would not make sense.
- deleted 6y ago[deleted]
- ttty 6y agoIf you do front end, just learn node. Both are js. Plus you can share code. 2 in 1.
- uyuioi 6y agoThe lack of structure in node is really bad for beginners.
- heynk 6y agoWhile it is harder to actually do something, node helped me understand how web development "really" works. I started with Rails - I could put a simple app together, but I had no idea how it worked. It wasn't until I worked with node, where I had to do my own routing, controllers, models, database connections, etc, until I finally could understand what was happening under the hood in Rails.
- trcollinson 6y agoFair enough. I mean if we are talking purely "getting a job as an engineer eventually" then .Net and Java own the market in my area. Though there are plenty of positions in Javascript, Python, Ruby, and even C/C++. I would imagine other areas vary heavily (and the data I have seems to show that). Pick the thing that will get you to your goal, I would say.
- gt2 6y agoWhat is your reasoning for it not making sense to choose rails now? It's mature and has a big community no? Hard to recommend it to a beginner, but not sure if I would recommend Node or Java to a beginner either, so that's a tough one.