mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel Bonekeeper" <thehazard@gmail.com>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: "Jacek Luczak" <difrost.kernel@gmail.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: RFC: Writing Solaris Device Drivers in Java
Date: Tue, 1 Apr 2008 09:51:15 -0300	[thread overview]
Message-ID: <e1e1d5f40804010551q392b7717pf3004f804e154c6a@mail.gmail.com> (raw)
In-Reply-To: <804dabb00803310754q40eaca5ai8b9faacecef0edef@mail.gmail.com>

On Mon, Mar 31, 2008 at 11:54 AM, Peter Teoh <htmldeveloper@gmail.com> wrote:
> On Mon, Mar 31, 2008 at 7:58 PM, Jacek Luczak <difrost.kernel@gmail.com> wrote:
>  > Peter Zijlstra pisze:
>
> >  >
>  >  Java? Compete against C? Don't scare embedded devs.
>  >
>
>  The future is always uncertain for us.   Embedded development usually
>  emphasizes on performance, unlike those of the desktop.   So which
>  language will be king tomorrow in embedded, it boils down to
>  performance + optimization + ease of development.   Just imagine:
>  from 10 lines of C reduced to 2 lines of XXX-based language software -
>  I think the 10 lines will scare off the embedded developers of
>  tomorrow.    I may be wrong :-).

I hope you are... otherwise I may not have the necessary patience to
cope with such people in the future =)
It's funny how people nowadays are dumbing down languages & systems to
fit expectations of how easy programming should be [for a newbie]...

One thing that I can live with is the fact that program interfaces are
getting dumber by the week so that the "general user" can use them
without thinking too much.

Another thing that I cannot accept is people who call themselves
developers wanting to push stuff like Java where it doesn't belong to
make it easier on the kids who're entering the field (maybe on
themselves ?), who are supposed to know how the computer works, live
with it and actually like it, specially the low level stuff.

Who would trust a surgeon who's afraid of a little blood ?

On the other hand, it's always good to know that there will always be
a need for the real programmers, apparently =)

-- 
What this world needs is a good five-dollar plasma weapon.

      reply	other threads:[~2008-04-01 12:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31  2:14 Peter Teoh
2008-03-31  2:59 ` Bernd Eckenfels
2008-03-31  3:13   ` Al Viro
2008-03-31 15:18   ` Peter Teoh
2008-03-31 15:52     ` Peter Teoh
2008-03-31 16:20       ` Ioan Ionita
2008-03-31  3:10 ` David Miller
2008-03-31  5:56 ` Willy Tarreau
2008-03-31  8:48   ` David Newall
2008-03-31  8:12 ` Benjamin Herrenschmidt
2008-03-31 10:28 ` Peter Zijlstra
2008-03-31 10:45   ` Wander Winkelhorst
2008-03-31 11:58   ` Jacek Luczak
2008-03-31 14:54     ` Peter Teoh
2008-04-01 12:51       ` Daniel Bonekeeper [this message]

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=e1e1d5f40804010551q392b7717pf3004f804e154c6a@mail.gmail.com \
    --to=thehazard@gmail.com \
    --cc=difrost.kernel@gmail.com \
    --cc=htmldeveloper@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®