840 karma · joined April 19, 2011
The hard part will be fighting the technophobes when somebody drives into the side of one of these and kills themselves. I don't envy being in that battle.
e.g. https://github.com/rupa/z
I very, very rarely type cd by hand anymore, mostly just use z and popd
> ...small shared library files that don't justify their own package.json...
Generating a package.json + dependencies is a 30 second job with npm init + npm install --save + npm link. I follow a similar pattern to you when developing inside a single module, where I start growing module saplings in a ./lib folder to spike on ideas without the overhead of totally decoupling from the parent, but as soon as you need to share that code around and put it into your $NODE_PATH, you've got to decouple it anyway, so really you're effectively 30 seconds worth of work away from creating a real module anyway, and thus you could do away with your custom $NODE_PATH.
"[$NODE PATH exists] mostly for historic reasons. You are highly encouraged to place your dependencies locally in node_modules folders. They will be loaded faster, and more reliably."
http://nodejs.org/api/modules.html#modules_loading_from_the_...
> From now on, the new terminology that Microsoft is using is "Windows 8-style UI"… and "New User Interface".
The blog post carefully omitted the final, critical line in the parent article (I skipped the line myself):
> As we get closer to launch and transition from industry dialog to a broad consumer dialog we will use our commercial names.
This new name has a totally different persona and sends a confusing, unsexy message about Microsoft's vision for the future. It shows no competent person/team is in charge of maintaining a unified, consistent brand, but I guess we already knew that. The name "Metro" must have been an accident. Is "Windows 8-style UI" even really a name? It's more of a literal description. I don't know how you could pick something more lacklustre.
The experience formerly known as "Metro" encapsulates all of the innovative, risky developments Microsoft has been making on the UI front, with mostly positive responses (at least regarding the appearance). Metro was the word for Microsoft's sex appeal. Changing the name to something so unmemorable and vanilla is like deleting the word and its definition from the dictionary.
While this could have been a great opportunity to fuel the hype for the new UI with a slick new name, instead they choose to wet blanket the whole thing, making "Metro" not even really a thing anymore.
Microsoft needs help, they're clearly very, very sick.
Freshbooks Integration?
In Australia, I tip when service is awesome. In America, I tip when service isn't absolutely terrible.
Full disclosure: I am Australian
If you contribute code to an OS project, and then someone makes money from that OS project, do you feel pissed off that you didn't get a cut of that money?
If you trust people to build you free stuff, why do you suddenly not trust them to get paid for it?
edit: clarified
Also, PAAS offerings like Heroku and Engine Yard make deploying sophisticated rails environments far more convenient than their PHP equivalent.
> "sticking code snippets in web pages"
You can do exactly this in ruby with ERB, but many shy away from this approach due to a distaste for the bolognaise pattern.
You should try ruby/rails/sinatra on your next project, it will change your life.
I guess if you've lived in a box your whole life, a slightly bigger box must seem pretty good. Don't knock my box, you should have seen how small the last one was.
The less usable the net is for older browsers, the closer we move the users of those browsers to the threshold of upgrading.
It may mean more complaints from the staff to the IT department, it may mean grandma asking her grandkids why the google is broken, but if enough people are vocal about it, it will encourage upgrading.
Every time you support IE, you are slowing the uptake of newer browsers, and you are a bad person for it.
Some of the most notable improvements listed below (results rounded, possibly misleading, but nonetheless awesome).
According to these benchmarks, 0.8 is approximately:
* 43% faster at reading files.
* 119% faster at reading 4096 byte buffers.
* 117% faster at writing 16384 byte buffers.
* 243% faster at http benchmark TYPE=bytes LENGTH=123456
* 506% faster at http benchmark TYPE=unicode LENGTH=55555
Be sure to note the actual figures though, as they are what really matter.
https://github.com/timoxley/node/blob/ddee8bcda50c8377d135d6...
You could easily add the simple helpers in underscore too, they're not complex, but the idea is you use a library so you can work at a higher level of abstraction. Why write your own array intersection method? Why write your own camelcase function? Sugar opens a lot of doors that are just a little much effort to normally be bothered with (and underscore does too, but to a lesser degree).
"…start extending things that weren't built that way?"
It's ok to extend the prototypes, so long as a) you own the objects and b) you only extend the prototypes from a single module (e.g. sugar). c) Don't extend Object.prototype (unless you're really brave). http://blip.tv/jsconf/jsconf2011-andrew-dupont-everything-is...
The major risk is in collisions, and if you follow those rules you reduce the chance of this occurring to a minimum. If you're worried about for-loops, the way sugar handles extending the object prototype makes this a non-issue. http://sugarjs.com/native
Please actually use a tool before you condemn it.
This gives you the flexibility to transparently change the file into a folder + index.*, then break functionality up into pieces that live inside that folder.
It's incredibly confusing and they should have just picked one way to export data, instead of three.
npm init: Prompts for basic/common package.json entries
npm install --save: Install a module and place into dependencies
npm install --save-dev: Install a module and place into dev dependencies
npm install --save-optional: Install a module and place into optional dependencies
http://blog.timoxley.com/post/22371787222/handy-new-options-...