81–90 of 141 posts
How would recent leak of Windows XP source code help these guys? Would they be able to use some of it for reverse engineering and then create their own solutions?
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…
Do we? Virtualization and emulation usually sort this out. 8- and 16-bit console games are a good example of this.
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…
> but we struggle to run 10 year old software Do we? Virtualization and emulation usually sort this out. 8- and 16-bit console games are a good example of this.
There are a great number of games that cannot be played by most 16-bit and 8-bit console emulators. The Famicon disk system, for instance, is a real struggle to get working right.
90s machines are dying off rapidly, and hardware is becoming very very scarce. Much DOS software, for instance, requires very specific hardware timing and behaviors that is either not known about or still emulated wrongly. Worse, some emulations simply don't exist or are very difficult to get working (see also 3DFX Voodoo3 8-bit paletted textures).
2010 machines are next on the chopping block. Though tose systems may be easier to deal with hardware wise, emulation will still be a challenge.
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…
It's really saddening if you've been following the project for years. They had some good progress back when the Russian government got interested in ReactOS, but lately they seem to just be doing webdev stuff not directly related to improving ReactOS. To the ReactOS devs: what's the deal with the last couple years of GSOC projects? Why is there little to no work going on to improve compatibilty?
There are a qute a lot of pretty ideas https://reactos.org/wiki/Google_Summer_of_Code_2020_Ideas
The problem is in lack of students ^)
Earlier quoted context omitted.
> else we'll endlessly repeat ourselves rewriting the same programs over and over again Doing this is ok. We are also rewriting the same books all over again. Knowledge is forgotten and reinvented and rediscovered. You see this in computer science and programming all the time, but also in other fields. Rather than the programs themselves, preserving the concepts and learnings is much more important. Don’t get me wron…
Knowledge being lost and reinvented is a bug, not a feature. Some lessons have been paid-for in blood (like the Therac 25, if you're looking at software development). There is value in understanding how things work and what knowledge came from specific lessons, but starting over again simply invites making the same mistakes all over. I wish we could aspire to be better than that.
It has the same problems: the historical context is imperfect and very tedious to understand (for those who even try). Reinventing the wheel is always easier, cognitively (perhaps while being vaguely cognizant of how there was a Roman Republic that fell to dictatorship that then fractured into hundreds of apocalyptic Christian fiefdoms and how there was an incident with this thing called Therac-25 [and maybe crystallizing that cognizance in proper government standards for medical software]).
Also, since the bottleneck is brain bandwidth, it's not helpful that old code is written in old languages which were formulated in a time where the most salient bottleneck was memory/processing speed.
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…
How well does this actually work ? Wouldn't Ubuntu+ Wine be a better combo for most ?
The goal of ReactOS is the binary compatibility not just with application programs but also with Windows device drivers.
It's perfectly fine if this is effectively ' we did it to prove we could ' thing. I've heard of React OS before and it's been in development for such a long time.
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…
> else we'll endlessly repeat ourselves rewriting the same programs over and over again Doing this is ok. We are also rewriting the same books all over again. Knowledge is forgotten and reinvented and rediscovered. You see this in computer science and programming all the time, but also in other fields. Rather than the programs themselves, preserving the concepts and learnings is much more important. Don’t get me wron…
Earlier quoted context omitted.
Knowledge being lost and reinvented is a bug, not a feature. Some lessons have been paid-for in blood (like the Therac 25, if you're looking at software development). There is value in understanding how things work and what knowledge came from specific lessons, but starting over again simply invites making the same mistakes all over. I wish we could aspire to be better than that.
Isn't this kind of like wishing that we could apply the lessons of the fallen Roman Republic to present-day America? It has the same problems: the historical context is imperfect and very tedious to understand (for those who even try). Reinventing the wheel is always easier, cognitively (perhaps while being vaguely cognizant of how there was a Roman Republic that fell to dictatorship that then fractured into hundreds…