Technology

59123 readers

4466 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

162

Windows NT vs. Unix: A design comparison (blogsystem5.substack.com)

submitted 1 month ago by [email protected] to c/[email protected]

42 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 23 points 1 month ago (2 children)

Moving down the stack, Unix systems have never been big on supporting arbitrary drivers: remember that Unix systems were typically coupled to specific machines and vendors. NT, on the other hand, intended to be an OS for “any” machine and was sold by a software company, so supporting drivers written by others was critical. As a result, NT came with the Network Driver Interface Specification (NDIS), an abstraction to support network card drivers with ease. To this day, manufacturer-supplied drivers are just not a thing on Linux, which leads to interesting contraptions like the ndiswrapper, a very popular shim in the early 2000s to be able to reuse Windows drivers for WiFi cards on Linux.

[–] [email protected] 19 points 1 month ago (1 children)

Nvidia:

[–] [email protected] 2 points 1 month ago

It's a wonder that someone hasn't implemented a similar wrapper for WDDM. I suppose they'd rather force the vendors to play nicely.

[–] [email protected] 1 points 1 month ago

Also ndisgen under FreeBSD. MS could have been nice for a difference and not broken compatibility.