Hot take: it's never news when a substantially more expensive computer is faster than a cheaper one.

The Orange 5 is not an alternative to the Pi. It's an alternative to other $100+ SBCs.

"The Ford F250 is so much more powerful than the Ranger!" isn't news -- it's a more expensive pickup, and of course it's bigger and has a bigger engine.

In Washington, it's not just "highly regulated" -- the dams and hydro is owned by us, the people living there. Every watt of cheap power that's wasted by the bitcoin miners has to be replaced by expensive fossil-fuel generators.

As a user of the Acer Jade Primo Windows phone that had the same feature: IMHO, a chunk of the problem can be traced to convenience and apps.

On the Acer, the phone comes with a case and a dock. When the phone is in the case, it doesn't fit into the dock. And regardless, the connecter was a really tight fit, so it's always awkward to pop it in.

And ⦠the Netflix app didn't run in full screen when docked. If it had worked, it would have been worth it for that feature.

Hey, stupid fucking racist asshole.

If you're offended, that's _your_ problem to solve.

I worked for one of the many "3D on the web" companies. Step one, of course, is to make the basics actually work reasonably effectively. Step two is to figure out what kind of content would be embraced by users.

And there was the sticking point. We tried interactive fiction, maps, greeting cards, office-style output, music players and games. Of those, high-performance video for maps was valuable (we sold off all our patents on that), and games were enthusiastically embraced by users.

Everything else was "nice", but not nice enough to be worthwhile authoring the content.

(I made a super nice interactive globe powered by an entire cheap-o pipeline from Project Gutenberg. You could point and click on a country the rotating globe, and it could give you a list of books that mentioned that country.)

There's also a question about specific technology. Of them, we explicitly decided that VRML was just plain horrible to work with: it was super hard for anyone who wasn't deep in the field to grasp and it had too big a focus on "being cool" and not enough of a focus on "being fast".

Can I also suggest riding on National Forest roads? Out west there are thousands and thousands of miles of them, winding to a ton of very pretty forests and mountains. The forest service roads tend to be pretty beat-up gravel roads which are no fun in a car, but are plenty of fun on an e-bike!

That depends entirely on the tire. I have a RadPower Mini folding e-bike; as shipped it came with very knobbly tires. I recently replaced them with more urban-type tires, and the noise level dropped considerably.

(on the forest-service gravel roads that I ride on, I haven't noticed an important difference in traction, so from my POV it's a total win.)

The "who can't get a measles vaccine" includes every single person on the planet. The current CDC recommendation is to get the MMR vaccine at 12 to 18 months; that means that we are all susceptible at some point in our lives.

Reading the Actual Story, and looking at the web site for Creative Access, that's not really the whole story. A group of people noticed that although London has a ton of non-white people, that the creative agencies were overwhelmingly white. So, like any set of capable and energetic people, they set out to do something: they created an agency to widen the incoming funnel.

Kind of like how Harvard pushes it's graduates on the industry, but for non-White people.

The BBC, like many other organizations, would like to be more diverse, and is having trouble doing it. Hence the partnership.

I think I've seen this rodeo before. What I see is that web developers work to make their site "fast enough". In Scrum terms, they don't apply premature optimizations. They use too many modules with too many dependencies and assume everyone has a fast internet.

My two predictions: this will just encourage web site bloat, and a bunch of people are going to discover that their cheap-and-barely-working HTTP parsers don't actually handle 100-series responses.They are also going to discover that many high-level APIs don't provide any access to this new paradigm.

• Tide tables
• Atomic clock time
• Astronomical and orbital data
• How many people live in different states
• Tabulated results from asking companies how many people they are hiring

Each of these are more or less accurate and precise, and each has their own source of biases, and therefore you can trust them more or less.