And there's at least tens of millions of people who only have one name:

https://en.wikipedia.org/wiki/Mononymous_person#Modern_times

https://en.wikipedia.org/wiki/Indonesian_names#Mononymic_nam...

The curse of oil.

This has the same problem as hyperloop, then. Sure the main part of the journey is quicker, but if you have to take a connecting flight from New York to Boston, and a train from Luton to London, it's overall slower than a subsonic plane.

If he wants to control where people get his software, he should have published it under a proprietary license. Not saying he does, though.

Fair enough. I would posit that he didn't ever expect that the npm folks would undo his actions, even if his decisions were/seemed rash.

He doesn't care if anyone takes over the leftpad module.

He unpublished leftpad

Someone else republishes leftpad as a new owner

Since npm won't allow you to publish old versions, stuff is still broken since the depended on files have a hard dependency on v0.0.3

npm (the company) forces a republish on v0.0.3 or I guess an ununpublish.

People are only trying to help. Better now than when the press hears about it and starts taking the piss out of them.

Xcode works fine for me. I can't say the same for Android Studio, which seems to require a machine more powerful than a top-of-the-line MBP.

I don't think I understand. If they could rehabilitate unsuitable donor organs and didn't have to worry about rejection, there wouldn't be a shortage. Isn't that the end game?

There would still be a great shortage. The supply of donor organs is tiny.

No shortage is more like it. Intact cadaverous hearts are plentiful by comparison to awaiting heart transplant patients. Most heart failures are immediate and fatal, but people who have progressive failure are relatively rare. Transplant patients would conceivably be donors for the program (since most heart damage is soft tissue failure).

You could use a much broader range of donor organs, and not having to worry about matching would vastly increase the number of usable donations.

Still, Uber knows who you are. If you damage their car they can invoice you. Presumably they will have CCTV in these things?

Useless clickbait. Nobody ever claimed that the one and only benefit of standing is to "burn excess calories".

Personally I had developed back pain from too much sitting. When I stand, I have better posture and so I don't get the pain.

> Nobody ever claimed that the one and only benefit of standing is to "burn excess calories".

Well, the article didn't claim that, either. It mentions that as one potential (arguable) benefit. It mentions this in the broader context of standing desk improving health in general, and the fact that there's basically no evidence for this.

Agreed. However, it seems to me that "health in general" is potentially harder to quantify than specific health conditions. It might be of interest to people who deal with workers in the aggregate, such as insurers and employers.

But I could imagine individual workers wanting to know more about the specifics: Could standing at work help with my personal health and medical issues? That question presented itself to me when my doctor told me that my neck and upper body pain was caused by sitting at a computer all day. Switching to a standing desk gave me fairly rapid relief after struggling for more than a year.

Of course that's just my anecdote. If someone else doesn't have the same problem, then the question is completely different for them.

Strange, I have the reverse! Carrying to many heavy loads when I was stupid/young means that standing is actually quite a lot more tiring for me. I can walk for miles without problems, but /standing/ for a few minutes is really painful on my lower back.

There is a case of wear an tear on the mechanical bit of the body. Sitting has it's issues, but standing put a lot of unnecessary strain on many sensitive joints. You /will/ pay for it later on...

Getting older sucks ;-)

On OS X, Adium, Textual and Colloquy are predominantly built in HTML. It's hardly groundbreaking.

This is a good point. I'm not opposed to using HTML in an app. Back in the early 00's, I did a decent bit of tweaking my Adium conversation display style. It's useful for displaying that kind of content easily.

But there's a difference between saying "I put a webview in my app" and "I put my whole app in a webview". Driving the whole thing from HTML/JS tends to have bad implications for:

• Performance (laggy animation, excessive CPU use, more drain on battery)

• Window management (everything in one box! Modal overlays! Window management is overrated, nobody uses Exposé or multiple windows of one app anyway)

• and UI consistency (some popup menus look one way, right click and every other popup menu on the computer looks another way)

Adium, Textual, and Colloquy use HTML to display things, but they don't try and shove the whole damn app in it.

UI concistency is horrible with these html-in-a-webview app.

Every app has to re-invent the wheel here, and there's a lot of native controls that don't exist on HTML.

Generally though, window management is unimportant because these apps tend to be single-windowed apps anyway.

They're only single-windowed apps because they choose to be. Colloquy and Adium both let you pull channels/servers out into multiple windows (just like tabs in a browser).

Slack actually does use multiple windows. The sign-in flow (enter organization, enter email address, choose between magic-email or password authentication, enter password) happens in a popup.

What it can't do is pull organizations out into separate windows like Adium or Colloquy. I'm in 3 separate groups on Slack, and sometimes in a conversation in more than one of them simultaneously.

And yeah, I can go open up the second one in my web browser, but it kind of defeats the point of having a "native app" if it's going to be crappier than just going to the website.