Linked by Andrew Hudson on Mon 20th Jun 2011 17:19 UTC
Thread beginning with comment 478039
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Looking Forward to Haiku
by Laurence on Wed 22nd Jun 2011 08:56
in reply to "RE[6]: Looking Forward to Haiku"
What a stunninly useless term then.
Ahh so you don't have a point to make other than to argue semantics?
You might as well mention Hitler now and finish the thread completely :p
I don't think I can continue responding to you further as you clearly haven't put much thought into what you are writing or don't share the terminology most people use to discuss these topics.
Is that why I've corrected you on a number of points and the only comeback you've had thus far is the usage of the term "modern" over "current"?
You might want to read into the benefits of a trusted code base and a provable kernel for operating system security.
I already understand those points thank you very much. Perhaps you want to get off your high horse and admit when you someone calls you on your other the top "knee-jerk" comments.
Nobody was disputing that micro-kernels have their benefits (there's pro's and con's for all sides of the argument), however the comments you made were biased beyond reason.
Edited 2011-06-22 09:05 UTC
RE[8]: Looking Forward to Haiku
by M.Onty on Fri 24th Jun 2011 00:37
in reply to "RE[7]: Looking Forward to Haiku"
You know what, I was enjoying reading your two quite well informed opinions on this ... Right up until the last three posts. Why the need to get so personal? You were debating, and could have continued to do so profitably without the "yeah, well, your mum codes like that" attacks. What is it about internet forums, eh?




Member since:
2009-12-07
Yes, that's a serious question. WTF is a "modern" kernel,
Anything current, clearly.
"
What a stunninly useless term then. Thanks for the clarification. I would simply use the term "current" from now on as it is more clear. Most people use "modern" as a descriptive term and it has connotations with respect to design and form. See ("modern aesthetics", "modern science").
It's something you made up.
Lol, so, how do we refer to anything before modern (whatever that is because current seems to change every couple of years? Also, what does current mean "currently on the market" or "currently developed" or ..?
Well, not exactly.
It's about modulising core components and then porting them outside of kernel space - the goal often being to eliminate kernel panics.
Um, that's exactly the same thing. I can see how you don't want to equate those terms I suppose.
I don't think I can continue responding to you further as you clearly haven't put much thought into what you are writing or don't share the terminology most people use to discuss these topics. You might want to read into the benefits of a trusted code base and a provable kernel for operating system security. Thanks for the comment.