Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.misc > #1489

Re: should we Go now?

From Ivan Shmakov <oneingray@gmail.com>
Newsgroups comp.lang.misc, comp.lang.perl.misc
Subject Re: should we Go now?
Date 2013-02-24 17:02 +0000
Organization Aioe.org NNTP Server
Message-ID <874nh1abn5.fsf@violet.siamics.net> (permalink)
References <87hal29eeb.fsf@violet.siamics.net> <87ehg5u0r3.fsf@sapphire.mobileactivedefense.com>

Cross-posted to 2 groups.

Show all headers | View raw


>>>>> Rainer Weikusat <rweikusat@mssgmbh.com> writes:
>>>>> Ivan Shmakov <oneingray@gmail.com> writes:

[...]

 >> as Go seem to be positioned as a successor to both the "system
 >> programming languages" (C) and the "Web programming languages," of
 >> which Perl is one I'm familiar with.

 > I'm using Perl for 'system programming' and 'Go' won't replace it (it
 > also won't replace C) for the simple reason that it uses another "I
 > swallowed the Kool Aid and it was sure tasty!" runtime environment:

[...]

 > a couple of assumptions about the execution environment of the
 > original Lisp implementation (AFAIK, an IBM 704 machine) such as 'no
 > multiprogramming, no networking, single userspace application in
 > total control of the environment, pointers are not data' which
 > essentially haven't been true anywhere since

	Doesn't seem to be all that applicable to Go.  Consider that:

	* Perl uses GC;

	* so does Emacs;

	* Go provides multiprogramming facilities "out of box";

	* Go seem to have a decent networking library;

	* Go has pointers.

	Somehow, Go seem to lack destructors, although I don't quite
	understand how this goes well along with having a GC.  But
	perhaps it doesn't.

	Other than that, my most major objection to Go's design
	currently is its syntax.

[...]

-- 
FSF associate member #7257

Back to comp.lang.misc | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-24 10:47 +0000
  Re: should we Go now? Ben Morrow <ben@morrow.me.uk> - 2013-02-24 13:40 +0000
  Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-24 16:37 +0000
    Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-24 17:02 +0000
      Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-24 19:38 +0000
        Re: should we Go now? Nils M Holm <news2009@t3x.org> - 2013-02-25 07:23 +0000
          Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-25 17:30 +0000
      Re: should we Go now? Ben Morrow <ben@morrow.me.uk> - 2013-02-24 21:42 +0000
        Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-24 22:26 +0000
        Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-25 01:04 +0000
        Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-25 13:32 +0000
          Re: should we Go now? Ben Morrow <ben@morrow.me.uk> - 2013-02-25 15:28 +0000
            Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-25 17:54 +0000
      Re: should we Go now? "BartC" <bc@freeuk.com> - 2013-02-25 01:29 +0000
        Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-25 13:12 +0000
  Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-24 17:04 +0000
  Re: should we Go now? Bjoern Hoehrmann <bjoern@hoehrmann.de> - 2013-02-24 18:24 +0100
  Re: should we Go now? Keith Thompson <kst-u@mib.org> - 2013-02-25 17:01 -0800

csiph-web