9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lamg <gort.andres000@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go for systems programming
Date: Fri, 17 May 2013 13:53:00 -0400	[thread overview]
Message-ID: <CAHwE2-snLrPeZ64ycb7Dmfo5zZqUaP3WeJBsk9tEvbSsSeeQFQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmJppM0h6ODmziNnbu7PUWAVKxme6D_5927ENcPRywN1Uw@mail.gmail.com>

What about lack of makefiles and fast compilation times?, I don´t want
to "remove" that.  The  point is making a more practical C, not a
Go--. Go´s grammar is designed for being easy to parse (and is
different), so it wouldn´t be C without punctuation symbols; and Go´s
package system makes the compilation faster. What about the
preprocessor? Can we get rid of that?
 If think if we can make better our lives, why wouldn´t do we? About
the support, well is difficult to break our links with the past, but
as a parallel long term project changing one thing at the time when it
is ready would be possible to achieve stability and to write programs
more easy.

2013/5/17, Skip Tavakkolian <skip.tavakkolian@gmail.com>:
> Go's is a great language that makes it easy to write applications of all
> sizes well, but its greatest benefit to Plan 9 is the plethora of packages
> that make it possible to deal with the numerous Web standards.
>
>
>
> On Fri, May 17, 2013 at 9:31 AM, Matthew Veety <mveety@gmail.com> wrote:
>
>> On May 17, 2013, at 11:51, lamg <gort.andres000@gmail.com> wrote:
>>
>> > I think it will be nice for Plan9 having such language-compiler, Go
>> > has proved to be an improvement over C in its own niche.
>> >
>>
>> In its own niche is the important point here. Just because writing a
>> kernel or system utilities can be done in Go doesn't mean it should be.
>> Go
>> isn't even totally stable or feature complete on Plan 9 at this point.
>> You
>> get the same shit in C on Plan 9 as you do Go plus it's more stable and
>> has
>> better support.
>> At this point I would say keep using C unless you have some specific need
>> to use Go on Plan 9.
>>
>> --
>> Veety
>>
>



  reply	other threads:[~2013-05-17 17:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 15:51 lamg
2013-05-17 16:07 ` Nemo
2013-05-17 18:45   ` Bakul Shah
2013-05-17 19:23     ` hiro
2013-05-17 20:31     ` Kurt H Maier
2013-05-17 20:37       ` erik quanstrom
2013-05-17 20:42       ` Bakul Shah
2013-05-17 20:46         ` Matthew Veety
2013-05-17 21:05           ` Bakul Shah
2013-05-17 21:53             ` Kurt H Maier
2013-05-18  3:17         ` erik quanstrom
2013-05-17 16:31 ` Matthew Veety
2013-05-17 16:49   ` erik quanstrom
2013-05-17 17:28   ` Skip Tavakkolian
2013-05-17 17:53     ` lamg [this message]
2013-05-17 20:29       ` Charles Forsyth

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=CAHwE2-snLrPeZ64ycb7Dmfo5zZqUaP3WeJBsk9tEvbSsSeeQFQ@mail.gmail.com \
    --to=gort.andres000@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).