That one order of magnitude is about 7 years behind the Moore's Law. We're still progressing but it's slower, more expensive and we hit way more walls than before.

IntelliJ use wasn't that widespread until about 10-15 years ago. Java was thriving before that.

It was in heavy use in London investment banks in 2005. Even resharper was commonplace by the following year.

I mean, Apache Commons are still widely used. But it's just a handful of libraries maintaned by one organisation.

Switch 2 seems to be more up to standard. I was able to charge it with a normal phone charger and also the Switch 2 charger seems to work with everything else unlike the one for Switch 1. Fortunately I never bricked anything with that, but it just never worked with anything other than the console.

Switch 1 require the charger to support pd2 12v to charge at all. Some changer may decide to skip that voltage, and support only 9v and 15v. So Switch is not happy about it.

Every device in my room except for switch supports more than one voltage config. Wondering why on the earth switch decided to handle voltage setting like this.

Usually, pd charger will label their supported voltage config. And you can read that label to find out whether a charger will work with switch or not.

Source: I do use my phone charger to charge switch during traveling

Also notice, some charger will disable part of the supported voltages when there are more than one device connected. Mine apparently drops 12v when there are other device connected (thus prevented switch 1 from charging)

Please, this is HN. Don't make moot points. Smartphones existed before 2010, but few people had them.

The author used kernel compilation as a benchmark. Which is weird, because for most projects a build process isn't as scalable as that (especially in the node.js ecosystem), even less after a full build.

Yup, I noticed yesterday that all items were a few days old. It seems to work now.

According to the spec:

These constants are defined mostly to make serialization of infinite/NaN values simpler and more obvious, but can be used to indicate a "largest possible value", since an infinite value gets clamped to the allowed range. It’s rare for this to be reasonable, but when it is, using infinity is clearer in its intent than just putting an enormous number in one’s stylesheet.

Considering that only the last part of one article is missing it really looks like a bug.

Agree. And most of us would immediately assume that if it were any other administration.

I do all the time — and I have concluded that the current administration has done themselves no favors whatsoever in this regard. I really can no longer give them the benefit of the doubt and I think it's on them.

I'm guessing there's something strange about the whole site, because not only are the remaining clauses of Article 1 Section 8 missing (and section 9 and 10), so are all the annotations. The structure shows up in search engines, but the website gives 404s.

Also collections. I almost finished Tomb Raider II.