HNHacker News
TopNewBestAskShowJobs

secoif

840 karma · joined April 19, 2011

submissionscomments
secoif··on Valve brings non-game software to Steam
Have you used windows 8? The preview is embarrassingly bad, garbage is being generous.
secoif··on Google's Autonomous cars complete 300,000 miles without an accident
This was the easy part.

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.

secoif··on Huffshell: You probably type too much.
Aliases to cd into directories? You need to check out autojump style tools! Will change your life.

e.g. https://github.com/rupa/z

I very, very rarely type cd by hand anymore, mostly just use z and popd

secoif··on Node and Express Tips
May be a valid use case so long as you know what you're doing, and if this works for you, that's great. Though, considering the fact it's generally a bad idea, advising people to break the rules should probably be qualified with a serious disclaimer when presented in the comments of a post appealing to beginners...

> ...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.

secoif··on Node and Express Tips
You might be trolling, but custom $NODE_PATH configurations are a slippery slope and can reintroduce dependency hell f you're not careful. You're voluntarily disabling one of npm's finest features. This sentiment is even in the manual:

"[$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_...

secoif··on Letter to John Carmack
Talented people like Carmack have the potential to make things less crap, if they took an interest. If they don't take an interest, things will remain the way they are for a lot longer. John Carmack should join the Chrome team.
secoif··on Microsoft abandon Metro name due to legal challenge
Ok, the hyperbole of both articles got me.

> 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.

secoif··on Microsoft abandon Metro name due to legal challenge
"Windows 8-style UI"???? Did their legal team pick that name? This says so much about the state of Microsoft.

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.

secoif··on Gittip minimum raised from $0.25 to $1.00
Many devs don't have recurring income. It'd be good if i was able to simply say "10% of every invoice I send gets sent to gittip for me to distribute amongst the projects I used to generate the work in this invoice."

Freshbooks Integration?

secoif··on Gittip minimum raised from $0.25 to $1.00
The American "I am obliged to give you a tip because minimum wage sucks" doesn't seem to be what gittip is about. In fact, it's much closer to the Australian idea "I am giving you more money because of your impressive performance, and I want to say thanks".

In Australia, I tip when service is awesome. In America, I tip when service isn't absolutely terrible.

Full disclosure: I am Australian

secoif··on How can a programmer learn to design websites that don’t suck
Yep. I've seen far too many people taking this "no absolute positioning" habit too far, they end up positioning everything with floats. Float abuse is a lot like playing Jenga.
secoif··on OS X Mountain Lion available on the Mac App Store
Are you running time machine? Time machine brings my SSD MBP to a crawl.
secoif··on Seed-DB
Are exits the only measure of success?
secoif··on Command line tools every web dev needs to know
see also burl: https://github.com/visionmedia/burl been good for testing requests against json apis
secoif··on Ask HN: If there was no internet, what business would you have started?
Link for such SCADA exploits?
secoif··on An idea for Github to make more money
I don't see the problem. The money goes to the owner of the repo to distribute as they see fit.

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

secoif··on PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names
I don't know any rails developer who has written a web server, where did you get that idea? Many use mod_rails via nginx or apache:

http://www.modrails.com/

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.

secoif··on Jeff Atwood is a muppet
Author's primary argument is that Atwood is ignorant of PHP, but provides no evidence author isn't ignorant of everything but PHP.

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.

secoif··on JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
I don't know what your definition of software success is if jquery doesn't fall in that category.
secoif··on JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
The reason IE is still clinging on is because not enough people are making noise about it.

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.

secoif··on JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.
It is only not possible if you are incapable of changing your build script.
secoif··on Cloud9 IDE lets you code together in the Cloud. And offline. And in Ruby, PHP…
Why isn't it on by default?
secoif··on Node.js v0.8.0 [stable] is out
While the benchmarks look like there's an overall improvement, it's not instantly clear how much of an improvement they demonstrate. To more easily parse what the benchmarks are telling us, I calculated the percentage difference and the results appear really impressive.

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...

secoif··on We will try to stop fixing bugs in PHP
Every php job can be turned into a rails/django/whatever job, you just need to sell it.
secoif··on Visual simulation of the 6502 CPU
Appears to not work in Chrome (at least for me). Safari did the trick though.
secoif··on Using unix as your IDE
This is one of those cases where you should have calmed down before typing.
secoif··on Show HN: Joosy, the rails-tied browser app framework
" it just seems like it comes with so much i wont ever user - and could easily add via a mixin on a per project basis"

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.

secoif··on Your first Node.js module
You shouldn't require using the extension.

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.

secoif··on Your first Node.js module
'this' is also the same as exports. Initially, they all have the same value, they all point at the same object. If you assign module.exports to a new object (vs simply adding properties to the existing object) it will ignore the value of exports and this.

It's incredibly confusing and they should have just picked one way to export data, instead of three.

secoif··on Your first Node.js module
It should also be pointed out you rarely need to edit the package.json manually:

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-...

← PreviousPage 4 of 9Next →