Yet another angle would be that both the phone and the ring are in one's material possession, whereas the cloud is someone else's computer, and to display a nice web UI it has to have the data unencrypted over there.

In that case, the cloud is the potentially untrusted intermediate between the data and one's eyeballs.

All of these are equally valid, it all depends on what is your threat model.

This is closer to PSDoom:

https://www.cs.unm.edu/~dlchao/flake/doom/chi/chi.html

The issue that is being taken is about "too little too late", which is being interpreted as "since even in the best case scenario we're going to have dramatic consequences, any action is going to be fruitless", the counterpoint being that the new best case scenario (which is not a good one because it is late to take action, and is mostly equivalent to what once was thought to be the worst case) is still much less worse than the new worst case one.

As much as any large scale energy project.

Per kW it is quite effective.

The implication of GP's reasoning is that were Green not yelling about nuclear these would already be built because the projects would have started long ago.

>> where would you store nuclear waste (bonus points for: in your region)

People don't want solar farms, windmills, or oil rigs in their backyard either. Fun fact, coal emits orders of magnitude more toxic waste (including nuclear!) than nuclear itself; it's just stored in the atmosphere.

Also people largely don't want to cook themselves to death because the atmosphere has turned into a literal oven.

Instead they read the news, yap "oh my god 50degC shadowside that is horrible", turn the newspaper page and Gell-Mann-amnesia-forget about it because it's happening at the other side of the world, comfortably sitting on their couch with their HVAC pumping heat outside further contributing to the problem.

>> contributes little to global energy mix atm

Catch-22. Because there's not enough nuclear reactors.

France has a ~ 70% nuclear 10% renewable 10% fossil 10% hydro mix.

> France generates roughly two-thirds of its electricity from nuclear power, well above the global average of just under 10%. This heavy reliance on nuclear energy allows France to have one of the lowest carbon dioxide emissions per unit of electricity in the world at 85 grams of CO2 per kilowatt-hour, compared to the global average of 438 grams

https://en.wikipedia.org/wiki/Nuclear_power_in_France

>> uranium is limited.

Uranium is aplenty.

> more than antimony, tin, cadmium, mercury, or silver [~40x!], and it is about as abundant as arsenic or molybdenum.

https://en.wikipedia.org/wiki/Uranium#Occurrence

The problem is enrichment, and it is not even a technical problem. We're doing more difficult things producing nanometer scale compute wafers by the millions.

Nuclear has drawbacks. I don't think it is the endgame. I'm still waiting for anyone to come up with a less bad solution that actually a) addresses nuclear drawbacks and b) works, because all I see is yelling at nuclear and the proposed alternatives are either unobtainium or nothing at all, both equivalent to the status quo that turns the planet into a death trap.

FTFY, e.g nvim-treesitter:

https://github.com/nvim-treesitter/nvim-treesitter/discussio...

https://en.wikipedia.org/wiki/Lp0_on_fire

https://www.punkt.ch/products/mc03-premium-secure-smartphone

There's a little bit - but barely - more about AphyOS in the FAQ if you scroll way down.

- when hit by ransomware, disclosed publicly, bit on the data loss and told them to fsck off

- devices can very much operate without any account, app, or cloud connection (of course you don't get the more advanced "Connect" features)

- plug it in and you have rw access to .FIT files over MTP

- same mechanism to build and sideload apps made with Monkey C

- ANT+ is a fairly open ecosystem (progressively replaced by BLE, often in much less open ways)

I hear that some people are annoyed that devices stop receiving major feature updates after a year or two, and see that as predatory "you must upgrade every year", which is like, ridiculous?

Also in a sense I like that I buy the device and it's mostly "done". Like a mechanical watch it's a utility item I can rely on and it won't ever have a Liquid Ass pulled up on me.

I've had to explicitly direct the machine to read existing sibling code and follow the specific idioms and patterns in use.

See e.g the lock screen gap that another commenter noted in a nearby thread.

That 32GB or even 64GB is considered a minimum to be able to run some word processing, chat app, fetch remote content, and display funny cat photos is preposterous. In terms of information storage, these are absolutely immense numbers.

The infinite treadmill of chasing for more RAM and then immediately proceeding to carelessly fill all of it at the first line of code is part of a deeper, wasteful, and self-imposed obsolescence process.

We don't need more RAM, we need more frugal software.

Also I'm tired of doing these hacks:

    # increase to bust cache entry
    RUN true 42 && apt update

So is running `docker build` and the `RUN apt update` line doing a cache hit, except the latter is silent.

The problem solved by pinning to the snapshot is not to magically be secure, it's knowing what a given image is made of so you can trivially assert which ones are safe and which ones aren't.

In both cases you have to rebuild an image anyway so updating the snapshot is just a step that makes it explicit in code instead of implicit.

Even more damning is that there seems to be three independent layers to the feature ("three suggestions" area above keyboard, autocorrect-as-you-type, correction popup as you touch a word) and neither agree with each other about which language it should be using.

- it's non-obvious that the second mechanism (a file picker) is a permission granting mechanism.

- it's non-obvious that the second mechanism (a file picker) is a permission granting mechanism whose permission survives the action context that triggered the file picker (e.g "pick a folder to do action A" also magically imbues similarly gated actions B C D and Z with access to that folder, possibly non-interactively even).

- it's non-obvious that the second mechanism (a file picker) is a permission granting mechanism whose permission propagates to an action gated by the first mechanism, a first mechanism for which "Yes" means yes but "No" means "Maybe, depending on past unrelated actions that triggered an unrelated permission mechanism"

I really really disliked Accelerando in particular, finding it completely vacuous, the sciencey namedrops is self-aggrandising and sound like attempts at reader flattery, the entire plot is telegraphed, characters are generic and perfectly forgettable.

It was several friends recommendation and I only got reading through the whole ordeal because whenever I asked "well I'm about there and it doesn't click" they answered "no spoiler, just a dozen pages and you'll see!"

Not a critic, again this is my personal experience of it. If people enjoyed it, more power to them.