dpedu

How much did you know about N64 and 3DS development/internals before starting this project?

Gitea and the self-hosted version of Coder.com. It's the perfect development stack. I can have consistent (and infinite!) development environments no matter which computer I sit down at to work on a project.

I understand this is snark, but if you think about it, this is already implemented in electrical infrastructure. If I use too much power, the circuit breaker trips to protect me and protect the electrical grid. OP is about a billing breaker, but the parallels should be obvious.

If the CEO of the electric company didn't mandate circuit breakers, he should go to jail.

I'm surprised this isn't law. Should it be?

> Reactor 1 runs at 50% output as a preventative measure, EDF says

> Reactor 5 was already offline for maintenance and reactor 6 remains fully operational, EDF says

> EDF expects quick restart after cleanup as no new jellyfish are arriving, an engineer says

This seems like a graceful degradation, not an outright failure or closure.

That's pretty interesting, I've never heard of this! I've done something somewhat similar when visiting the Isle of Man.

For the unfamiliar, the Isle of Man hosts a world-renown motorsport race, mainly motorcycles, widely considered the most dangerous and deadly race in the world. Average of 2 to 3 fatalities per year.

It's a rather small and relatively sparsely populated island, but for the weeks of the race, the population absolutely explodes as visitors come from all over the world.

The local government runs a program called Homestay, which encourages residents to rent out their properties or spare rooms, etc, to tourists. And I stayed in one such Homestay. I think I paid 25 pounds a night to stay for about 2 weeks, in the 4th largest town on the island.

It's a great deal, my hosts were amazing, and it's a much better experience than a hotel if you care about learning about the island. I met their entire family and they shared "local knowledge" of interesting spots to check out.

350x is only about 10-20 years of improvement, using CPU FLOPS as the benchmark.

Digitizing books, even if it means the destruction of the original, means more people end up having access to the knowledge within, and is a good thing. Full stop.

Trump is the symptom; the "disease" is whatever causes people to want him running the country over some traditional politician.

What remains of this computer? Diagrams? Code? Anything that would let us take a closer look at how it works?

I've been re-building my NAS and decided on NFS on top of ZFS. However, my goals are slightly different than the author: I'm using a low-power cpu/motherboard, and I've built 2 distinct systems that can fail over as a form of high availability. I've actually written some custom software to handle the failover and data replication. In my testing, clients see writes block for just a couple second during failover. Would anyone be interested in a writeup about this?

I'm totally on board with the idea that ORMs create a variety of inefficiencies, pain points, and make it really easy to create bad queries or querying strategies. But I use them anyways because the convenience of mapping a row to a code object makes writing programs feel fast and simple. And if you know how ORMs can cause problems and how to watch out for them, you can still get a lot of mileage out of them.

That being said, what's the closest alternative that satisfies this - "mapping rows to a code object" - that doesn't suffer the same problems as an ORM? A middle ground between an ORM (like SQLAlchemy, for example) and "your rows are returned as a key/value dictionary where the column names are keys" type approach like Python's DB-API's DictCursor or PHP's mysqli_fetch_assoc. Is there a middle ground here?

Developers having a troubled relationship with documentation isn't new.

This is an argument for returning to living in caves and hunting mammoths for fear that our modern civilization becomes unavailable for a day or two.