Back in 2012 I threw together something like this for managing UI dialogs in C#. For all the hate async/await gets about being an over optimization, it's good to see people find use for it as an ergonomic tool outside of concurrency
It may seem responsive if you run old software on modern hardware.
It was always slow on contemporary hardware. On affordable PCs Win 3.1 was so slow you could see it redrawing windows and menus. Win 95 was so resource hungry, people wrote songs about it (https://www.youtube.com/watch?v=DOwQKWiRJAA). XP seemed fast only at the end of its very long life, due to Longhorn project failing and delaying its famously shitty successor.
It wasn't just Windows. Classic MacOS for most of its life could not drag windows with their contents in real time. Mac OS X was a slideshow before 10.4, and Macs kept frequently beachballing until they got SSDs.
> Classic MacOS for most of its life could not drag windows with their contents in real time
There was shareware you could install which would do it though! Even on a 25 MHz 68030 it was surprisingly usable (more usable than the passive matrix LCD at least) https://www.youtube.com/watch?v=4cQo29SIIgU
That wasn't a hardware limitation. BeOS was outperforming Windows and Mac on the same hardware. If JLG hadn't demanded too much money, Apple would have merged with BeOS (and probably be a distant memory by now but that's a separate issue)
Not necessarily. Everyone saying HTTP/1.1 is simple has never implemented a full real-world-compatible parser for it.
HTTP/1 has lots of unobvious edge cases, and legacy quirks. Text format has way more flexibility than it seems from valid headers. It has obscure features like multi-line headers and old MIME features, 100-continue race conditions, custom hop-by-hop headers, GET bodies.
Fortunately new HTTP RFCs document many pitfalls. If you just implement what RFC 2616 said, you won't have a safe implementation.
Actual size of a request or response can be specified in multiple ways (at the same time, with conflicting values), and depends on a combination of several features, and values of headers with weird parsing rules needed for backwards compat, so "simple" HTTP implementations can be tricked into request smuggling.
Either way you need a robust, well-tested mature implementation.
That is not true for Tesla which automatically routes via charging stations when necessary. Tesla has an exceptionally good implementation that even re-routes drivers when chargers are busy, and they have top notch reliability.
There’s no hunting involved, you go where the nav tells you.
It's not so much that chargers are hard to find, whether Tesla or otherwise, it's that they're less common and may or may not be convenient to where you're staying or where you're driving while you're on your trip. If I was going to travel somewhere and rent an EV, I'd at least look on Google maps first to see where the chargers were, something I've never felt the need to do when renting a gas car.
This isn't an insurmountable problem, but most people don't like any additional uncertainty when traveling and that extra little bit of friction is probably enough to make travelers want gas powered cars. But I can also see that changing over time as more chargers come on line and especially if hotels start becoming reliable charging destinations. If I could rent an EV and charge at my hotel, that's way more convenient than looking for a gas station.
When I road trip with my EV, I prioritize hotels with chargers. While it's getting better, there really is no guarantee a hotel has a charger or that it's functional.
Or that even if it has a charger and it is functional that it won't be already in use or blocked by a regular car. I've had all of those happen before and it really is a crappy idea to rely on chargers in hotels. The only one this has worked at really well was a very posh hotel in Yorkshire that had a valet, I asked if they can charge my car and they did, the car was fully charged the following morning when they brought it out - but that's a place where the entire charging situation is managed by the hotel, so they knew how to do this and I didn't have to worry about it. I guess once you throw enough money at a problem it's "easy".
I travel a fair amount to mid-sized and smaller towns in the midwest. I've never seen an EV charger at a hotel. And in larger cities, hotel parking is often by valet.
>Tesla which automatically routes via charging stations
That's only true in certain situations: longer trips with superchargers. If you are renting a Tesla for a trip across the country, you're probably golden. If you're renting it for bopping around a city, it's not going to work as you propose. Even if there's a convenient Supercharger, you're likely to be doing enough short trips that you never trigger it to hit a supercharger.
On longer trips though: the Supercharger experience has been exceptional.
For reference: I've had a Tesla since 2016. Just last weekend I was in "the big city" coming home, and turned on navigation and it told me "You don't have enough charge to make it", and I had to do "navigate to supercharger" instead.
Whenever EV drivers describe their 'charging experiences', all I hear is ordeals, whether they think it was positive or negative.
It could be so simple: side payment card and done, with the only worry being the power output. (Still a worry that gasoline doesn't have, but OK, I understand that that's a fact of this infrastructure.)
I'm not going to be interested until I am not required to install random proprietary apps on my phone to charge, but I can just use my payment card.
Weird to make this complaint in an article about Teslas, when their charging stations work exactly as you hope. You just pull up, plug in, and leave when you're done. Nothing to install or log in or add payment details.
Gas: I'm driving West across the state of Colorado, I'm on I-70 in the mountains, with 2 other vehicles, they get dramatically longer range than I do. I can see 1-2 miles most of the time. My car tells me it's range, but I have no idea where the upcoming petro stations are, I just know that they're going to be "pretty frequent". So at 50 miles I start looking for a station. I pull off, I might have to wait, but usually no more than a few minutes, usually not. I have to mess around with the credit card reader. It's the better part of $100.
Tesla: I tell the car my destination and it tells me where I'm going to stop to charge and for how long. I pull up, I might have to wait but usually not. I plug in. It's free.
The one where the Tesla's battery system is miscalibrated and you run out of power three miles from the charging station it was routing you to. I'm a happy EV owner, but I'll never rent one again.
Meanwhile, to be fair, you don't need satnav to get to a gas station -- I-70 has signs a mile or two before every exit telling you which gas stations there are, just like the rest of the interstate system. I'd like to see another blue sign with charging stations, and which businesses you can relax in while you charge!
While the number of miles it shows for range is wildly inaccurate on the highway, the navigation does not seem to be impacted by that. When I've been unable to make the next charger, it has warned me a good hour ahead of time, and slowing down by 10-20 MPH has given me the range I needed. I've never run out before hitting a charging station.
I'm in agreement that I think they are terrible for most rental car needs.
I've been driving across Europe for decades now, and I have not even once worried about not finding a fuel station on time. Even without nav each most highway stations have a sign stating the distance to the next one, so if you like the excitement of nearly running out you can, but otherwise you just fill up pretty much whenever. The term 'range anxiety' hasn't come into our vocabulary until electric cars for a reason I think: it just wasn't there.
In a very distant past the only worry might've been if I had enough cash currency of the country I was currently in.
It's a bit different in the US, there are areas where they have signs up saying "X miles to next services" because of 50+ mile stretches without stations. I distinctly remember years ago trying to figure out how fast I could go across a section of Montana without running out of fuel between stations, so it's not entirely unheard of hear to have "range anxiety".
There are some stretches of 100+ km sans fuel stations in Europe too. It still isn't a problem, since you simply don't need to drive as much near the end of your projected range as you will in an electric car.
> I don’t want an exceptional experience recharging a car. I want a mundane experience. Just like a gas station is.
I understand that but you won't get there by expecting it day one. These things take time.
It's amazing to me the Tesla was able to roll out the best and most ubiquitous charging network in the US despite being a newcomer in a field that had absolutely no guarantee of catching on any time soon.
In Norway we have more chargers in the big cities and fewer out in the country side or up in the mountains. This means that if you rented an electric car for your Easter holidays and drove up to the mountains like a lot of other people do then you would be routed to a charger with 20 cars in line to charge in front of you.
I’m guessing the problem here is that Hertz didn’t have chargers. I rented and EV was allowed to return the car with 10% battery. The rental, I assume, had a charger on site. It was a super great experience. I would not use hertz if I had to charge the car upon return, and I say this is a Tesla owner knowing how the charging navigation works
But it still takes time, more so than a petrol car - and when you rent a car, that's exactly what you are paying for.
It's fine if that time is while you are asleep, or at your destination - but the last thing I wanted to do when returning the car before a flight would be to wait for ~30 mins for the thing to charge up, no matter where the app would direct me to.
Logically you'd have a supercharger at the car rental depot to try and relieve this problem, but alas, the last time I was renting a car, and was considering an electric one from Hertz, this was not an option.
One fun thing about returning the car less than fully charged is that the cost of recharge is just labor. I think they billed me $15-25 for it when I left a car without fully charging it.
Gas stations are ubiquitous. Charging stations are not.
You don't need to use any brain power to fill up a gas tank. I've never driven an EV before. When I'm on vacation or business trip, not sure I'd be in the mindset of learning how to find a charging station and charging a car for the first time in my life.
learning how to find a charging station and charging a car
I'm traveling to a foreign country and renting a car in a few weeks and this is the main reason I don't want to rent an EV. I know I can work out how gas stations work there, I have no idea if can work out how to charge a car (Do I need an app? will that app work on a foreign phone? Do I need a local address/credit card to create an account with that app etc. etc.)
I like to use nav as little as I possibly can. On road trips I usually look at the route once in the morning, then turn it off and don't look at it again the whole day. Feeling tethered to the nav sounds like a total drag.
If you are using Tesla's map. If you have paper directions because GPS doesn't get you there (happens all too often to some destinations) you won't have that. If you have already made the trip 3 times this week (common on a business trip) you know the route and may not use GPS anymore.
Gas stations are all over. I have high confidence in most places that when I notice the gas gauge is getting low I will see a gas station in about 10 minutes without a any detours. By contrast EV chargers exist but you will not see every 10 minutes no matter where you go.
If you own a Tesla you might know that and even trust it. As a potential renter, I don't know that and will still need to make sure there are chargers near where I am headed.
...and also means that (a) your battery will be heated ready for a fast charge when you arrive, (b) the charger will likely actually be in operation, and (c) you can start charging your car as soon as you plug in without messing around with apps or cards.
Here in the UK at least, you still don't reliably get (b) or (c) with non-Tesla chargers. Though that is seemingly starting to change.
It cuts both ways — there are companies that know how to build a car well, but have no clue how to manage batteries, use electric motors efficiently, and are institutionally incapable of writing even half-decent software.
So far it seems that tech and battery companies (Tesla, BYD) may catch up on the car things quicker than Toyota or Stellantis learn how to make an EV drivetrain that doesn't suck.
Hyundai/Kia Highway Driving Assist (HDA2) is really good. They're price competitive. Their charging speed can exceed Tesla's, and you get physical buttons, 360 camera, and a HUD that you can't get in a Tesla.
My impression from Rust/LLVM bugs is that LLVM is only a C++ compiler, except where people complained long and loud enough.
Rust had to add patches to support optimization of Rust allocators (not just malloc and new). Ran into several bugs in mutable aliasing that doesn’t exist in C++ and is very rudimentary in C. Spent seven years fighting with miscompilations due to a C++ rule that infinite loops are UB. Had to implement custom float to int casts to avoid C UB, and so on.
Maybe it's time to dramatically simplify autoconf?
How long do we need to (pretend to) keep compatibility with pre-ANSI C compilers, broken shells on exotic retro-unixes, and running scripts that check how many bits are in a byte?
https://docs.rs/glib/latest/glib/struct.MainContext.html#imp...