3 ms·
Having followed this project for around a decade, it amazes how slow it is being developed compared to Haiku. On the surface it looks like windows 2000, but as
by jamesu 15y ago
Having followed this project for around a decade, it amazes how slow it is being developed compared to Haiku.
On the surface it looks like windows 2000, but as soon as you try and do anything useful, you bump into problems. Firefox hangs the system when loading. Fonts don't always draw correctly. LOTS of things are missing. Quite often i press a button on a dialog, and it does nothing - why was is it even enabled if it doesn't work?
Still a long way to go!
- diminish 15y agoI have been watching this project for 7 years already; why doesn't ReactOS simply target running IE7, 8, 9? if they could do that millions of people would use it in VMs.
- cookiecaper 15y agoUnfortunately WINE and WINE derivatives are not in a state where they can be trusted to render pages as IE would render pages. WINE changes very quickly. The drawing code is no exception; they've spent the last year or so integrating a DIB engine, which will be among the flagship features of 1.4. WINE is not likely to reflect a pixel-perfect representation of what your IE users will see and that's the simple fact. I've been bitten before by trusting the output of an IE in WINE. For testing IE, there is still no substitute for the official Windows platform. I don't think there will ever really be one, but it may be a decent distant-future goal for WINE: consistent pixel-perfect rendering in every IE version.
- bwarp 15y agoI think that's because it's an order of magnitude more complicated than Haiku. BeOS was fairly new and well designed when they started. Windows however has nearly 25 years of evolution to reproduce. ReactOS is remarkably functional considering though!