rhubarbquid

This site is pretty CPU heavy for something reminding us to respect our users' resources...

In hindsight, this was probably a candidate for the basis of OS X before they decided to buy NeXT and go with that

I read it as "The Marco" at first too

That was my first too. What's listening for this? Good luck getting me to grant random apps permission to use my mic.

It could be a "Smart" TV though, listening for your phone/tablet/laptop, or a device installed in places like cafes...

I'm no lawyer, but encouraging registered developers to violate their contract with Apple could be pretty shaky ground, legally speaking.

I've been doing contract work for a company that uses Python and Stripe, so I found that surprising too.

Terrible recommendations for my neighborhood in Oakland... the top 3 recommended places are the 3 of the most popular and crowded restaurants and bars in the area. The top one being the restaurant that's so busy it's generally hard to walk past on the sidewalk because there are so many people waiting out front.

> It's really interesting how OS X is the one that has a terminal emulator with the most features out there.

In my experience, the vast majority of web developers use OS X. Those of us doing server side and devops work spend a lot of time in the terminal

This error pops up for me:

    This site or app is sending too much traffic to   
    rawgit.com. Please contact its owner and ask them to use 
    cdn.rawgit.com instead, which has no traffic limit.

The sound quality of land line voice connections is terrible for anything but speech. IIRC it's something like 8 bit 3 KHz

Seconded. Get your legal advice from lawyers not from HN (or any other web forum).

Because they didn't show any new hardware.

Didn't they just announce they were going to stop doing that?

> Choosing a development platform is more than just a technical decision—it’s a career decision.

That's not a great argument to convince me to adopt a brand new platform

> I wish we were Apple and had $159 billion in cash reserves.

Apple went from near bankruptcy to that $159 billion by sweating the details. (and, I suspect, a certain amount of luck)

DuckDuckGo and Blekko seem to think so.

I assumed they wanted to limit the amount of feedback/bug reports they got to a level they could usefully cope with. Any new release is potentially going to have tons of issues with real world situations that never happened for developers or in QA. Anything released by GitHub is going to get a lot of attention. By limiting the number of initial users, they can get some real world testing and not get millions of duplicate bug reports.

Reporting on rumors doesn't preclude journalistic integrity.

ARM didn't "come out of nowhere", it's been used in embedded and mobile systems as a low power CPU for decades now. The earliest mobile use I can find is the Apple Newton in 1993. DEC was marketing their StrongARM product as a low power CPU back in 1996.

That was exactly the conclusion of the paper. The US is effectively an oligarchy.

It appears to be a lamp, but other than that, I'm clueless too.

a16z is almost certainly doesn't own a majority of GitHub, so it's not entirely their decision.

I think it's about trying to take the question of acquisition off the table completely. The people who put money in to a16z's fund might be unhappy if they turned down an offer. The other people/groups (employees and angel investors) who hold shares of GitHub might be unwilling to turn down a big payout, when, in this case, a16z wants GitHub to keep existing and working closely with them. If the company is essentially overvalued from this investment, no one's going to make that offer.

To your point, I don't see how that benefits GitHub's management, though, unless they value independence over profit (which is entirely possible, but I have no idea).

Sure it's likely good for the FOSS community, but he's addressing the question of if it's good for the investor. On the face of it, an open source package management system doesn't have an obvious profit model, so it's not obvious to many people how anyone would expect to make a return on investing in NPM.

> I feel this takes a way a lot of the fun.

Agreed. Building the kit by the instructions was only about 1/10th of the fun. The real fun was building new stuff out of the pieces from all the sets you have.

No for profit company is your friend.

I assume you mean "Soylent"... though drinking solvent would probably also make you give up food

In older PCs the FPU was a separate chip.

Most text inputs in Mac OS support at least C-a and C-e too.

Cute but nauseating.

> Is this Python upgrade unusually difficult/ambitious?

Yes.

> Or is the Python community just very reluctant to jump on new things?

In my experience no. Lots of features have been added over the years, and they seem to be adopted quickly. v3 is a really big change though.