Linked by Hadrien Grasland on Fri 30th Dec 2011 08:24 UTC
Hardware, Embedded Systems In the world of alternative OS development, portability across multiple architectures is a challenging goal. Sometimes, it may be intrinsically hard to come up with hardware abstractions that work well everywhere, but many times the core problem is one of missing information. Here, I aim at learning more about the way non-x86 architectures deal with CPU IO ports, and in particular how they prevent user-mode software from accessing them.
Permalink for comment 501760
To read all comments associated with this story, please click here.
by daddio on Sat 31st Dec 2011 04:34 UTC in reply to "RE[2]: IO on other platforms"
Member since:

Why would anyone have a problem with the word "managed" as used to describe dotnet?

Because there was nothing new there that didn't already exist in other execution environments. They were not considered "managed".

It was PURE marketing.

It wasn't manged any more than java, or heck, interpretted languages like bash or BASIC, which run under the supervision of another process.

Reply Parent Score: 1