Originally posted by Tiger_Coder
View Post
Announcement
Collapse
No announcement yet.
Latest Trolling? The Linux Kernel In Perl
Collapse
X
-
IIRC, there was an OS written in Haskell a while back. Development stopped, but it was fairly functional.
In fact...here's a stackoverflow question with a fairly comprehensive answer: http://stackoverflow.com/questions/6...ten-in-haskell
I think I was thinking of House.
Comment
-
^^ You don't have to do something just because it can be done. There is so much stupid stuff being done on this premise, utter waste of resources, and for what, just because you are in a desperate need to shine with something "original" and you could not thing of anything actually original and instead opt for something no one has done simply because it is pointless.
Perl is anywhere between 2x and 200x slower than C - THE language of choice for kernel development, and the distribution is predominantly in the upper regions of this range. Also the very notion of using a dynamic interpreted language to write kernels sounds bad and dangerous to begin with. Surely, it might be useful to "open up" a C kernel for a narrow, safe and specific context to modify with a dynamic language, but writing entire kernels sounds like a terrible idea. And yes, I know performance is not the utmost concern when writing kernels, but it is still very important in the majority of cases, but running Perl code in kernel mode simply doesn't sound like a good idea.
Comment
-
Originally posted by ddriver View Post^^ You don't have to do something just because it can be done. There is so much stupid stuff being done on this premise, utter waste of resources, and for what, just because you are in a desperate need to shine with something "original" and you could not thing of anything actually original and instead opt for something no one has done simply because it is pointless.
Perl is anywhere between 2x and 200x slower than C - THE language of choice for kernel development, and the distribution is predominantly in the upper regions of this range. Also the very notion of using a dynamic interpreted language to write kernels sounds bad and dangerous to begin with. Surely, it might be useful to "open up" a C kernel for a narrow, safe and specific context to modify with a dynamic language, but writing entire kernels sounds like a terrible idea. And yes, I know performance is not the utmost concern when writing kernels, but it is still very important in the majority of cases, but running Perl code in kernel mode simply doesn't sound like a good idea.
Now, to pull out my straw-man's hat. If everyone decided not to do things, because "it can be done" (as you say), a lot of good things would never be invented or so. Imagine if someone said "why are you wasting your time on creating that stupid levitating train; it's too expensive to operate, and we already have working trains that do just fine!" Well, guess you can forget about traveling 200+ miles in under an hour without flying. Or maybe someone said "internal combustion engine? pfft, we've already got steam engines, why would we want that? It's horribly inefficient anyway!" (this was done for electric vehicles a long time ago, by the way, though inefficiency wasn't the reason they were dismissed, but rather effective range of operation)
Comment
-
Originally posted by ddriver View Post^^ You don't have to do something just because it can be done. There is so much stupid stuff being done on this premise, utter waste of resources, and for what, just because you are in a desperate need to shine with something "original" and you could not thing of anything actually original and instead opt for something no one has done simply because it is pointless.
Comment
-
Originally posted by Nobu View PostNow, to pull out my straw-man's hat. If everyone decided not to do things, because "it can be done" (as you say), a lot of good things would never be invented or so. Imagine if someone said "why are you wasting your time on creating that stupid levitating train; it's too expensive to operate, and we already have working trains that do just fine!" Well, guess you can forget about traveling 200+ miles in under an hour without flying. Or maybe someone said "internal combustion engine? pfft, we've already got steam engines, why would we want that? It's horribly inefficient anyway!" (this was done for electric vehicles a long time ago, by the way, though inefficiency wasn't the reason they were dismissed, but rather effective range of operation)
Comment
-
Originally posted by mrugiero View PostIt's really not that similar, as all those examples had the possible benefits explained before doing anything. A kernel in haskell has its possible benefits explained (haskell guarantees no side effects, so you get a trivially parallelizable kernel, which should help with scalability), internal combustion engine means you can use an alternate energy source (while previously it was coal or coal, and oil looked far more abundant at the time), the train, you named it yourself, it can help you travel fast and efficiently. Perl kernel? None explained. Maybe there are possible advantages, but the guy didn't bother explaining, if he even thought of any. That being said, it's his time. I'm never against anyone having hobbies. He shouldn't expect having it mainlined, though.
Comment
-
Originally posted by Nobu View PostWell, you have to drop a ball first before being able to say that it will (with certainty) bounce...unless you do some math or have prior examples.
Comment
Comment