News for hackers. Stuff that matters.
Re:I am not yet ready to switch to Zig from Rust by knighthack on Friday June 14, 2024 @12:15PM (#40682110)
How is it a "better C" as compared to Go? Genuinely asking.
Re:I am not yet ready to switch to Zig from Rust by Bilal_io on Friday June 14, 2024 @12:19PM (#40682139)
Go is a garbage collected language
Re:I am not yet ready to switch to Zig from Rust by kstrauser on Friday June 14, 2024 @12:19PM (#40682143)
Go is garbage collected. That's a non-starter for a lot of C use cases.
Re:I am not yet ready to switch to Zig from Rust by ilrwbwrkhv on Friday June 14, 2024 @12:21PM (#40682156)
Go would be amazing if it didn't allow dumb mistakes such as:

    type Human struct {
        Name string
        MaybeHasCat *Cat
    }

    type Cat struct {
        Name string
    }

    func main() {
        h := Human{}
        h.MaybeHasCat.Name = "Taffy" 
    }
And boom. Null pointer exception because MaybeHasCat is null. The fact that go doesn't let you define an optional type is such a pain. A lot of newcomers while getting trained up fall for this bug.

edit: updating to add the pointer i missed. also adding a playground link: https://go.dev/play/p/izcod8xF7ZQ

Re:I am not yet ready to switch to Zig from Rust by koeng on Friday June 14, 2024 @12:26PM (#40682207)
That’s not true. Here is a go playground of pretty much that exact code running just fine

https://go.dev/play/p/v7OM9s_pRqY

Re:I am not yet ready to switch to Zig from Rust by deathanatos on Friday June 14, 2024 @12:51PM (#40682441)
Steelman their example. Given that they named the member "MaybeHasCat", it's pretty clearly meant to analogue an Option<Cat>; if you correct the small typo then (make the type of "MaybeHasCat" a pointer, so that it can store nil for the other half of the Maybe), the example behaves exactly as they describe.
Re:I am not yet ready to switch to Zig from Rust by iknowstuff on Tuesday June 18, 2024 @05:35AM (#40715702)
Wtf? what are you doing? Did the point fly over your head, are you being malicious by removing the star, or?
Re:I am not yet ready to switch to Zig from Rust by koeng on Wednesday June 19, 2024 @06:14PM (#40733003)
They added the star as an edit because of my playground link. So, neither
Re:I am not yet ready to switch to Zig from Rust by burnished on Friday June 14, 2024 @01:02PM (#40682551)
That would work. It would need to be a pointer to get a nil pointer exception, or an interface (obv function call to trigger instead of field access), but there are some simple and common patterns you would follow to prevent that.

Edit: should do more than just suggest the fix is easy

So for pointer types you have two options IMO: nil checks, or getters that do the nil check for you.

I think a map type instead of a string would also make your point more strongly because your zero value will fail on access. Which yeah that sucks to run into, and I'd agree actually that a lot of Go painpoints pop up early. I appreciate that now, because most of my foe stubbing was done inside the first few weeks, but it is undeniable imo.

Re:I am not yet ready to switch to Zig from Rust by ilrwbwrkhv on Friday June 14, 2024 @01:31PM (#40682831)
> nil checks, or getters that do the nil check for you

Yes I agree there are patterns to solve for this but it is just strange that the compiler doesn't stop you from making these errors. I mean even Typescript has:

  interface Human {
    name: string
    cat?: Cat
  }
Re:I am not yet ready to switch to Zig from Rust by burnished on Friday June 14, 2024 @01:52PM (#40683076)
I don't know what 'even typescript' is supposed to mean. Are you saying that typescript is the natural bar for comparison here? That doesn't seem correct, isn't typescript a project that tries to correct javascript's lack of typing?

Since it isn't an error to have a nillable type, and it isn't an error to access a field, it makes sense that the compiler doesn't error when you do that thing. If you want a warning when doing something silly then you can setup a linter.

If your first thought is that is not very beginner friendly then I agree with you - I edited my original response. But otherwise there are solutions to these problems.

If that doesn't suit you and Go isn't sweet enough for you, well, fair. Its rather austere. I don't think it is a categorical error for the project (though there are features I would also like for asking).

Re:I am not yet ready to switch to Zig from Rust by ilrwbwrkhv on Friday June 14, 2024 @02:20PM (#40683411)
My point is nillable values by default is a strange choice and throws out 50 years of computing history. It has been clearly established that it leads to null pointer exceptions. The fact that a modern language lets you do it is a bit strange.
Re:I am not yet ready to switch to Zig from Rust by burnished on Friday June 14, 2024 @03:36PM (#40684219)
Oh I didn't really get that from what you had been saying.

Sure, I'd agree it feels like a whoopsie, I dislike nil values because they are a common source of faults.

Re:I am not yet ready to switch to Zig from Rust by matrix87 on Friday June 14, 2024 @12:27PM (#40682215)
Could just do null -> none, nonnull -> some, optional doesn't introduce anything new here. Either you null check or you optional check

Optionals are just another outlet for "best practice" bullshittery and not much else. If go doesn't have, sounds like they're following YAGNI principle

Re:I am not yet ready to switch to Zig from Rust by ilrwbwrkhv on Friday June 14, 2024 @03:36PM (#40684218)
> Could just do null -> none, nonnull -> some, optional doesn't introduce anything new here. Either you null check or you optional check

I am not sure what you mean by the first point but what I am saying is that the compiler doesn't stop you from having a basic runtime null pointer exception because of "simplicity" and "yagni".

Re:I am not yet ready to switch to Zig from Rust by archgoon on Friday June 14, 2024 @12:29PM (#40682236)
I think you meant

  type Human struct {
     Name string
     MaybeHasCat *Cat
  }
As you have written (not making MaybeHasCat a pointer), go will correctly initialize (at least as of go1.20.5) the nested Cat structure and allow for direct assignment.

Having a null pointer exception for a null pointer is a behavior I would expect. Having one for a non-pointer structure would be surprising.

Re:I am not yet ready to switch to Zig from Rust by adrusi on Friday June 14, 2024 @12:22PM (#40682176)
Go has a heavy runtime, including both a garbage collector and a userland scheduler. Those features both make it inappropriate for some applications where you would use c, and also make calling (and especially being called from) foreign code problematic. You effectively cant implement a library in go and then call it from another language, not without considerable ffi overhead at the very least.
Re:I am not yet ready to switch to Zig from Rust by cletus on Friday June 14, 2024 @12:34PM (#40682280)
Let me preface this by saying I like Go. I do. But as much respect as I have for Rob Pike (which, again, I do), he doesn't understand the systems programming space. Go was originally pitched as a systems programming language, a better C, like you said.

But it isn't. It is, however, a better Python (IMHO).

The reason it's not a better C is that it's a garbage-collected language and it has a runtime overhead. As such, Go doesn't really have predcitable performance. It's easy to blow up memory usage (as it is on any GC language) eg goroutines.

So Go just doesn't suit a typical systems or embedded application. Yes, you can use a subset of Go to avoid dynamic allocation and GC in general but really, what's the point in that?

Why it's a better Python (again, IMHO) is that Python has all the same negatives but has a few more, most notably that it is dynamically typed or, as I like to put it, you need to write unit tests for spelling mistakes. I've come to abhor dynamic typing as a truly horrendous false economy. Go doesn't have that problem. Go does need to be compiled but it's a simple language and that compilation is incredibly fast.

My one criticism is that I find Go's unbuffed channels to be a less elegant coordination mechanism to cooperative async/await in other langauges. But YMMV.

Some evidence to back this up is that, at least while I was still at Google, Go projects on google3 were cannibzlizing Python projects and nothing else really.

Re:I am not yet ready to switch to Zig from Rust by mark_undoio on Friday June 14, 2024 @12:55PM (#40682483)
> Go was originally pitched as a systems programming language, a better C, like you said.

I've always understood this claim as a particular (rather restricted) interpretation of "systems" code - meaning network servers, basically (maybe also CLI applications?)

I'd always thought of "systems" as including things like writing standard libraries, kernels and embedded code. But I guess there is a decent slice of other systemsy stuff that Go is good for.

Whereas something like Zig feels like it could really be a better systems programming language in general that C, in all of its different application areas.

Re:I am not yet ready to switch to Zig from Rust by stouset on Friday June 14, 2024 @01:46PM (#40683006)
> I've always understood this claim as a particular (rather restricted) interpretation of "systems" code

This is basically the retcon that the golang community has settled on but it's frankly not true.

When go was originally being promoted it was heavily advertised as a systems language suitable for writing low-level programs. Nowhere was it caveated that "systems language" means something different from what everyone understood a "systems language" to be at the time. Only when it more or less failed to gain traction in that space did this get redefined to mean "network servers that mostly just shuffle bytes around and CLI applications".

Re:I am not yet ready to switch to Zig from Rust by Capricorn2481 on Friday June 14, 2024 @12:47PM (#40682393)
Python also has some positives that Go doesn't have, like iterators without the community freaking out about them. It's obviously way more ergonomic to use Python, and if you want types, Pyright works very well.

My issue with Go is that it's not low level enough to be good for systems programming but it's not high level enough to avoid boilerplate.

Re:I am not yet ready to switch to Zig from Rust by nkozyra on Friday June 14, 2024 @03:50PM (#40684369)
> My issue with Go is that it's not low level enough to be good for systems programming but it's not high level enough to avoid boilerplate.

That's really interesting because in general I find Go faster to work in than Python. Python has great flexibility but even production code I read is littered with noise that I don't see with Go applications. Other than error propagation - which is more a style choice than boilerplate - I find doing something in Go results in fewer lines of code and less spaghetti logic.

I'm a bit too dug in on Rust to spend a ton of time replacing it with Zig and my use cases frankly could be handled by a Go app without much worry about performance. But one thing Rust has is boilerplate out the wazoo.

Re:I am not yet ready to switch to Zig from Rust by Capricorn2481 on Friday June 14, 2024 @05:09PM (#40685158)
I have heard this anecdote a few times but I don't understand it. Even ignoring error handling in Go, I feel like everything is noticeably more verbose and noisy than something like Python. A language that prioritizes readability is intriguing to me, but I just haven't experienced that with Go.

Not that I haven't seen messy Python code (I sure have). The best Go code is gonna look better than the worst Python. But on average, it seems like complicated flows can be written very elegantly and readably in Python and look ugly in Go.

Re:I am not yet ready to switch to Zig from Rust by etse on Saturday June 15, 2024 @04:44PM (#40692570)
Go isn't pretty to look at, but I feel so much more confident in a successful Go build than starting up Python–not knowing when exceptions will throw or crash until it's run is frustrating.

I'm sure Rust folks feel exponentially more safety than Go at compile time, but the jump from Python to Go is dramatic for me.

Re:I am not yet ready to switch to Zig from Rust by adamors on Friday June 14, 2024 @12:50PM (#40682424)
As someone who used to write a lot of Ruby and now has started to write some Go, I feel like you nailed it.

Go is compiled language for people coming from dynamic languages. The type inference is good enough and the compilation types are also quite fast.

Re:I am not yet ready to switch to Zig from Rust by orwin on Friday June 14, 2024 @12:52PM (#40682452)
I dubbed Go 'C+-' the first time I used it, and it was on a program that made heavy use of threading and used a producer-consumer workflow, so I don't think I could have used a better program to test it (and I think Go was the best language for my program).

It probably has changed since, it has been 10 years now, but my feelings were at first 'wow! This is easy' during the prototyping phase, then 'ugh, i'm so limited' during the finalization (and at random points in the middle too probably, but I was fanboying at the time so I didn't really notice). One of the worst thing is the debugger imho. I _get_ gdb. I haven't written a line of C in years, you put me in an interactive gdb, I'm home. Go, I didn't understand how to debug, I had to use my 1rst year technique of printing everywhere, except I never managed to make use of %p, so I was even less effective than that.

Re:I am not yet ready to switch to Zig from Rust by mikemitchelldev on Friday June 14, 2024 @12:58PM (#40682508)
Delve is a great debugger for the Go.
Re:I am not yet ready to switch to Zig from Rust by orwin on Saturday June 15, 2024 @11:10AM (#40690276)
Bear in mind this was 10 years ago hopefully Go have a debugger now, but still, it won't be gdb.
Re:I am not yet ready to switch to Zig from Rust by etse on Saturday June 15, 2024 @04:48PM (#40692596)
Go's debugger has worked just fine for years. What do you prefer about gdb (which also seems to support Go)?