Once EVs are produced in the same volumes as combustion cars today then the price for an EV will be the same, and probably lower as EV cars are much simpler and contain less components. Right now there is probably also some markup added just because the manufacturer can charge more for an EV (status, more demand than production capacity etc).
The charging time will likely also go down further which could allow for the batteries to become smaller for most use cases and thus the price come down even more.
And on top of that, if energy prices continue to stay high, the SUV/Truck era might slowly die away and smaller/lighter/aerodynamic cars with better mileage will become the norm. Less metal and smaller motor needed means cheaper car.
But you can always change CDN provider in a few minutes, an hour or a day.
You cannot move from Twitter to SomeOtherUnknownPlatform.com or from the App Store to UnknownAppStore.com if those platforms decide they don't want you there. Well you can, but no one will ever see you again. You cannot even move to a well known platform in case your followers are not there (or don't use that OS). At least, it will take years to move them over.
That's like saying that your application that is running in AWS can easily be moved elsewhere, but that's going to be true only sometimes: a lot of the time you'll use their managed services (which may or may not be compatible with others), their SDKs for setting up the infrastructure (which may or may not be trivial to migrate) and might end up with a lot of knowledge that's largely only valid within their ecosystem.
But that's mostly because a lot of the larger service providers out there try to expand their market reach and provide lots of different services: like I could go to my domain registrar and get either managed hosting or VPSes.
The system predates the popularity of installable PWAs. It is basically an exec spawning a Qt Web view and a server process then the Web view connects to local host. Server process shuts down when the Qt UI is closed. The server process is just Java with a webserver lib.
The binary is built for those OS and installed via installers idiomatic for those systems.
It defaults to use a local sqlite backend but could use any rdbms. Simple really.
Yes, you are right, knowing the clock rate and duty cycle would be interesting to know. And knowing what the MCU is actually doing. Powering an MCU from a lemon or potato is nothing new and has been done with more than 30 year old MCU's, implementing clock's etc.
More challenging is probably to power a complete system, i.e. everything around the MCU, like driving Ethernet or WiFi or BT as well as some analog sensors and the like. Embedded MCU's do not require much and if you can spread out the computing needs over time, no big deal.
Look at Casio watches and the like which you can run for 10 years and they provide quite some features. It's okay as long as it is features that stay within the MCU/Display realm. Now, the watches which provide BT, GPS, different sensors etc kind of suck in this regard.
Also from a user perspective there are many benefits with a software that exists on many platforms. It's often better with a slightly less good/snappy app that runs on all platforms than a perfect app than runs only on one platform. It's a feature.
It could also be said that it's a feature that the app does not 100% follow the native UI as the experience will be the same irrespective of which OS you are on.
Is it a feature, that MS Teams (as a default setting) does not use native notifications on OS X? As a user, I have to disable two notifications now, because one does ignore the system setting. I don't know how to sell that "feature"... Imagine having many apps with each having it's own notification setting, layout and appereance.. That's hardly an improvement to the status quo.
That is only a feature for app developers and (especially) the marketing departments of companies who do so, not platform users. I use non-platform native UI as a leading indicator of contempt for users.
Electric wire bus is better than tram as it does not require expensive tracks. It is also much easier to change the route. The tracks also create a lot of noise and vibration that gets into nearby buildings. Tracks are also dangerous for bicycles, and slippery for cars and trams.
There might be benefits with trams, but I do not know what.
Not having a consumable battery pack which has to be replaced, and mineral resources expended upon making new sets?
There is obviously a trade off, some routes are obviously suitable to trams, some others to buses, be they all electric or hybrid. So possibly in ICE mode out of urban areas, and on battery within?
> There might be benefits with trams, but I do not know what.
Good tram systems don't share the asphalt except at intersections making public transportation a win for the individual which in turn reduces traffic. Buses always suck, that is an important part of their design.
They should be, at least. San Francisco runs historic (interesting, attractive) cars on the Market Street line, some of which sound and feel like the rails are surfaced with gravel.
Every time I ride one of the orange cars from Milan Italy, I am reminded that the Milanese in the 1930s had bigger things to worry about, and that I should just get over it. :)
Isn't that what calendars are for? Most of the time they are pre-installed on all OSes and they handle recurring schedules and notifications. On Linux I use Thunderbird for email with the Thunderbird Lightning Calendar [1]. I sync phone and desktop using CalDAV.
In my mind I put those reminders in the group of “things to do”. Just like I need to do whatever task of the day, I need to do that accounting tasks if the happens to be the first week of the month. So I like them to be in the same place.
Btw, I decided for Todoist. The recurring reminder is on the premium plan, but I am using a good enough process: I set the recurring tasks to have a deadline of, e.g. the 5th of next month. Then, when I get there, I will set the deadline for the next month and so on. And I grouped these tasks in a group named “Recurring”.
