The only root I use on my mayonnaise is horseradish. Which I guess is a bit of a food hack.

It's not about having hatred... It's about lacking trust. Do you trust a company that spent 30 years and billions of dollars trying to kill open source to be a good steward of open source software, If your business/livelihood depends on it?

Starting off by including a runtime dependency is a great way to have zero buy-in from old school admins. This was very much a part of systemd's political problem, which fed their technical ones.

Netcraft confirms... System V is dead.

You are plainly incorrect.

Big props to the xps line. Side note:

Who the hell thinks "only" a $420 discount on comparable hardware and build quality isn't a great deal?

Git-bash for Windows is fine.

On the one hand, duh. On the other hand, the binary download of emacs 25.1 for windows weighs in at ~60MB. Atom for windows around 90MB. Intellij IDEA community for windows: 345MB. emacs isn't really a text editor... it's an IDE. it's still VERY lean by that standard. Bear in mind too that the other two will proceed to download a bunch of stuff after installation, just to become functional.

I read /. for the centerfold, you insensitive clod!

You're surprised because you don't know your history. You should really read and learn about what you're talking about before making obviously false declarations.

How do you say stuff like:

with a straight face? Javascript has been an ISO standard since 1997! It's just a few years younger than python FFS.

AJAX is a pattern used within in-browser javascript, having nothing to do with the language itself, and yes, 5/6 look much different than 1.... much like you can't run python 3 code in a python 1 interpreter.

Migrated probably isn't the word. But my company has done some pilot projects from scratch in Node. There are some advantages:

• Node is usually comparable or better in terms of performance and resource efficiency
• Node projects seem to get to a MVP state very quickly.
• The event-driven model is a very good solution to SOME problems.

There are some disadvantages:

• The number of choices you have for different stack layers can be paralyzing. Example: we had to interface with an MSSQL database. 6 different libraries were evaluated, two were found to meet requirements, one was settled on. A month later a new requirement was added which meant we had to switch.
• if you are not very careful things can go spectacularly wrong with your dependencies (see: lpad disaster)
• callback hell is trying to trace a chain of callbacks for debugging. Promises have helped... some.

If developing something new I tend to look for ways that node can be used first, mostly because we're still trying to work out our stable development pipeline about 9 months after it started. Unless it was required I probably wouldn't choose PHP, only because the composer chain has more or less the same pitfalls of NPM, neither PHP nor node has any typing to speak of, and PHP has its rich history of inconsistency still weighing heavily upon it. to get top-notch performance out of it, you've gotta use something like HHVM which is less forgving.

Working with a legacy base, ask yourself: can this self-contained bit be written in node as a bridge to an eventual php-free-future? Does the event model make sense for the problem at hand? Will it incur unnecessary technical debt? If the answers are yes, yes and no... then develop that part in node. No reason to rebuild working PHP parts unless you actually need to rebuild them anyway.

Private space flight is rapidly advancing, and I'm pretty sure there's no copyright on the moon... ...yet

You know, it's usually actuaries that determine a drug testing policy must be in place. Being a business with no workers comp insurance because the rates are tripled in the absence of such a policy is a recipe for not being able to hire anyone at all.

Why build useful stuff when we can build a wall instead.