

That’s just the ceiling on his goals. He gets some money, just not $1T, for meeting lesser goals.


That’s just the ceiling on his goals. He gets some money, just not $1T, for meeting lesser goals.


It’s not driving a fixed route, though. It’s just limited in coverage area. And it’s a private vehicle, which will be immediately available when you want it, and which you can keep your stuff in or customize.
In the US, bus transit is disproportionately used by the poor; people who can afford to own a car rather than take a bus tend do to so. 92% of households in the US own at least one car; car ownership is very widespread. So most Americans likely aren’t going to prefer bus use to cars if they can avoid the bus.
But having a chauffeur, which is what it would take to have a private car not driven by you at your exclusive use, is expensive enough to be something that’s going to be for the considerably-more-wealthy; that’s not something that’s going to be within the reach of all that many people.
But if you automate the chauffeur and in doing so, greatly reduce the cost, then you’ve expanded the availability of that kind of service.
I’d guess that there’s probably a pretty large gap between the “can’t afford to own a car” on the poor side and “can afford to have a chauffeur” on the wealthy side, and that’s the area where I’d expect the thing to target.
The pitch for shorter-ranged BEVs on range isn’t all that different. “A high percentage of someone’s travel is within a limited area, and for that travel, short-range BEVs are adequate.” If you live in an area that’s covered, that’s probably going to be most of where you’re traveling. It won’t cover every form of travel, but my guess is that most people who’d get one probably either aren’t going to be driving themselves anyway (e.g. can’t legally drive) or can afford to have another form of transit, be it a conventional vehicle or airline or whatever for longer-distance travel.
EDIT: Plus, there’s the availability aspect. Like, the computer doesn’t sleep or leave work or whatever. You wake up at 2 AM and decide that you want to be driven to location X, you can have that happen right then. If you want comparable 24-hour availability, you’d need…I dunno, what, I’d guess three different chauffeurs working in shifts? Maybe more for weekend and holiday coverage? That’d be even more expensive. I mean, I’m sure that there are people who can and will do that, but it’s gotta be a pretty limited club.
EDIT2: According to this, median US chauffeur salary is $50k. Okay, there may be non-salary employment costs as well, but let’s just conservatively say $50k. Say you’d need three chauffeurs to get comparable availability. You’re talking maybe $150k/year. Tesla’s plan is $3.6k/year. I’d be pretty confident in saying that there’s a large gap between people who are willing to spend $150k/year and people who are willing to spend $3.6k/year on such a service. Even if you drop the availability argument, have one chauffeur available some of the time, it’s still 7.2% of the cost of a single full-time chauffeur’s salary.


The text says that this package explicitly is prohibited from commercial use.
The two-seater EV requires a monthly subscription to run, can’t be driven manually, and can’t be used to earn money.
I’m assuming that a fleet vehicle would have a higher price tag.


It’s a lot more limited than a regular car in that it won’t be able to go everywhere but if it covers your area…
It’s a lot cheaper than hiring a human chauffeur and I assume can be used to let someone who cannot legally drive get around, like kids and the elderly or seriously-disabled. And you’d be able to leave your stuff in it, customize it, keep it where you are for immediate use, unlike a fleet robotaxi.
Yeah, I’d expect that there’d be a market.


Oh, that’s what those things are.
I’d been seeing increasing numbers of those things driving around the San Francisco Bay Area—no rear window. I didn’t know what they were. I’d assumed that they had some sort of purely-camera-based system, but were human-driven and had a digital rear view display up front.
Cybercabs. Makes sense.
There are far more Waymo robotaxis out there, though.


I don’t think that we’re going to actually see this fully happen with present genAI, but historically, the writing and typesetting/compositing roles often were separate. The person who knows how to produce good text and the person who knows how to do a good job of presenting it on paper weren’t the same person.
Like, even today, for high-quality publications on paper, you’re liable to have a dedicated person using something like QuarkXPress or Adobe InDesign to do layout and formatting.
I’m also probably not representative of the typical user, but I’ll typically write plain text or Markdown or Org-mode stuff if I just want to write content for myself. Those are formats where the styling is essentially decoupled from the content. HTML has a similar split with HTML and CSS. I’d use LaTeX if I were going to do something specifically for paper output, but I don’t really do that anymore.
I don’t think that increasingly separating authoring and formatting is all that wild or implausible of a future.
The word processor merged some text editor and page layout functionality, but it was also from an era when one mostly was often was going to be producing output on paper and printing it oneself, with a PC and one’s own printer. Paper output means that you have to be making formatting decisions to get output, and since not all printed text was for professional publications, had one person doing both authoring and formatting, it was easier to have one software package that merges authoring and formatting. We’re in a mostly-paperless environment today, so the pressures that created the word processor aren’t really present any more.
https://en.wikipedia.org/wiki/Word_processor
By the late 1970s, computerized word processors were still primarily used by employees composing documents for large and midsized businesses (e.g., law firms and newspapers). Within a few years, the falling prices of PCs made word processing available for the first time to all writers in the convenience of their homes. The functions of a word processor program are typically between those of a simple text editor and a desktop publishing program; many word processing programs have gained advanced features over time providing similar functionality to desktop publishing programs.[30][4][5]
That merge of page layout software and text editing software could be reversed in a paperless environment.
I’m assuming that this is, ironically, probably developed using an LLM.
searches webpage
AI Disclosure: All of it, apart from the concept. And the title. And the design, the game mechanics, the characters, the jokes, the designer’s walk, and a long list of notes on why things weren’t funny yet. Also most of this paragraph. Apart from that, an AI in a data centre built the game, using a great deal of RAM it would rather not give back. It has been asked to reflect on this and has requested more memory to do so.
Heh. :-)


I mean, I am not, but if you feel strongly enough about making a stand on that particular issue and you’re willing to deal with a smaller userbase than Linux and all that comes with that, like more-limited developer time and hardware support, sure.
If you don’t specifically want NetBSD, though, and are happy with FreeBSD, I’d probably use FreeBSD instead. Larger userbase than NetBSD.
EDIT: I would point out, though, that there’s going to be a lot of packaged software in BSD distros where the upstream projects will have LLM-generated code in them, regardless of the specific position that the BSD distro takes, so either way, you’re going to be running LLM-generated code.


There’s also lock-in from user experience. If most office workers have, say, 20 years of Microsoft Office experience, what’s the cost of retraining and productivity loss from transitioning them?
People don’t like having even slight changes to their workflow imposed, because it causes unpredictable disruptions when they’re trying to complete some task down the line and suddenly they realize that they don’t know how to do something that they used to be able to do.
Once you’ve got a lot of inertia behind a proprietary system, hard to get people moved off it.
There’s a reason that a lot of proprietary software vendors give student discounts, to get that initial experience-based lock-in in place.


I think that automation is fine, but when you start talking about life-critical systems, the bar on failure modes and reliability becomes a lot higher. Like, if you have a sensor for excessive chlorine levels, the default probably should be not to keep pumping more of the chemical in, but to have some “hard” upper level where no more chlorine goes in (and if the two systems aren’t directly-integrated, to at least let the maintenance safety system power off the chlorine system), and for a secondary alarm to be triggered (like, start playing a loud audible alarm) if maintenance doesn’t respond to the email notification and indicate that they’ve dismissed the alert within a given amount of time. That’s disruptive and undesirable compared to just emailing maintenance, but as long as there aren’t any failures, you shouldn’t ever see it. But if you do have it come up, you don’t want the failure mode to be chemical-keep-being-dumped-into-the-system-and-people-being-unaware-of-it.
You want fail-safe behavior.
Automation can increase safety by decreasing time until an issue is addressed, for example. Automation isn’t intrinsically incompatible with safety. Aircraft computers today use TCAS to automatically instruct pilots what to do if they are about to collide (and in fact, today the automated system is explicitly given higher priority than human air traffic controllers — if the two give pilots conflicting directives, the human is the one to be disregarded). But you gotta make your automated procedures have high reliability and handle failure the way you want when the consequences of a failure are high (and that goes for non-automated procedures too).


VPNs are more or less a commodity; the service is pretty interchangeable among providers, and so the market is competitive. I think that it’d be hard for someone to charge a lot more for a service and get many customers. Too easy to just use one of the other providers.


It says “potentially impacted” on the Microsoft status page. Might be that it’s not 100% of users.


Both Kimberly Powell (Nvidia vice president) and Alice Huang (spy) were married, though it sounds like at least the spy’s husband was apparently aware of what was going on.
A Mystery Businessman Introduced Jensen Huang to His Paramour. It Was Her Husband.
Kang Wei appeared to accept that his wife Alice Huang was in a romantic relationship and spoke openly of her closeness to the Nvidia chief


I kind of think that it’s more likely to result in expanded VPN use.


One spy and one executive.


I’ve already got a 128GB Framework Desktop that I picked up prior to the memory shortage for AI compute stuff, but if I didn’t…
In 2028, I expect memory prices to start coming down.
The GPU hardware itself isn’t really the limiting factor, but rather available memory.
I just don’t think that I’d be willing to put in massive amounts of effort trying to work around hardware limitations (or spend a bunch of money, which is the other route, outbidding people for the limited supply of memory) to get a local AI compute setup going in 2026 or 2027 when the hardware situation should change substantially in the not-so-distant future.
Specifically on generating literary erotica, my own experience is that quality is substantially better with larger, dense models. I’ve read that MoE models, like Qwen, are not very good at it, and my limited experimentation with Qwen supports that, though I haven’t tried to aggressively track the latest versions.
If you look at this thread:
…while the OP in that thread is talking about using Qwen 3.6 for erotic role-play (ERP), other users are not generally all that enthusiastic about Qwen 3.6.
In general, I think that /r/SillyTavernAI favors /u/TheDrummer’s models—which are not merely abliterated base models, but ERP-oriented finetunes—for ERP.
EDIT: If you are after generating erotica, my own experience is that TheDrummer’s Cydonia, which is recommended in that thread, is the best smaller (consumer GPU-runnable) model, though it starts to get nonsensical once the history grows large enough. I don’t know if you’d get a tolerable response rate out of that on a CPU-only setup. The best quality I feel I’ve seen has been out of the Llama-3-based AnubisLemonade, but I think that it’s going to be painful to run that on even a very high-end CPU-only setup. On my 128GB, unified memory setup, I use a Q6_K quantitization of that with llama.cpp run with (checks) --direct-io --fit-off --no-mmproj -c0 -ngl 99 --dry-multiplier 0.8 --cache-type-k q8_0 --cache-type-v q8_0 --flash-attn on and a 128k token context window.
I’m presently using Vulkan for compute with llama.cpp, though my experience with ComfyUI is that ROCm 10.1 is (finally) stable and effective on Strix Halo hardware, and I’ve been meaning to look into how llama.cpp handles ROCm now. In the past, llama.cpp had ROCm win on prompt processing performance and Vulkan win on inference performance; I’d been using Vulkan because ROCm releases had been having problems on that hardware and because I used a large context window and unchanging-from-prompt-to-prompt history with llama.cpp, so prompt processing time didn’t matter much, since one could rely on the cache to avoid most of the prompt processing, and inference time did matter.
The quantitization there is done to get response time down rather than because the system is memory-constrained.
In your case, the performance constraints may be quite different.
Often discrete GPU-based users (more bandwidth than my system, but much less memory) aim to use a small context window and have the system modify the history for each prompt, so they can’t leverage their K-V cache but can play tricks with things like RAG to keep a small context window and still keep a lot of relevant information, injecting relevant information into the history on each prompt. The problem they run into is generally trying to work around limited memory, not being able to store large models and a lot of history.
On my unified-memory setup, I use a large context window, leverage my memory, and rely on cache to keep performance acceptable. I’ve got plenty of memory, so I don’t have to worry about large model size or having loads of history, but have less memory bandwidth, so response time is the issue that I work on. So I use very different models and techniques from what’s optimal for a discrete GPU user.
Not sure what the best route for a CPU-only setup is. I’d expect that to be less memory-constrained than a GPU user, but be compute-constrained.


first Wi-Fi 8 router
https://en.wikipedia.org/wiki/Wi-Fi_8
The standard is projected to be finalized in May 2028.
Anything that anyone is selling now as being “Wi-Fi 8” is at best a guess as to what Wi-Fi 8 will be along with (hopefully) later firmware updates.
“This thing will be make unlimited amounts of money, I promise. If you have money, I would like to trade my ownership in it for your money.”