I think it's not ready yet but I agree that eventually it will be. The 40th anniversary of ReactOS might have some substantial features. This is the decade of ReactOS!
The new graphics driver stack they're touting (capable of running unmodified modern windows display drivers) along with support for x86_64 landing may result in increased interest in the project. They've already made a lot of progress with almost no resources as is. It's truly an impressive project.
ReactOS requires all contributors to affirm that legally they have not used or seen any leaked Windows source code. This is to avoid any hints of copyright violation. While AI may be capable of writing a new driver or fixing bugs, a developer using AI can’t affirm that the model hasn’t seen/trained on any leaked source code. So AI submissions would very likely be denied.
Oh? Because Copilot might have trained on code it shouldn't have?
Assuming a ReactOS developer used Microsoft / Github Copilot to work on this codebase, then if Microsoft attempts to sue (themselves?) over their own Copilot tool injecting their own copyrighted code into a user's codebase, then that would be next-level irony right there.
I would chip in my $100 to fund whatever side of that legal battle is necessary just so I could see that case be argued in court.
"if Microsoft attempts to sue (themselves?) over their own Copilot tool injecting their own copyrighted code into a user's codebase"
Such an attempt can't make sense, given that the model used by ReactOS is in Microsoft's control and thus Microsoft alone is the one responsible for the model's behavior. They won't sue, thus much is clear.
I've been having good results lately/finally with Opus 4.5 in Cursor. It still isn't one-shotting my entire task, but the 90% of the way it gets me is pretty close to what I wanted, which is better than in the past. I feel more confident in telling it to change things without it making it worse. I only use it at work so I can't share anything, but I can say I write less code by hand now that it's producing something acceptable.
For sysops stuff I have found it extremely useful, once it has MCP's into all relevant services, I use it as the first place I go to ask what is happening with something specific on the backend.
I made something like with a similar aesthetic a few years ago but themed after win95 (which seems to be hardly unique these days). But it had a secret gimmick where aspects of it were implemented with in terms of itself (mostly, file icons could be edited within app and you could see them update on the desktop).
I had grand plans for it but they never eventuated.
I got to 3, then opened one of his YouTube videos in the "bottom" browser. Nothing seemed to happen then the audio started playing and everything slowed to a crawl. After closing the tab the audio kept playing and my entire PC became unusable until I rebooted. I'm not even mad, I'm impressed!
We being who? What is your evidence it's better? The fact all the cars stopped moving when the power went out? The fact they cost WayMore? Show the evidence for your claims. And they have remote operators as proven by the power outage.
Apologies, I was unclear with the "i.e." bit I assume, to spell it out: I think after struggling with it over years its time to call it because Waymo has a scaled paid service, no drivers, multiple cities, for 1 year+.
It’s because you spam this thread so much with such aggressive language that it honestly is scary to deal with you.
You’re smart Darren, and so are other people, you should assume I knew the cars have remote backup operators. Again, you’re smart, you also know why that doesn’t mitigate having a scaled robotaxi service vs. nothing
I doubt you’ll chill out but here’s a little behind the scenes peek for you that also directly address what you’re saying: a big turning point for me was getting a job at Google and realizing Elon was talking big game but there’s 100,000 things you gotta do to run a robot taxi service and Tesla was doing none of them. The epiphany came when I saw the windshield wipers for cameras and lidar.
You might note even a platonically ideal robotaxi service would always have capacity for remote operation.
I can't tell if this was suppose to be for me, I am not Darren. The reply was on my thread...
My replies are at the same level as that which I respond to, never aggressive IMO.
And if you "knew" something about the relevant topic and leave it out, that in itself is part of the dishonesty.
So once you got a job at Google then you felt Waymo was better, hmmm.
Tesla has a robot taxi service that in some cases has nobody in the car. Also everyone that owns a Tesla has experienced FSD in which it goes from A to B without being touched which is the same as it driving by itself. A person just went cross country and back with this. So to say Tesla is doing none of the 100,000 things you think are required, I think that says more about what someone at Google thinks is needed vs what is happening on the ground.
I am not against remote operation in some cases, but those suggesting Waymo has solved this need to admit that it relies heavily on them for basic decision, like what to do when the power goes out at intersections.
This is such a weird take when Elon Musk is still letting his Optimus robots be teleoperated for basically every live demo. If you're lenient with him, it's completely unreasonable to be strict with Waymo, which works autonomously the vast majority of time.
Optimus is early days, and my take isn't against remote operators but pointing out that Waymo relies on them much more than Tesla. You can go from 1 side of the country to the other without ever touching the wheel, something Waymo could not do. And the SF power outage incident showed us that it is actually only autonomous until it isn't, then you have a bunch of cars that can't move and won't and do not.
What's lacking here? Waymos are driving driverless in multiple cities and Teslas are not. Robotaxis have a person with hands on button at at times for emergencies.
They might get better but how is that not evidence enough that currently Robotaxis are behind Waymos in self driving capabilities?
This was your chance to provide the evidence to your claims. It is conjecture what you have provided. Waymo requires the remote operator make decisions often, such as at uncontrolled intersections when the lights go out, as shown in SF. Just because you don't see the strings doesn't mean they aren't there.
reply