Hacker Newsnew | past | comments | ask | show | jobs | submit | DustinBrett's commentslogin

OS in JS, ok I am interested now...

I can eat half a pizza pretty easily.


Comments full of EDS. Everyone is a rocket scientist in here also.

Enemy of the State was accurate in 1998


It's sad how few competitors have come out in a decade.


How do you steal open source code? It's open.


You violate the license (such as GPL)


Copyright licenses are not one word. They are written with intent, and usually at minimum that intent is to credit the original author.


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.


At some point AI might get good enough to write whatever is missing from that thing. Seems like they have the ability to wait it out.


Maybe, maybe not, but one thing is for certain: you can't seem to escape conversation about AI regardless which post you open on HN!


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.


"Assuming a ReactOS developer used Microsoft / Github Copilot to work on this codebase"

No need to assume. It's a certainty: https://github.com/reactos/reactos/pull/8516

"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.


> that would be next-level irony

More like end of Copilot.


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: