I believe that it's a physical plant thing. We have spent over a hundred years building hydrocarbon-based energy infrastructure. Much of that is still out there. Wind and solar have made a ton of progress in the last 15 years or so, but it's only really become substantially better financially in the last 5 or so years maybe. It's still going to take decades to actually replace most of that stuff, just as a matter of how fast we can build and install hardware.
Note also that it's a worldwide chart, so it includes developing countries that may not be so quick to jump on projects that are expensive right now even though they'll save a bunch of money in the long term. Though to be fair, some may have a leapfrog effect when it comes to building brand new infrastructure.
I would like to think that the switch to renewables is inevitable, but could a continuous series of administrations similar to the current US admin be enough to curtail it?
Seems unlikely to me. I always thought the only engine that could actually accomplish transition was capitalism. We will transition at a time and to an extent that renewables are actually cheaper and better, no sooner and no later. Government action can encourage technological development, but it can't force the transition when the technology is not ready yet, and it can't stop it either once it's actually better. Note that we are actively building out a lot of that stuff now, even though the current administration is at best indifferent towards it. It all fits with the bottom line that we transition when the technology is ready, and the opinion of activists and Government officials isn't relevant.
Coal is dirt cheap, to the point where most of the cost is in transporting it and the infrastructure to convert it to power is simple and not very capital intensive to it’s the first thing developing countries reach for when they don’t have strict environmental regulations. It also doesn’t require as much precision manufacturing so a lot can be done domestically even in less developed industries, which is important when foreign currencies are in short supply.
The problem is where it's measuring joules of energy. To use cars as an example:
It measures joules of energy as in "how much heat the gasoline we burn produces", some of which we convert to mechanical energy to drive the car, but the majority is just waste heat going out the tailpipe.
By comparison an electric car powered by solar has no tailpipe. There's still a bit of waste heat from electrical resistance, but nowhere near as much.
If we measure like this, by converting a gasoline car to electric (powered by solar for the sake of ignoring some complexity), and driving the same distance, we somehow managed to cut our "energy demand" in half. Despite the fact that we're demanding the exact same thing from the system.
If we measured "joules delivered to the tires of the car" we wouldn't have the same issue. At least until someone starts arguing about how their car is more aerodynamic so joules delivered to the tires should count for more in it.
Edit: We could also go in the other direction. Instead of reporting it as 1kw of solar energy (electricity) it could be 4kw of solar energy (the amount of sunlight shining on the solar panels)... No one does this for obvious reasons, but it's more similar to that primary energy number for fuel in many ways.
The total energy supply figure is a primary energy mix - for the fossil fuels it represents the thermal energy of the fuel. You can look at the final energy consumption section a bit lower to get a different picture taking into account conversion losses.
That is still subject to the primary energy fallacy. Those reports are in terms of primary energy, i.e. how much heat is released by combustion of fossil gas. But in order to replace fossil gas in a chemical plant, you need much less electricity than the primary energy of the fossil gas suggests.
> For all energy sources, the IEA clearly defines energy production at the point where the energy source becomes a “marketable product” (and not before).
Doesn't that mean if you are burning coal to make electricity, you wouldn't count the heat output because the generated heat is not a marketable product.
Looking at the chart for TFC, the wind and solar case looks even worse. Wind and solar supplies 2 million TJ compared to 36 million for coal.
All I was really trying to say from the outset is that I'm surprised at how important coal still is and how little we use renewables. I see articles here all the time about the massive advancements in solar (and wind to a lesser degree) and I had it in my head that renewables were a much larger part of the energy mix than they are.
Some people go all the way down to 1 or 2 bars (soup espresso). I've mostly seen it in the context of very light roasts and I tend to buy darker roasts so I really haven't spent much time investigating it.
I did see a video on americano's recently where steaming the water to heat it rather than using a kettle or water from the espresso machine's boiler made a better drink. That does intrigue me and I'll probably give it a try this weekend.
Lately I've been making mostly decaf and it's really hard to get a good shot no matter what I try. Drip coffee comes out great, but my decaf espresso always seems to have a real harshness. Beans are fresh and my water is good, so I'm thinking it's time to replace the burrs in my grinder.
1-2 bars isn't really espresso, it's a moka - which can be quite good in its own right. It falls into the genus of pressurized brewing though, so same genus different species. There's a no man's land from 3-5 bars that is not really used and might be worth exploring, but most 'standards' consider 6 bar the minimum to be a true espresso.
The SCAA (Specialty Coffee Association of America) has an even more restrictive definition[1]:
> Espresso is a 25–35ml (.85–1.2 ounce [×2 for double]) beverage prepared from 7–9 grams (14–18 grams for a double) of coffee through which clean water of 195°–205°F (90.5°–96.1°C) has been forced at 9–10 atmospheres of pressure, and where the grind of the coffee is such that the brew time is 20–30 seconds. While brewing, the flow of espresso will appear to have the viscosity of warm honey and the resulting beverage will exhibit a thick, dark golden crema.
I have no problem with calling soup espresso. It's ground coffee brewed under pressure in an espresso machine and that's good enough for me.
Of all the standards, I find the SCAA the least useful. That was the standard 30 years ago, but nobody serious about improving their craft is brewing such a watered down espresso anymore, and a 1:2 ratio is the most common one. So 15g for 30ml. And for pressure, modern consensus is that 9 bar is the high upper limit. 10 almost always leads to a harsh cup. I find the 6 bar lower limit to be a tipping point in the concentration, such that lower pressures are more similar to drip than to espresso - the viscosity and mouthfeel changes dramatically. So I can't agree that whatever comes out of an espresso machine should be called espresso. But we are debating vernacular here, I just hope you enjoy your cup of coffee!
> steaming the water to heat it rather than using a kettle or water from the espresso machine's boiler made a better drink
Was it Mr Hoffmann[0]? He has a decent explanation for why this might be the case too (and does an experiment later which points to it maybe being dissolved gases.)
Yes, that's the video. He doesn't seem to be a fan of americanos. It's one of my favorites so I'm pretty interested in new ideas for one of the most basic drinks.
I developed my first Android app when I was around 16 years old and I remember distinctly wanting to publish it on Google Play, but couldn't because they required developers to be 18+, and this was even before they introduced strict identity verification requirements. And iOS was a lost cause as XCode famously requires an operating system that only runs on very specific hardware for which I had no money. No matter, I published an apk on a website and ended up reaching a few tens of thousands of users that way. My app ended up transforming a (niche) industry and making a real impact on the world.
If Android isn't open, we lose the last open mobile operating system, which will have immeasurable negative effects on computing as a whole. People will need permission from either Apple or Google to create any mobile program. If you don't fit into their neat little system, you don't get permission. If I hadn't been able to publish my app for another 2 years I probably would've shelved it, decided it was stupid, forgot about it, got busy with other things, and never published it.
This is why I really wanted Capyloon to take off [1]. The idea was to build a whole mobile OS around PWAs. App Stores are just CDNs. There are no weird rules about payment processors. The ecosystem did not need to start from scratch.
Unfortunately, it just never gained the necessary momentum.
I was as well. It was very early, but not necessarily too early.
I think part of the problem is that they decided to have the flagship devices be low-end hardware, rather than high-end hardware. They were trying to ensure that development took low-end hardware into account, but they failed to consider that by the time the platform grew, high-end would become mid-range.
It's hard for me to know for sure, but to me it felt like the fact that none of the firefoxOS phones were targetted as devices developers would themselves want to use as their main phone was a big misstep in strategy.
I actually use the ability to install custom software on Android. I actually use the ability for Android apps to bundle JITs, and language interpreters, and other things that allow you to extend the app at runtime. The Apple walled garden would be unusable for me. And moves like this one to turn the Android ecosystem into the Apple ecosystem will generally be regressions.
If anything, I'd like more openness in Android. For instance, apps should not have any control over what data I can back up; I should be able to back up every aspect of every app, restore it to a new phone, and apps should not be allowed to care.
You can download torrents on an android and plug usb media devices into it. When I was bicycle touring Europe with my wife a couple years ago we constantly downloaded books for direct input into our kobos and shows and movies to fall asleep to at night you could play from random, often old and crappy, hotel and airbnb televisions. You can’t do any of that on an iPhone.
That said; iPhone is my main phone, has been for a decade or more. But I deeply appreciate what you can do with an android.
I used to build custom apps for my Android all the time, install APKs, transfer files over USB, use USB tethering on my Linux computer, torrent, use a mouse and keyboard (I think iOS can do this now though), use the integrated terminal, etc.
A few years ago, iOS lacked basic features like widgets, NFC, calculator on their tablets, etc. And iOS still has a completely inferior keyboard (I used to write code and essays on my Android while walking) and a completely inferior notification system. Androids are also the only phones still offering a fingerprint scanner, which is way better for me. These nice things all combine well with the oppenness.
What's worse is that we're clearly in a progression of restriction. Bootloader restrictions, app installation restrictions, "age verification" requirements, etc. Openness is being locked down from every angle with serious momentum, it's not anticipated to stop here.
The openness of Android also acts as a check of sorts on how restrictive the walled garden can get. If google were to clamp down on useful functionality in the play store, then you could always install apks yourself. But if the latter is no longer an option, then there's much more temptation to google for the former.
I get the feeling that clamping down on useful functionality is often an unfortunate side-effect of closing down paths that are being exploited by criminals to harm users.
What should Google do when a change they are making to protect regular less-technical users breaks functionality needed by more advanced users?
If the user must click through a tons of disclaimers (including locked 60-second timeouts with huge WARNING: SCAM ALERT or something) in something buried in settings to get scammed, I think the few edge cases may be worth the tradeoff of being able to install apks.
Remember there is already malware-scanning by default (by Google play), apps need to ask for permissions, they generally can't read other app data or control say banking apps, modify system data (at all), etc..
The threat vectors seem already restricted. I haven't met anyone which has fallen to actual Android malware ever (that I can remember), but I can remember several close family members which were victims of simpler social engineering scams (mostly unsuccessfully) recently.
The problem with the toxic max-security[0] arguments is that it is always possible to invent a more gullible fool. There is no security measure that will perfectly protect a user from getting scammed out of everything, save for scamming them first and then treating their property as your own. That's the Apple argument. The only way you can keep people secure without falling into the same rhetorical trap Apple employs is with bright red lines that you swear not to cross, no matter how many people wind up getting scammed, because at the end of the day, people are adults, and their property is theirs.
Furthermore, we have to acknowledge that scam-fighting is not Google's job. They can assist with law enforcement (assuming they do not violate the rights of their customers while doing so) but they should not be making themselves judge, jury, and executioner in the process.
If you want a more concrete technical recommendation, locking down device management profiles would be a far more effective and less onerous countermeasure than putting a 24-hour waiting period on unknown app installs. Device management exists almost exclusively for the sake of businesses locking down property they're loaning out to employees, but a large subset of scams abuse this functionality. Part of the problem is that installing a device profile is designed to sound non-distressing, because it's "routine", even though you're literally installing spyware. Ideally, for a certain subset of strong management profile capabilities, the phone should wipe itself (and warn you that it's going to wipe itself) if you attempt to install that profile.
Requiring every package in F-Droid to pay a developer licensing fee is not protecting anyone, in fact it will make people less safe. The whole model of F-Droid relies on free software, needing to pay a license fee to Google banishes people who have no profit motive - Google is explicitly banning a nonthreatening group of developers.
> What should Google do when a change they are making to protect regular less-technical users breaks functionality needed by more advanced users?
Have people read and type in a message saying "I'm not on the phone with a potential scammer who is trying to get me to install a package that may be dangerous", trust people to actually read what they're typing, and if they can't read and comprehend that, stop getting in the way of them shooting themselves in the foot.
That requires having a PC to unlock basic functionality on your Android device, assuming the change we're talking about is still app installs.
I don't think OS vendors should be expected to keep people from doing dangerous things. A warning label saying "hey that's dangerous because..." is reasonable, but anything more and they're trying to be my sysadmin against my will.
The sysadmin part is their value-add. One reason my current phone being an iPhone after being 100% Android for a decade are the better walls and nicer garden.
These are sold as consumer devices and not general computers. It sounds like you want something different. They’re selling cars and you want a motorcycle.
Android was very open when it was released and for some time after. Installing APKs directly was easy. Most devices had unlocked or unlockable bootloaders. An Android phone treated its user much like a PC did.
More sysadmin-as-a-service type stuff is fine as long as the opt-out is easy. This isn't. I'm upset about the rug pull.
I understand. I was one of the 25 people excited about the OtherOS option on the PS3. When Sony removed that in an update I was bummed because that’s one of the reasons I bought it.
You never know though. Sometimes things go the other way. When the iPhone launched there was no way to create apps for it or install third party applications except as web apps.
People keep framing it as tinkerers versus normies. That's not the real problem.
The real problem is that prior to verification, Google can't ban ICE tracking apps (or whatever the next problematic government doesn't like) from Android, and after verification they will be able to for most users.
They say they won't do that. I might even believe the people currently running things won't do that, but they will be incentivized to do that in the future, and incentives are much better at predicting outcomes than intent.
I reject your premise. I do not believe that the primary motivation here is to protect less technical users. However even were I to accept that, I would say the change is an unacceptable one thus they should either figure something else out or do nothing.
I think they know that they are going to lose some users.
If you are a fan of open source, maybe this will be a good thing. Maybe this will drive more people and money to open source projects directed at making a better mobile OS.
>For you, is the openness of Android appealing as a matter of principle or does it enable you to do things you couldn't otherwise do?
Both. I don't like the idea of locked down computers and that includes phones, especially now that they're so prominent in our lives.
I dabbled in Android development for fun a decade ago and I loved how there was no barrier to entry. I've loaded apps that aren't available on the Play Store and have loaded apps that my friends have made just as fun side projects.
There was a handheld gaming system in the early 2000s called Cybiko. Cybiko and Sega Dreamcast homebrew opened my mind up to the power of computers and having control of your hardware. These things should not be locked down. I liked messing around with making little programs on the Cybiko and downloading homebrew games for it and the Dreamcast. The openness of Android really excited me when it was new because I thought of it the same way as a Cybiko or Dreamcast or PC and not a locked down device where I can only run software approved by the hardware manufacturer.
I modify several apps for my own use in ways that wouldn't get accepted upstream (or are proprietary), and I modify OS components to reduce the impact of opinionated Google UI design (and Apple is worse in this context).
Both, very much both, and I would assume that the 'actually being able to use the device in whatever way I want' feeds back into the 'this should be a thing we can do with purchased-to-own hardware' feeling
I'll chime in with a really basic example. On my Android phone, I can have syncthing run as a background task. I can point other applications to use a data folder, in my syncthing share, and store their persistent state there. The Camera app, for example. Or Obsidian, my current favorite note taking app. Syncthing, by virtue of being always on and manipulating a decades old, very well understood filesystem concept, "magically" syncs all of these changes to every other device I own. Entirely offline, even if the internet is out, because the devices can just talk to each other.
So far, I have been utterly incapable of getting my iPad to do anything remotely similar. It can run syncthing, technically, but not in the background. Apps don't have a shared filesystem structure, so it's difficult to get anything else set up to "save within my shared folder" in a way that would work, and that disregards that the syncing cannot occur when anything else is open. There's all sorts of cloud backup options, but those require the internet and even when they're working, there's this awkward import/export flow that adds friction to the whole dance.
In isolation this would just be a small papercut, I guess, but these sorts of limitations are all over iOS. It's just terribly hostile to anyone not fully committed to the Cloud-first, Apple-hardware ecosystem. Android doesn't care, and doesn't have to care, because it lets me run the software I want. It's a really small set of programs too, at the end of the day. (Firefox with real extensions is the other one.)
This is the exact reason we switched my wife from iPhone to Android – because her iPhone couldn't sync reliably for our shared password vault or for Immich.
Well for instance the top app on fdroid is apparently "simpmusic" which would be impossible to run on an iphone because apple doesn't allow apps like it [1]... and it has 800k downloads from f-droid by itself.
To be clear though android isn't stooping to Apple levels yet. You can still do anything, it just makes it obnoxious to do so.
Your best bet is probably to attach a VCR, if you can find one; they generally have a tuner, and I think most TVs still usually have a component input and/or, in Europe, SCART.
I'd be a little surprised if anyone still makes a TV with an analog tuner.
Do you really want a universal app engine? If you don't have a good reason for ignoring platform guidelines (as many games do), then don't. The best applications on any platform are the ones that embrace the platform's conventions and quirks.
I get why businesses will settle for mediocre, but for personal projects why would you? Pick the platform you use and make the best application you can. If you must have cross-platform support, then decouple your UI and pick the right language and libraries for each platform (SwiftUI on Mac, GTK for Linux, etc...).
Platforms and app engines are orthogonal concerns. I agree that platform guidelines are worth preserving, and the web as a platform solves it by hijacking the rectangle that the native platform yields to it. Any app engine could do the same thing.
reply