Sure. I would expect that each country would want to protect themselves from other countries.

>"This is about whether a hostile third party can affect a vehicle remotely because of manufacturer incompetence."

Oh, well, both are important :)

I have often wondered if it is reasonable to just find the antenna(s) and put a keyswitch across it/them, so you have absolute control over when/if they can be accessed remotely at all.

The above was already quite long, but allow me to add a bit :-)

I spent a few minutes looking for the state of the art in C++/Rust interop for contexts that don't have a nice intermediary like binder. It turns out that the situation isn't as bad as I thought. The CXX project enables automatic generation of bi-directional definitions between Rust and C++ and is being used at scale by the Chromium project and that seems to be going pretty well.

There's also a Google-funded Rust Foundation project to define a better solution, though I don't see what, if anything, has happened since it was announced last year. Hopefully that's because there's a small group working too hard to waste a lot of time talking about it.

The reason I went to look is that my new team (I left Google a couple of months ago) might need such a thing. I've been asked to define an API that would benefit from being implemented in Rust and usable from C++ and Rust.

>"I will pause judgment until they conduct the same test on domestically made buses."

Most new vehicles have all kinds of spyware and remote control crap (mine certainly does). But, presumably, domestic ones are nowhere near as much of a threat than a foreign, potentially hostile nation-state.

Telling people that vaccines are bad, ensuring that any parent who wishes to refuse to vaccinate their children is fully supported in that decision, and working to make vaccines harder to get, more expensive and more painful (RFK Jr. wants to separate the MMR vaccine into three shots, each of which will still require three injections, so kids will have to get 9 shots to be fully vaccinated instead of three).

This is similar to their plan to fight inflation by imposing tariffs and forcing the Fed to lower interest rates in spite of rising inflation (note that this last part hasn't really happened yet -- the interest rate cuts have been measured, cautious and justified by economic conditions -- but Trump is working on it). Though to be fully fair, by making the tariffs arbitrary and capricious so that business leaders are completely unable to plan, Trump is also causing a contraction in US economic activity that might eventually generate significant unemployment, which actually does reduce inflation. I see no corresponding "silver lining" in the mumps plan, though.

And, ultimately, slavery was a far less efficient and effective economic system. One might think that keeping a big chunk of the populace poor is efficient, since you're not "wasting" a lot of production on providing them with unnecessary goods and services, but it's really not, at least not since the industrial revolution. I think the core reason that it's so inefficient is the same reason that Marxist communism is inefficient: From an economic perspective, both systems value the masses only for their physical labor, and fail to cultivate and take advantage of their brains, which also actually tends to reduce their labor output. Harnessing the distributed ingenuity of your workforce requires giving your workforce some reason to exercise ingenuity and some way to benefit from doing so.

It's going to be interesting (or maybe terrifying, or maybe just sad) to see what happens when we fully automate ingenuity, too, which will mean that the system no longer depends on or benefits from distributed ingenuity because the machines are smarter and think faster, just as the machines are already stronger and indefatigable.

I don't think vibe coding is going to last long as a thing, because it's just a sort of intermediate step to telling the AI to do what you want and having it do that. Right now, people are telling the LLM to write code to accomplish a thing and then running the code to see how it works, then telling the LLM to refine it, but that's a lot of unnecessary extra steps. I'm sure that in the not-too-distant future people will just tell the LLM what they want to do, which may require creating a custom user interface to make user interaction convenient, and may require creating databases or performing network queries or whatever, and the LLM will understand what they want, and do it.

In that future, it's possible that the LLM may generate code to implement the requested functionality, but if it does so that will be a compute-saving shortcut, essentially a way to cache the LLM's work and be able to repeat it with less effort. There won't be any need to show any of the code to the user, or even tell the user that the LLM chose to generate some code.

As an aside, the whole notion of leaning "prompt engineering" is another intermediate step that will die. The whole point of natural language-capable AI is that it will be able to understand what humans want when we express ourselves as we would to other humans. As the LLMs get more capable, it will become less necessary to treat them as something different from an entity that is fully capable of understanding and acting on human communication.

One of the things Android did very right with the Rust transition was to set up a small team of people who were entirely focused on Rust support. It wasn't a large team, only 2-6 people (it varied over time) out of approximately 1500 engineers. Having that core team who either were or became deep Rust language and toolchain experts was critical to smoothing the path for everyone else. It provided a group that had the knowledge and bandwidth to solve the problems that inevitably came up, as well as to offer advice and code review support to the early adopters.

That group no longer provides code reviews and design advice because Rust knowledge is now widespread enough that teams have their own, homegrown, Rust experts (not people designated as Rust experts, just engineers who became enthusiastic and dived deep), but the group still exists to resolve complex technical problems with language integration and to work on improving tooling and performance.

I think any shop adopting Rust (or any new language or complex tool) needs to have some people who become deeply expert in it and are allowed the time and freedom to support others who are picking it up.

So does Android. Google has been a primarily-C++ shop since its inception and although I'm not sure if Android had a lot of C++ in it when Google bought Android in 2005, it definitely became a C++-based system as soon as that happened.

The highly-segmented architecture of Android really helped facilitate the transition. Most of Android is structured as a web of collaborating services that communicate through a common language-independent [*] IPC mechanism (binder). Implementing Rust binder IDL generation and support libraries was a moderately big job, but once that was done it was easy to begin writing new system components (or replacing existing system components) in pure Rust, generally without any unsafe blocks at all.

If your code runs as a monolithic process, or has a lot of different IPC mechanisms, or uses a lot of existing libraries, it will be a lot harder, and the benefits will come slower. You'll have to wrap a lot of C interfaces in Rust -- and they will have to be C, not C++, since there isn't a good way for Rust to interoperate directly with C++. People are working on that, but it's a very hard problem and at present the best option is to layer a C interface on top of your C++ code, then wrap a Rust interface around the C interface. Yuck. Or, in the alternative, insert some other language-agnostic boundary between them.

So in a lot of ways Android got lucky because of its modular architecture and single, language-agnostic IPC mechanism. OTOH, that wasn't really "luck", it was a lot of work, done for good reasons, one of which was cross-language compatibility, notably between Java and C++.

[*] Language independent-ish, maybe I should say. The binder IDL is definitively Java-based, but this maps fairly nicely onto OO languages that support common primitive types (int, char, enum), basic composite types (array, vector, class/struct, string (which is just a vector, but used enough to be worth treating as a first-class thing)) and Java-like methods (fixed argument list, single return value). Further, it's based on "old" Java, before Java acquired functional extensions, when doing things like passing method references as argument was uncommon, and therefore not supported. So it's moderately-expressive but avoids things that get weird and complicated. My one big complaint about it is that I wish it supported unsigned integer types. That's my biggest gripe with Java, too.

He'll be dead before any technology exists that can even remotely come close to bringing her back. It's unlikely she survived having died and then was frozen, let alone repair the cancer AND the damage from the cancer that was severe enough to kill her.

>"12345" topping their list while "123456" dominates among everyone else.

Not a SINGLE system I use, and I use a LOT of systems, would allow such a stupid password. Granted, there are also tons of systems that go extreme in the other direction with requiring FAR too complex (which is also incredibly stupid). And the stupidest of all is password aging.

A reasonable password, coupled with rate limiting and lockouts, is very secure. It will not be broken by brute force on the "outside" of properly-configured systems.

Shouldn't the ACLU and EFF be devoting their efforts to ending the Valley Transit Authority's comprehensive video surveillance of all its bus and light rail passengers first?

https://www.marchnetworks.com/...

https://www.youtube.com/watch?...

What's been going on with the VTA over the past twenty years makes the deployment of LPR cameras in San Jose look like a joke. An LPR system records license plates, but the VTA records comprehensive video and audio of every single passenger who rides on it. That includes where those passengers get on on off - exactly the sort of "tracking" that the ACLU and EFF condemn.

Exactly when did all those MTA passengers consent to give up their privacy? If privacy is sacrosanct for people driving on public roads, what about people on public transit?

>"I just had trouble looking at a comment on one of my posts yesterday because I can't get through the Cloudflare bot detector."

I had the same problem yesterday and this morning. I could not open any direct links to postings. Period.

Ironic because I recently posted on Slashdot about how dangerous it is that all these sites are handing over their accessibility to a single huge company like Cloudflare, and complaining that Slashdot was throwing bot checks against me all the time in the last few weeks (which it had never done before).

>"Ban the collection of these types of information about individuals beyond what is necessary for performing a service -and ban keeping any collected data longer than is necessary for performing the specific service. No database = no database searches."

+100.

My issue is that I don't believe they will abide by any data collection retention limitations, use limitations, or other limitations; regardless of the rules/law. Especially if the three-letter agencies have a tie-in, they will do whatever they want. The only real way to prevent abuse is to not have those in use at all.

I really think this is a losing battle. People will almost always give up liberty and privacy for safety and convenience.

>"I just bought a new Ford Maverick for my business. It came with built in cellular data hardware -not optional. They say it is for diagnostics, updates, maps, and wifi-hotspot. It comes with the 1st year of data connectivity included. They want me to pay for additional years (no thanks!)"

^^ This
I bought a new Ariya earlier this year. All the hardware is already there. 3 years of service included, then you have to pay. You can opt out of data collection, and if you do, you lose half the "connected" features.

When in the history of humanity has there not been a big problem coming? Or occurring, for that matter.