News for hackers. Stuff that matters.
Re:I disagree with Linus Torvalds about C++ (2009) by jacquesm on Monday December 24, 2018 @07:21AM (#18751815)
Agreed, unless the purpose is to extract lessons learned. I can think of several where that has not happened yet.
Re:I disagree with Linus Torvalds about C++ (2009) by giancarlostoro on Monday December 24, 2018 @07:51AM (#18751893)
One thing I always do when they happen is read through the comments anyway, sometimes people bring up some rather insightful things about a language, editor or whatever. Having heard from an emacs user why he prefers it over vim made me really appreciate emacs. I'll use either vim or emacs though, just don't care personally as long as I can: open a file, edit a file, and save a file. I also use full blown "bloated" IDEs.

Of course I ignore a lot of comments, but try to go for the ones that seems intelligible.

Re:I disagree with Linus Torvalds about C++ (2009) by cube2222 on Monday December 24, 2018 @09:38AM (#18752296)
What was it that he said about emacs?
Re:I disagree with Linus Torvalds about C++ (2009) by giancarlostoro on Monday December 24, 2018 @09:49AM (#18752349)
It was some blogpost I can't seem to find, but they explained all the different things they can do from within emacs, which were lots of things vim doesn't seem to be capable of doing, things such as SSH'ing to a remote system to open files remotely, fully being capable of handling mail through emacs, being able to use emacs as a web browser as well which is interesting, and other things which were fascinating enough to me. There's also the built-in git functionality, which some people use emacs exclusively to manage their usage of git.

The emacs editor really is an Operating System to it's own extent. I really fell in love with the idea of being able to just work all day with nothing but emacs, I have not gotten to that point yet though. Being able to not leave my editor for anything sounds pretty useful if done right.

Re:I disagree with Linus Torvalds about C++ (2009) by ci5er on Monday December 24, 2018 @08:42AM (#18752068)
> I can think of several where that has not happened yet.

Tell me more! :-)

Re:I disagree with Linus Torvalds about C++ (2009) by jacquesm on Monday December 24, 2018 @09:29AM (#18752262)
Monolith vs Microkernel.

I suspect in the long run that one will be settled in favor of the microkernel, but it will take a long long time to get there. Missed chance if there ever was one, but I can see some ulterior motives to keep the kernel as complex and hard to contribute to as possible. If everybody could write drivers then where would be the glory in that...

Re:I disagree with Linus Torvalds about C++ (2009) by ci5er on Monday December 24, 2018 @09:37AM (#18752294)
> If everybody could write drivers then where would be the glory in that...

Everyone can write drivers. It's one of the few things we can do in monolith-land. I guess I'm probably missing your point.

Re:I disagree with Linus Torvalds about C++ (2009) by jacquesm on Monday December 24, 2018 @10:02AM (#18752410)
> I guess I'm probably missing your point.

Yes you are, but that's fine. I totally see why the difference between 'can' and 'actually does' is lost. The reason for that is simple: device driver writing on a monolithic kernel is something of a black art, even with all the tools we have at our disposal today. On a microkernel you'd just be writing any other user process, with access to a couple of ports and and maybe a special hook to handle hw interrupts, but other than that you would not be able to tell the difference. Debugging would be almost as easy as debugging any other user process. You could use a whole slew of high level languages to do your device driver writing. If the interpreters on the system would take care of the lower levels of interacting with the kernel to deal with IO and/or interrupts then you could do your device driver writing in interpreted languages.

But, you'll have to wait a little longer to be able to do that. Or try to locate a copy of QnX...

Re:I disagree with Linus Torvalds about C++ (2009) by zozbot123 on Monday December 24, 2018 @10:33AM (#18752554)
> On a microkernel you'd just be writing any other user process, with access to a couple of ports and and maybe a special hook to handle hw interrupts

This is a fiction. Hint: if a "user process" can wreak havoc on the system simply by misbehaving (in a way that may or may not be malicious), as drivers interacting with low-level hardware can, it's not a user process in practice, and should not be understood as one. The whole point of making that kernel vs. user space distinction in the first place is so that user programs can't wreak havoc on the system. There are plenty of things that can and should be done in userland (and oftentimes they are, see e.g. Plan9), but drivers are not among these unless you can always rely on something like IOMMU to make sure that the hardware cannot be made to misbehave in a way that affects security guarantees.

Re:I disagree with Linus Torvalds about C++ (2009) by jacquesm on Monday December 24, 2018 @10:58AM (#18752668)
> This is a fiction.

No, it has existed roughly since the mid 80's. Source: programmed a whole bunch of stuff including very fast serial hardware drivers on systems like that.

The users process can not wreak havoc on the system, no matter how much it would misbehave in that context.

Hardware typically has pretty clearly spelled out bounds and limitations, users processes operate with less rather than more privilege than a kernel side thread would and so have much less in terms of ability to wreck the system. As an extra bonus: a microkernel is small enough that formal verification is an option.