cmaher

That's assuming all people want to live like that. I wouldn't know what do do with that much space, and I hate having to drive anywhere. Give me decent public transportation and access to world-class restaurants over a house and a yard and a car any day.

> > Are you suggesting that it's reasonable for people from less-affluent backgrounds to have to spend their entire twenties working their way through school while the more affluent finish at 22?

> Yes.

Why? What positive economic impact does this have? How can you justify 4+ years of lost positive contribution by these individuals to the economy? How is that economically efficient? What metrics are you basing your reasoning on?

The difference being that large bureaucratic organizations need an army of lawyers to approve the use of open source libraries, and using a common license that is already understood (e.g. CC0) will result in a far smoother experience when the developers in that organization try to use anything to make their miserable lives a touch nicer.

source: I have formerly lead one of the described miserable lives.

> Cause you've got a web browser that was designed to view pages of linked information that has now been pressed into service as a ad-hoc run-time for building applications

At this point, this is argument is 100% false. Browsers of today aren't the browsers of the 90s. Chrome came out in 2008 and has ALWAYS been designed to run applications, and an entire operating (ChromeOS) is based on the idea that the browser isn't just a system built for viewing linked documents, but a valid application platform.

> "Tired of all the slow and bloated preprocessors..."

libsass is amazingly fast. I generally see it churn through ~20k lines of CSS (don't ask) in 6ms.

That's actually where I want to take this, I'm thinking a wind speed sensor to recognize if it's on/off and a temperature sensor to turn it on/off automatically.

Thanks! It was supposed to link to https://www.particle.io/

(how embarrassing)

While I appreciate another look at React, I have to disagree with the article's conclusion that React is "objectively better" than other frameworks. The summary article of the story is basically "we completely re-architected our application and things are better now". There's nothing in Backbone that makes you construct the initial architecture on display, and you can use Backbone to build the final architecture as well. So, moral of the story: re-architecting an application you know more about than you did at the beginning is probably a good thing.

At the website: http://mitpress.mit.edu/sicp/full-text/book/book.html

Or as a pdf: https://github.com/sarabander/sicp-pdf

Small daily doses of antibiotics act as a growth stimulant for animals. Bigger animals = more money, and there aren't any incentives in place to prevent farmers from killing the effectiveness of antibiotics.

First, this post: http://blog.zackshapiro.com/want-to-learn-to-code-start-here gives a good foundation of troubles you should expect, although point #1 is more than a little impractical for most people.

You should also be aware that the only way to learn to code is to actually do it.

Try going with a book tutorial, such as http://eloquentjavascript.net/

You can click on the buttons next to code entries to try stuff out.

Learn how to develop code outside of a browser. Pick a text editor and learn it. Sublime text (http://www.sublimetext.com/) is a great choice for beginners. Learn how to use the command line.

After you have an OK foundation, check out the problems at http://projecteuler.net/ working your way through them sequentially (apparently, most people don't go beyond ten problems)

Create a GitHub account. Learn basic git, and start putting your code out there.

Come up with something you want to make and start a project to actually do it. Be sure to start small, since a lot of software development skills only come with practice.