All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Antti Heikkinen <antti.heikkinen.4@gmail.com>,
	linux-kernel@vger.kernel.org, advocacy@perl.org,
	beginners@perl.org
Subject: Re: Propose for LINUX kernel and PERL
Date: Sun, 05 Jan 2014 12:48:21 -0500	[thread overview]
Message-ID: <52C99AE5.6040209@gmail.com> (raw)
In-Reply-To: <CAM__s2Bk=Hgzm3-f7N=A032PxUV6N87=42qZ=7kt7u8d_Ny5gg@mail.gmail.com>

On 01/05/2014 12:46 AM, Antti Heikkinen wrote:
> To Dear Perl and LINUX kernel development community:
> 
> My propose to you at your list: is possible to write operate system
> in PERL? I am student in university, looked for interest project
> to conclude my study on LINUX kernel.
> 
> This semester, I take beginner PERL course and learn power of 
> procedural language. I automate many daily task with use of it.
> Very impressive ability to make many thing work, interpret or can
> compile also.
> 
> Also about LINUX, I talk to much fellow students and professors,
> and take a operate system course use FreeBSD and LINUX. FreeBSD
> okay, but they say LINUX kernel is too big and bloat, run poor with
> too many developer. And too much quick decision from leader with
> ego is too big and bloat too, kekeke.
> 
> LINUX kernel can perform more good if written in not C and C++ but 
> Perl? Just certain portion of LINUX kernel to rewrite? For
> instant, schedule or support of multithread? If so, should use
> Perl5 or Perl6, focus to x86 or x86-64? Can you want to join me
> this my project? But to hear your expertise.
No offense, but anyone who thinks that Perl (or any other interpreted
language except Lua) code will run faster than C is rather out of touch.
 C code doesn't have any of the translation overhead that interpreted
languages do. Perl is an extremely high level language, and thus suffers
from this even more (although it has been getting better about this in
recent years).  The only reason in fact that Lua manages to do almost as
well as native machine code compiled from C is that it uses a very
simple VM that is very similar in many respects to most modern processors.
> 
> Am excited to learn and begin study project. Can you want to join
> this my project? Please direct reply of email to myself.
> 
> Much thank to you, Antti Heikkinen
While I personally would never advocate a beginner trying to write an
entire OS because it is a HUGE undertaking (even more so in an
interpreted language like Perl), you might look into running Perl on
top of a micro-kernel like L4.  This would allow you to run Perl in
Ring 0/Kernel Mode.  If you wanted to use Lua instead (It's amazingly
easy to learn) then L4 would definitely be a good choice because the
init program for it already uses Lua.

  parent reply	other threads:[~2014-01-05 17:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05  5:46 Propose for LINUX kernel and PERL Antti Heikkinen
2014-01-05  8:12 ` bulk88
2014-01-05 23:43   ` Theodore Ts'o
2014-01-06  1:01     ` Al Viro
2014-01-05  8:50 ` Richard Foley
2014-01-05 17:48 ` Austin S Hemmelgarn [this message]
2014-01-06  1:45   ` Jovi Zhangwei
2014-01-05 22:32 ` Steven Rostedt
2014-01-06  1:49   ` Jovi Zhangwei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52C99AE5.6040209@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=advocacy@perl.org \
    --cc=antti.heikkinen.4@gmail.com \
    --cc=beginners@perl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.