Different person, but I don't want a car that has an app precisely because it's so expensive. Cell phones her replaced way more often, and the people running the app stores are very aggressive about not supporting old apps. So within maybe half the life of the car, the app will no longer install.
Yeah, my phone barely goes out of date and can't install some apps. My wife's phone is too old to install any. I'm not going to accept an obligation to keep installing new and worse OSes (eg liquid ass) on my phone until I have to get a new phone, I'm just not going to use apps.
They're already at the kind of range I'd be happy to trade off the other way.
I don't need 400 mile ranges; I'm happy to half that to get a shorter front so I can see the corners, a squared off hatch at the back, and proper headroom. Basically give me a smaller Transit van.
Unfortunately people are convinced that they would rather spend 10 minutes a week at a gas station rather than have to do one 30 minute charge on a road trip once a year.
Its reliably improves as the British engineering is reduced... These EV trucks are going to be running for 100 years. No crazy Chinese firmware, no bonkers Musk autonomy, charge them from the solar on your roof, enough torque to pull a semi trailer out of a ditch.
It's precisely because these EVs don't repackage android or attempt to remain internet connected that will allow them to keep working on the software side. Embedded firmware (for ISO/IEC 15118 comms with the CCS2 port) for charge controllers is about as sophisticated as it gets.
Oh, its good at doing desktop applications these days? Which GUI libraries are good these days? Some native win32 binding? Are there good equivalents for Qt?
I'm interested in getting back to native application development; the job is on Electron right now and it's… meh.
> Oh, its good at doing desktop applications these days? Which GUI libraries are good these days? Some native win32 binding? Are there good equivalents for Qt?
If your goal is "delivering applications to only well-sighted people who can handle non-native and buggy UI", yes iced, EGUI, gpui exist. But as you can guess they are years behind Qt where you have quite the professional toolkit and properly implemented accessibility features (with a lot of bugs and horrible API because Qt).
The only foolproof way of having truly professional software is still the same: have N different, very-well integrated UI implementations (like Adobe does, $$$ in developer or agent fees) or use a Web browser aka Electron.
With Rust you can use Win32 or WinUI3. Both are provided by Microsoft-developed crate windows-rs.
Note: You ask different people, and they will all have their favorite tool kits. GPUI is very promising but new. There are a pile of others people will vouch for like Druid, Tauri (Electron-like but faster?) Slint (As the sibling poster pointed out), Iced, Qt bindings etc. I am not sure about native Windows etc bindings: I recognize that OS-native things like that are the most performant, but for me it's worth it to make my programs cross-platform and not worry about OS-specific things.
Note: EGUI is an immediate mode GUI, which isn't for all applications. But it has never limited me, and have written some complex UIs with integrated 3D etc.
> In fact I believe they could've simplified it further by getting rid of station codes. Which passenger needs to know Dhoby Ghaut is NE6/CC1/NE24?
I believe they're usually for people who can't read the language (typically, tourists). NE6 is a lot easier to memorize for people who can't pronounce Dhoby Ghaut (think people from China or something that isn't used to reading Latin alphabets).
The code + number system is also easier for tourists / people new to the area to know which stations are on the same line, and to find them if you don't know the map (just find any station on the same line and look for the correct number on the line).
Also, as mentioned elsewhere in the thread, more scrapers. They're trying to keep things accessible without JavaScript, which mostly rules out the typical proof of work solutions like Anubis (which they're definitely aware of, as they had an article on it).
LWN is a poster child for something that could be entirely static pre-generated HTML for literally all unauthenticated requests at a server cost lower than serving and verifying anti-bot checks. If Anubis provides any benefit at all then they are really doing something wrong like fetching a bunch of comments from a database and generating the resulting HTML for each visitor.
Up to Win2k, I don't recall new releases of Windows leading to people lamenting the UI changes; I do remember people not liking the initial look of XP, though. Maybe it's just because complaints got more visible after the Internet became popular, though. But even now few people seem to have strong preferences for, say, Windows 1.0 (… which was pretty much a TUI, IIRC)
I believe Win9x all had basically the same UI appearance, and 2k just changed the default colours slightly (and they were always fully customisable, so no difficulty in changing them either.)
Windows 1.x/2.x were noted for being rather primitive, and similar to the "flat design" trend hated by many when Win8 came out. 3.x is when the UI elements became 3D, and then they retained nearly the same appearance until XP introduced the bitmap-based theme.
IIRC win2k introduced some transparency effects and shadows, like when menus would gradually appear from transparent to fully opaque (I don't know the right word for that.) I found it really cool at the time.
Yeah, I've been working around that for now by uninstalling notepad. Which actually uninstalls the store app, which in turn exposes the actual notepad executable that ships with Windows. Really confusing, and will probably break in some future version of Windows.
I don't understand why they didn't just stuff all the AI things and new features in Write, where it belongs…
reply