Comment Believe me, I love it as much as anybody, but. . . (Score -1, Insightful) 190
We get yet another conference in without dealing with some of the fundamental flaws in the Wine implementation, that if they continue to go unaddressed will get locked into core code and we'll end up with as much of a dog as the system it's trying to replace. I'm speaking of (at least - this is the short list)
-- Thread resolution and collection.
-- Incredibly sloppy video management and screen management code.
-- Conflicts with the kernel in the management of I/O and wait states for unsupported hardware.
-- TCP/IP stack is circa 1993, even Microsquid could do a better job.
I applaud this ra-ra attitude, but unless we're willing to take an *unflinching* look at where we are, Wine is really going to stay as a novelty.
-- Thread resolution and collection.
-- Incredibly sloppy video management and screen management code.
-- Conflicts with the kernel in the management of I/O and wait states for unsupported hardware.
-- TCP/IP stack is circa 1993, even Microsquid could do a better job.
I applaud this ra-ra attitude, but unless we're willing to take an *unflinching* look at where we are, Wine is really going to stay as a novelty.
