Extremely interesting and also humorously written. Considering that Firefox once changed its plugin system to become more secure, you can still cause quite a lot of damage with plugins. By now I get by with very few plugins. I think everyone should try to use as few as possible.
I have the feeling there are even more plugins for Chrome, right? That would certainly be worth exploring too.
The author mentioned there were far more in the chrome store, and it would be impossible to download them all in the same way he did here.
Anything that can inject content into webpages you load has pretty extensive abilities for abuse, let alone extensions with more access to browser APIs.
I tried for a long time to work with Thunderbird, but what kept bothering me was that I couldn’t simply define keyboard shortcuts. In the end, I landed on AERC and created my own extreme Vim-style keyboard configuration (the idea is to look at the list of mails like looking at a buffer in vim) for it. I’ve never been this fast when it comes to email.
Building nuclear power plants still takes the longest. Especially if you want to produce the same amount of energy that will be needed in the coming years. Currently, nuclear power plants supply about 9% of the electrical energy used worldwide — and it has taken us from 1950 until today to get there. Why should it suddenly be faster and more elegant now? We also don’t have the money to pursue both in parallel.
Yes, I know China and to some extent South Korea build nuclear power plants faster. But even there, some plants have taken up to eleven years to build, and others that were built quickly only achieve a capacity factor of 60%. At least in China’s case, many of the conditions cannot be directly transferred to Western countries. Space, social and political circumstances, and other factors are simply not the same everywhere as in China. Moreover, even China, whose share of nuclear energy in its electricity mix is around 4.5%, is finding that renewables are much faster and cheaper.
> We also don’t have the money to pursue both in parallel.
According to what?
We're not spending that much money overall. In particular the US government is putting very little into energy infrastructure considering its spite for renewables.
> Moreover, even China, whose share of nuclear energy in its electricity mix is around 4.5%, is finding that renewables are much faster and cheaper.
The cost of renewables starts to grow when they get over 50% of the power mix.
I'm not opposed to enabling 95+% renewable power by having an army of natural gas peaker plants on standby, but I think nuclear could be cheaper if we gave it an honest try.
Nuclear power plants produce CO₂ emissions. The only point at which they do not emit CO₂ is the electricity generation itself. Everything that happens before and after produces CO₂. The amount of CO₂ is debatable, even the major meta-studies (UNECE 2022) point out that across all collected studies, parts of the lifecycle emissions are consistently missing because, drumroll, the nuclear power industry is so non-transparent.
Important factors include the mining of uranium ore. If the concentration of uranium ore in the rock is low and the more nuclear power plants are built and the more ore is needed, the sooner such deposits will have to be tapped, mining becomes increasingly CO₂-intensive. The same applies to enrichment. Both processes would greatly benefit if renewable energy were expanded to the point where uranium mining and enrichment could be operated with lower CO₂ emissions.
You can install solar panels over areas that are already developed — rooftops (lol), parking garages, highways, and so on. Some agricultural land even benefits from being covered by solar panels. This has great potential and was first researched in the United States. China is covering water reservoirs with solar panels, which has the additional positive effect of reducing evaporation. And then there is the incredibly large amount of energy that the North Sea, far from any beaches or islands, could provide in consistent wind energy.
Rooftop solar is prohibitively expensive in Germany. My installation would only cover its costs if electricity becomes so expensive that it would lead to complete economic collapse.
No. In Germany, rooftop solar is usually economically attractive, not prohibitively expensive. Especially on a decent roof and if you use a fair share of the power yourself. Verbraucherzentrale(1) says PV systems for private homes are “usually worthwhile” economically, and that self-consumption is the key driver of profitability.
But 2011 was not the year the nuclear power plants were shut down. However, that is the year your previous commenter was referring to. So what exactly are you trying to say? Incidentally, the electricity that the nuclear power plants had supplied was not replaced by coal power plants, but by renewable energy.
There was not a single moment in time in which all nuclear power plants were simultaneously shut down. The shut down was gradual [1]. 2011 is relevant because it is when the German government decided to phase out its remaining nuclear power plants.
The SCBOE score is a good idea. However, in the case of Germany, it is often overlooked that the power grid dating from the 1970s, which was built as a one-way system from large power plants (nuclear power plants) to consumers, would have needed to be rebuilt regardless. A large share of the grid costs would therefore have been passed on to consumers even without the transition to renewable energy. Additionally, Germany is located in the center of Europe and is thus a major transit country for electricity. Here too, corresponding capacities would have had to be expanded. The expansion of a European power grid also means that the disadvantages of renewable energy variability can be offset. As the SCBOE system also shows, the individual power plant still accounts for the largest share of costs. Many of the additional factors can actually go down in prices as renewables scale up (nuclear has still to prove that this could work there too). In that regard, LCOE remains relevant.
For the next three intriguing articles you see on arbitrary sites, does the select all trick produce an aesthetically pleasing email? Do external dependencies get carried over? Do you spend any time manually removing cruft? Does the formatting leave anything to be desired?
When I do this all manually I can make it look great, and now that we’ve seen we can train computers to make stuff look great, it’s going to be a point of frustration for me until I have the one-click beautiful-article-email button.
"You’ve all experienced the Fundamental Failure-Mode Theorem: You’re investigating a problem and along the way you find some function that never worked. A cache has a bug that results in cache misses when there should be hits. A request for an object that should be there somehow always fails. And yet the system still worked in spite of these errors. Eventually you trace the problem to a recent change that exposed all of the other bugs. Those bugs were always there, but the system kept on working because there was enough redundancy that one component was able to compensate for the failure of another component. Sometimes this chain of errors and compensation continues for several cycles, until finally the last protective layer fails and the underlying errors are exposed."
I've had that multiple times. As well as the closely related 'that can't possibly have ever worked' and sure enough it never did. Forensics in old codebases with modern tools is always fun.
> As well as the closely related 'that can't possibly have ever worked' and sure enough it never did.
I had one of those, customer is adamant latest version broke some function, I check related code and it hasn't been touched for 7 years, and as written couldn't possibly work. I try and indeed, doesn't work. Yet customer persisted.
Long story short, an unrelated bug in a different module caused the old, non-functioning code to do something entirely different if you had that other module open as well, and the user had disciverdd this and started relying on this emergent functionality.
I had made a change to that other module in the new release and in the process returned the first module to its non-functioning state.
The reason they interacted was of course some global variables. Good times...
By the way, a corollary I encountered, I think with one of the recent AWS meltdowns, is that a paradoxical consequence of designing for "reliability" is that it guarantees that when something does happen, it's going to be bad, because the reliability engineering has done a good job of masking all the smaller faults.
Which means 1. anything that gets through, almost by definition, is going to be bad enough to escape the safeguards, and 2. when things do get bad enough to escape the safeguards, it will likely expose the avalanche of things that were already in a failure state but were being mitigated
The takeaway, which I'm not really sure how to practically make use of, was that if a system isn't observably failing occasionally in small ways, one day it's going to instead fail in a big way
I don't think that's necessarily something rigorously proven but I do think of it sometimes in the face of some mess
That's a fairly common pattern. As frequency of incidents goes down the severity of the average incident goes up. There has to be some underlying mechanism for this (maybe the one you describe but I'm not so sure that's the whole story).
I have the feeling there are even more plugins for Chrome, right? That would certainly be worth exploring too.
reply