840 karma · joined April 19, 2011
Finally somebody gets it. Building on top of some giant abstraction over abstractions is not an investment in the future, it's just a timebomb of technical debt. The landscape changes so fast the ability to easily replace a tool is a very desirable feature. This author has the right attitude, everyone else seems to be going around with blinders on, searching for a silver bullet.
I think you've got that around the wrong way. It's more of a problem in node/browserify because you're typically working with very many more 3rd party libraries.
By not messing with globals, node allows you to safely load multiple versions of the same module and not worry about strange runtime environment changes. It probably doesn't matter in this trivial case, but node's primary win is how easy and safe it is to write and share modular code so yeah, prototype pollution is a destructive anti-pattern.
Don't do this. Extending native prototypes in node is terrible practice since it ruins the thing node gets very right: code encapsulation. Not good advice at all.
http://www.georgehernandez.com/h/xComputers/Programming/Medi...
If this has any truth (perhaps a different c--?) I'd like to know which one is being referred to.
This tool just hindering your progression and yet another abstraction someone has to to learn if they are going to deal with this code. It would make sense if this was a one-off thing and you'd be saving someone the effort of learning some weird protocol or syntax, but since regex is so common and most programmers have just learned to deal with them, you're actually adding more cognitive load, since now they have to know two things instead of one. Imagine coming across this in someone else's code and discovering the regex didn't work as expected. Now I have to debug the regex and figure out whether it's a bug in the tool, or in my regex, etc…
Instead of focussing on teaching pirates a lesson, they should have set up an in-game option to "pay $x to remove piracy issues from game".
As a compulsive tab hoarder, I've been using Tab Wrangler for this same purpose for over a year and I believe its approach is far superior: it just closes tabs that you ahven't visited for a period of time. If you haven't been to a tab in ~20 minutes, likely you don't need it on hand. I can't know when I'm done with a tab until I've moved onto my next task, which means I'm no longer thinking about that tab.
Also, you can lock tabs, have a minimum number of tabs (I set mine to 5) and easily list any auto-closed tabs so you don't lose anything, though I find myself only needing to look through that list once or twice a week.
Anyway, Tab Wrangler absolutely changed my life.
Not my project, just think it's awesome: https://chrome.google.com/webstore/detail/tab-wrangler/egnjh...
Doesn't instil confidence.
This much:
var app = require('express')(); app.get('*', function(req, res) { res.send('hello world'); }); app.listen(8080);
Hello world probably a bad example.