Hacker News new | more | comments | ask | show | jobs | submit login

> "Ok, let's make a rails app" > "Oh, I need rails first" > "Oh, I need rbenv first" > "Oh I need brew" > "Oh I need xcode tools"

As a Rails dev, this made me chuckle, yes, I've put a lot of hours into troubleshooting dev setups. But this is the wrong example. All of these are installed with one line on the terminal. And really, there are far simpler web stacks to pick up without even having to leave Ruby. Sinatra on system Ruby works just fine. All you do is 'gem install sinatra', open up a text editor and go.

Really, the complexity you have to watch out for is the complexity you impose yourself. Choosing the wrong tools for the job or the wrong abstractions. For many applications, Rails is overkill.

That involves knowing the one line on the terminal, and when you google "rails set up" you will get a bunch of out-of-date tutorials, and not knowing rails you won't know which is out-of-date.

On the other hand, 30 year old C code will often compile right out of the box, because the people maintaining them weren't chasing the New Flashy every year.

The modern systems suck in terms of maintainability.

Lol as opposed to PHP where you just drop the folder into Apache folder and you're done.

Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact