Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ReactOS

reactos.org

Post reply on HN
Print view View original

121–130 of 141 posts

Re: ReactOS

#121

Post by rnd1 »

rnd0 wrote: post #119
russelg wrote: post #116

Earlier quoted context omitted.

https://github.com/reactos/reactos/blob/59b78b4756da02e275e3... Is just one example.

Odd, here's the commit history for that file: https://github.com/reactos/reactos/commits/master/ntoskrnl/k... What I'm wondering is if you just chanced upon a submission that wasn't actually accepted into the tree at any point? Perhaps because it literally says: >/* This part was copied from Windows source / > / We should obfuscate this somehow? */ And looks sketchy as hell? I'm not part of their project (just a fan)…

Do you expect someone to verify for you whether that is stolen source code?

Re: ReactOS

#122

Post by iainctduncan »

CyberDildonics wrote: post #14
iainctduncan wrote: post #11

If they ever get to the point of enabling audio folks to run windows audio apps with a low-latency pre-emptible kernel, they'll get big adoption in that world. Right not it's ridiculous how crappy the options are for low latency given how fast our machines are.

Does anyone try to shift audio mixing to the GPU and use the audio output of HDMI? I don't know if modern GPUs can take buffers and move them to the audio buffer without going out and back in through PCIe but it seems plausible.

I'm not sure, but that's a different issue. The latency problem with everything except linux is we can't tell the OS to elevate our audio apps priority above the rest of the kernel, so operating system calls randomly happen and jump in front of the audio callback, hosing latency. I used to get 0.7ms latency on linux with the CPU at over 90%!!! I'm lucky to get 7ms on OSX with the CPU at 30-40%ms, sigh. It sucks so bad, it's like being allowed to use 1/4 of your computer power for real time audio. Even Windows 98 was better, you could tweak it pretty well. If you put your audio latency down to 2-3ms nowadays you can use very little of your CPU without under-runs. :-/

Re: ReactOS

#123

Post by mycall »

jeditobe wrote: post #70
Jaruzel wrote: post #19

I'm saddened a little bit to see stuff like theming has been built. I was hoping that ReactOS would stick with the Windows 2000 look and feel. I also think that with the limited resources they have, the project team would be better focusing on improving compatibility, over shiny desktop effects. That said... I firmly believe there is a place for ReactOS. Eventually, XP will fail to run on new hardware, and when that…

> Eventually, XP will fail to run on new hardware, and when that happens a lot of great software will die also. https://www.win-raid.com/t4035f45-Windows-XP-Bit-and-Server-... After i have found this, i m not sure that xp will ever die

The questions have much different answers if you accept third-party software as part of the solution.

Re: ReactOS

#124

Post by [deleted] »

rnd1 wrote: post #121
rnd0 wrote: post #119

Earlier quoted context omitted.

Odd, here's the commit history for that file: https://github.com/reactos/reactos/commits/master/ntoskrnl/k... What I'm wondering is if you just chanced upon a submission that wasn't actually accepted into the tree at any point? Perhaps because it literally says: >/* This part was copied from Windows source / > / We should obfuscate this somehow? */ And looks sketchy as hell? I'm not part of their project (just a fan)…

Do you expect someone to verify for you whether that is stolen source code?

[deleted]

Re: ReactOS

#125

Post by rnd1 »

[deleted] wrote: post #124
rnd1 wrote: post #121

Earlier quoted context omitted.

Do you expect someone to verify for you whether that is stolen source code?

[deleted]

Why would anyone provide that sort of proof on the internet? ReactOS doesn't accept submissions from people who have seen Windows source and Microsoft will revoke source code access.

Re: ReactOS

#126

Post by [deleted] »

rnd1 wrote: post #125
[deleted] wrote: post #124

Earlier quoted context omitted.

[deleted]

Why would anyone provide that sort of proof on the internet? ReactOS doesn't accept submissions from people who have seen Windows source and Microsoft will revoke source code access.

[deleted]

Re: ReactOS

#127

Post by dang »

rnd1 wrote: post #121
rnd0 wrote: post #119

Earlier quoted context omitted.

Odd, here's the commit history for that file: https://github.com/reactos/reactos/commits/master/ntoskrnl/k... What I'm wondering is if you just chanced upon a submission that wasn't actually accepted into the tree at any point? Perhaps because it literally says: >/* This part was copied from Windows source / > / We should obfuscate this somehow? */ And looks sketchy as hell? I'm not part of their project (just a fan)…

Do you expect someone to verify for you whether that is stolen source code?

We've banned this account - it's not ok to mimic someone else's username like that, but it's especially not ok to add sockpuppet accounts to a thread you're already in. Doing that will get your main account banned as well, so please don't do that again.

Re: ReactOS

#128

Post by zerocrates »

ocdtrekkie wrote: post #34
zerocrates wrote: post #26

Earlier quoted context omitted.

Do you really think there'd still be a place for mobile Java now in the absence of Android? Seems pretty unlikely to me.

The state of the market today isn't the point: It obliterated mobile Java when Google infringed. Your question actually reinforces Oracle's claim that they were irreparably harmed by Google's infringement; there's no way to undo what has been done, and substantial damage compensation is necessary. https://en.wikipedia.org/wiki/Fair_use#U.S._fair_use_factors is a really good read for the basic understanding of how fai…

I don't mean "if you take away Android today would Java succeed on mobile?", I mean "if you retrospectively imagine Android never existed at all (or used a different language), how does Java do?"

My position is that it doesn't really change things all that much, with losses by Android probably mostly picked up by Apple or Symbian or webOS or Windows Phone but the trajectory to smartphones and away from J2ME stuff largely the same. The sense of how much Android actually "mattered" in this sense goes right to the "effect on the market" prong.

As for the broader case, both the copyrightability and fair use claims have been presented to the Supreme Court here. The temptation from the outside looking in is to think/hope/dread that the court will just resolve these questions once and for all, but they often prefer to resolve cases on narrower grounds, where available. Google spent a lot of time arguing for, and would be perfectly fine with, a simple remand based on the Federal Circuit's standard of review of the jury's fair use verdict.

Re: ReactOS

#129

Post by WesolyKubeczek »

CyberDildonics wrote: post #14
iainctduncan wrote: post #11

If they ever get to the point of enabling audio folks to run windows audio apps with a low-latency pre-emptible kernel, they'll get big adoption in that world. Right not it's ridiculous how crappy the options are for low latency given how fast our machines are.

Does anyone try to shift audio mixing to the GPU and use the audio output of HDMI? I don't know if modern GPUs can take buffers and move them to the audio buffer without going out and back in through PCIe but it seems plausible.

Doesn't work like this. HDMI is a separate device; also, in a thread somewhere Paul Davis of Ardour fame explains how exactly infeasible it is. (And you won't be able to do "real time" on a GPU anyway if it's not graphics.)

There's also more to audio than mixing (simple mixing was done on G3/G4, come on), when you take all the effects and filters, so to offload that reasonably you'd need an audio card with, say, an FPGA.

Re: ReactOS

#130

Post by jeditobe »

marttt wrote: post #117
yaseer wrote: post #7

Does anybody use ReactOS regularly? What's your experience with it? Very curious to see how far it's come for practical usage.

My goal is to get Avid Pro Tools 7 working on bare metal ROS. Partially successful attempts thus far: install is going smoothly, but the software doesn't launch. I get the nostalgic Blue Screen of Death and usually end up re-installing the entire OS. I assume it is a driver issue since PT of that era (2007-ish) requires a dedicated audio interface (the Mbox). But I need PT a few times a year, so I'll keep trying. I c…

Unfortunately, I was not able to find any bug-report related to the Avid Pro Tools 7 in the bug-tracker https://jira.reactos.org/

Filling a bug-report is the important first step to have your software working in ReactOS

Post reply on HN