News for hackers. Stuff that matters.
Re:The long goodbye to C by sytelus on Friday November 10, 2017 @11:48AM (#15671092)
Go isn't systems programming language. As soon as you enforce gc built-in to language, it seizes to be systems programming language.
Re:The long goodbye to C by pjmlp on Friday November 10, 2017 @11:52AM (#15671129)
Tell that to Niklaus Wirth, Alan Kay, Joe Duffy, Luca Cardelli and quite a few other industry luminaries.
Re:The long goodbye to C by sytelus on Friday November 10, 2017 @11:58AM (#15671176)
Go being paddled by industry hot shots doesn't change the facts. A language designed for systems programming must have precise control on everything that goes on. When you are dealing with thousand threads on 100s of cores, every microsecond counts. When you are designing control software for aerial vehicles on embedded devices doing stuff in ISRs, every thing needs to be predictable. No one in their right mind will rely on gc in that kind of systems programming world.
Re:The long goodbye to C by abiox on Friday November 10, 2017 @12:14PM (#15671307)
this is a narrow and arbitrary definition of "systems programming". you seem to be describing something closer to hard realtime computing, which is not the same thing.
Re:The long goodbye to C by dboreham on Friday November 10, 2017 @12:22PM (#15671357)
Seriously? He's using the term in exactly the way everyone uses it, even Wikipedia : https://en.wikipedia.org/wiki/System_programming
Re:The long goodbye to C by abiox on Friday November 10, 2017 @03:49PM (#15672902)
if you read your link, even the wikipedia article authors do not restrict the notion to hard realtime computing.

it's not really how "everyone" uses it. it's a narrowing that a subset of vocal people have been trying to push, i can only presume for ideological purposes.

Re:The long goodbye to C by vvanders on Friday November 10, 2017 @12:28PM (#15671406)
That's one aspect, the other is targets with small(<10mb) footprints where GC falls over spectacularly when you don't have 2x your working set of free memory.

These aren't uncommon targets, the PSP traditionally had 8mb of system memory. Lots of embedded routers and "IoT" things, etc.

Part of this is confused by everyone having a different definition of "System Programming". In my view if there's a target where hardware constrains prevent suitable performance from a language then that language isn't fit to be considered a "System Programming" language.

Re:The long goodbye to C by pjmlp on Friday November 10, 2017 @01:04PM (#15671691)
A systems programming language is any language usable to write a full OS with it.

http://www.projectoberon.com

The only thing that Go lacks in regards to Oberon are a few intrisics in the unsafe package, easily doable in Assembly, just like ANSI C requires on its libc for bare metal programming.

Re:The long goodbye to C by lodi on Friday November 10, 2017 @02:06PM (#15672114)
By that definition Haskell is a systems programming language: https://en.wikipedia.org/wiki/House_(operating_system)
Re:The long goodbye to C by pjmlp on Friday November 10, 2017 @03:05PM (#15672519)
Of course.

C gets put into a pedestal, yet it is impossible to write an OS in pure ANSI C, without making use of language extensions or Assembly.

Re:The long goodbye to C by katastic on Friday November 10, 2017 @12:29PM (#15671412)
People who are suggesting a GC language for systems programming have literally never tried it. They're just repeating slogans they heard someone else say. Anyone who had wouldn't dare suggest it's easy or a perfect candidate for the job.

I've done it and it's a pain in the ass. Why? Because the GC is _non-deterministic_. On many languages it can fire up at any time, freeze your threads at any time, and take however long it wants to. "But it usually doesn't take that long!" And? AND? The problem is, you've immediately added a blackbox thread attached to all your data. Enjoy having your program segfault in areas that are completely unrelated because the GC didn't run the finalizer till later. Enjoy having to fix a bug that doesn't have a repeatable effect. You're automatically writing multi-threaded code (and all the complexity that entails) even when you have a single-thread.

A GC adds an entire dimension to bug fixing and potential failure points. Every bug, multiplied by every possible interaction with the GC. This is something that systems programming usually cannot afford. You need to be able to prove your code won't crash.

And that's one more thing. Tons of systems code pre-allocates everything for that crash reason. So what problem is GC actually going to solve when everything is already carefully pre-allocated?

It really sounds like people who aren't used to unmanaged languages are simply projecting their fear of the unknown. I use both types on a daily basis, and to me they're just "the right tool for the right job." I would never try to shoehorn the wrong tool into an ill-fitted application just because I like that tool.

Re:The long goodbye to C by vvanders on Friday November 10, 2017 @12:35PM (#15671454)
Yup, don't forget the fact that you'll end up doing pooling, free lists and the exact same performance tricks you'd need to do if you managed memory explicitly.

You're adding a ton of incidental complexity for a benefit that you can't take advantage of(programmer productivity) because you don't have the necessary resources to make it happen(large swaths of memory and > 50ms response times).

Re:The long goodbye to C by pjmlp on Friday November 10, 2017 @12:50PM (#15671585)
Except that we have done exactly that.

I was a Native Oberon user during the 90s.

Educate yourself on Oberon and Modula-3, read about Midori and then feel free to carry on the anti-GC campaign.

Re:The long goodbye to C by davidcuddeback on Friday November 10, 2017 @12:49PM (#15671581)
Instead of appealing to authority, maybe you could link to some actual arguments by these luminaries.

If you're interested in Rob Pike's take on Go, he expressed regret over initially calling Go a systems programming language, because it gave people the impression that it was appropriate for writing operating systems. He prefers to call it a "server writing language" or a "cloud infrastructure language." @6:45 in this panel discussion: https://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/Pa...

Re:The long goodbye to C by pjmlp on Friday November 10, 2017 @12:52PM (#15671598)
Yet Google just wrote Fuchsia's network stack and filesystem drivers in Go.

As for the links they are easy to find on my comments history.

I don't have to repeat them all the time the anti-GC crowd comes to town.

Re:The long goodbye to C by AnimalMuppet on Friday November 10, 2017 @03:27PM (#15672695)
Depends. Do you want to educate, or just to rant?

Note that the set of people who read your post today probably includes people who did not read your previous posts on the topic.

Re:The long goodbye to C by dboreham on Friday November 10, 2017 @12:21PM (#15671349)
Luminaries are not typically burdened with the task of making stuff that works.
Re:The long goodbye to C by pjmlp on Friday November 10, 2017 @12:59PM (#15671647)
Except that they did, just to have their work killed by politics.
Re:The long goodbye to C by nice_byte on Friday November 10, 2017 @11:59AM (#15671192)
oh sorry i didn't know oberon ever amounted to anything
Re:The long goodbye to C by oblio on Friday November 10, 2017 @12:17PM (#15671326)
But was that due to inherent flaws or due to the hype driven industry we are part of? "Look, Rails is so cool and magic and powerful and DHH is so hot", basically.
Re:The long goodbye to C by dboreham on Friday November 10, 2017 @12:20PM (#15671341)
Wonderful pun : "seizes".