3 ms·
"Let's wait until Go has reached Java's maturity and see what happens when they change this package ;)" They did a while back, actually. Compare https://pkg.go
by jerf 3y ago
"Let's wait until Go has reached Java's maturity and see what happens when they change this package ;)"
They did a while back, actually. Compare https://pkg.go.dev/unsafe@go1.0.1#Pointer https://pkg.go.dev/unsafe@go1.0.1#Pointer with https://pkg.go.dev/unsafe#Pointer https://pkg.go.dev/unsafe#Pointer , in particular the modern very precise description of exactly what you can do with an *unsafe.Pointer. I'm not sure what the cutoff for that was but it was a while ago, yes. Still, it didn't do much.
- valenterry 3y agoInteresting! Personally I'm not a big fan of either Java nor excessive backwards compatibility. But I can't avoid noticing that a lot of people praise Go for things like the backwards compatible while despising Java at the same time, even though both languages are extremely similar in lots of regards.
- geodel 3y agoIt is not clear that people despise Java or they despise backward compatibility of Java. Because I haven't see anyone despising Java's backward compatibility.
- valenterry 3y ago> Because I haven't see anyone despising Java's backward compatibility. I'm happy to have beers, just so that you get the chance to see someone like that. :-)