Windows vs UNIX is like RISC vs CISC on cpus: each one has its flaws and
advantages. The unix api philosophy is to keep the functions as simple as
possible, and achieve the same tasks through serquences of configuration
calls, rather than big monolithic APIs that have the settings all specified
explicitly.
I'm not going to argue which one is best, as my personal preference falls
in between, if only slightly closer to the Windows way. The Windows API is
often overengineered, while the unix way feels overly simplistic.
In fact, the comparison between Windows and unix here is pointless: this
project is reimplementing Windows, not unix. Anyone who truly thinks
ReactOS won't be used becuase they already have Linux, probably wouldn't
care about the project and so wouldn't be writing to our mailing list. I
believe Riccardo referred to people developing apps for ReactOS/NT5, when
they can write them for NT6 instead.
On 22 May 2016 at 13:41, Love Nystrom <love.nystrom(a)gmail.com> wrote:
On 2016-05-18 02.10, Riccardo Paolo Bestetti <riccardo.kyogre(a)live.it>
wrote:
It's not like developers are gonna pick up
again an old (and, honestly,
bad!) architecture just because it is made free, when *here and now* we
already have a better alternative.
Bad architecture ? Compared to Linux ? I refute that on the strongest.
F.ex: Linux lacks, even to this day, a unified graphics API like GDI
(X-Windows notwithstanding), and window manager.
Instead they have a plethora of disparate kludges and hacks on top of
X-Windows, all more or less cumbersome to use.
The API flora of the Windows architecture should, by rights, make Linux
programmers green with envy ;-)
(Why do you think the WinE project was born in the first place?)
Best Regards
// Neo
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev