Ease of implementation? Just grab any modern Rails and pick a frontend framework later.
I worked with Rails briefly in my previous company and found a working product nearly unmanageable. Any tips on keeping the codebase legible?
Ask HN: Which web stack should I learn for personal projects?
21–30 of 51 posts
Re: Ask HN: Which web stack should I learn for personal projects?
#22So, if you already know javascript then I would look at node.js. Full disclaimer: I actually use golang for my personal projects because I'm attracted by its simplicity and how it really doesn't hide stuff from me using hand-wavy magic. Performance is also a factor, but not one I consider when comparing it to node. If I'm working on something I want to roll out fairly quickly. A prototype. Then I'll probably use node…
Thanks for the detailed reply :) I'm a little iffy with Rails myself.
Re: Ask HN: Which web stack should I learn for personal projects?
#23Re: Ask HN: Which web stack should I learn for personal projects?
#24Sometimes, bare Java EE is good enough.
Re: Ask HN: Which web stack should I learn for personal projects?
#25But so far I haven't heard anyone mention the Nim programming language which can compile to JavaScript or C and has what I consider to be superior syntax and excellent performance as well as great metaprogramming capabilities. See http://nim-lang.org
Re: Ask HN: Which web stack should I learn for personal projects?
#26My recent projects have been built on a Node server. I like to use knexjs as an ORM, sometimes including bookshelfjs for model building. Cacheing or rather message queuing has been done with redis. Often, this backend server will feed a much smaller front end web server that leans on react and jsx to spit out HTML.
PS I started out with rails but moved to a primarily node stack last year.
Re: Ask HN: Which web stack should I learn for personal projects?
#27Re: Ask HN: Which web stack should I learn for personal projects?
#28Ease of implementation? Just grab any modern Rails and pick a frontend framework later.
I worked with Rails briefly in my previous company and found a working product nearly unmanageable. Any tips on keeping the codebase legible?
If the developers put the projects together properly, it should have been very legible and easy to jump in on. Ruby isn't exactly a hard language to learn and generally very legible, almost to the point where each function/statement should be close to reading plain English (other than regexp and a few other things). That is, if the developers are following best practices, separation of roles, and not trying to hack together various work arounds because they don't know the language.
Re: Ask HN: Which web stack should I learn for personal projects?
#29So, if you already know javascript then I would look at node.js. Full disclaimer: I actually use golang for my personal projects because I'm attracted by its simplicity and how it really doesn't hide stuff from me using hand-wavy magic. Performance is also a factor, but not one I consider when comparing it to node. If I'm working on something I want to roll out fairly quickly. A prototype. Then I'll probably use node…
I would recommend the polar opposite, actually: use a framework that has nothing in common with anything that you already know. After all, half (or more) of the point of personal projects is to learn new things, right?
Re: Ask HN: Which web stack should I learn for personal projects?
#30Earlier quoted context omitted.
Thanks for the detailed reply :) I'm a little iffy with Rails myself.
Here's a great Rails learning resource: https://www.railstutorial.org