News for hackers. Stuff that matters.
Re:Declined Proposal: A built-in Go error check function, “try” by wybiral on Tuesday July 16, 2019 @08:33PM (#20455325)
> I think the Golang community is going to find itself growing more slowly as folks increasingly realize other options offer similar benefits without the bad ergonomics.

Personally I enjoy writing Go code similar to the way that I enjoy writing Python code. So they did something right because I wouldn't ever say the same about Java or PHP.

Edit: As a fun tangent... Python experienced the same kind of fracturing that adding generics or other dramatic features to a language can cause with the 2to3 move. There are still projects based on 2.7. It was hard to get people all on the same page once the community was split. What's also interesting is to watch the same thing happen with asyncio, which is practically an all-or-nothing thing to use in your Python project, so much so that most Python code still doesn't use it. Just an observation, but breaking changes to a language can really do a number on the community.

Re:Declined Proposal: A built-in Go error check function, “try” by KirinDave on Tuesday July 16, 2019 @08:38PM (#20455355)
I don't think folks are on 2.7 because they love it. I think they're there because it's difficult and expensive to migrate Python code.
Re:Declined Proposal: A built-in Go error check function, “try” by wybiral on Tuesday July 16, 2019 @08:43PM (#20455380)
There were multiple reasons based on my experience. New people were still using 2.7 tutorials because there was way more information out there than for 3. And package managers in Linux systems took a long time to change.

But the asyncio example is probably a better example of a fundamental program design change that's causing weird fracturing and incompatible library designs. Trying to use non-async from an async framework is a mess, trying to use async from a non-async is hard to integrate, etc.

Re:Declined Proposal: A built-in Go error check function, “try” by viraptor on Tuesday July 16, 2019 @09:14PM (#20455539)
I don't believe that python 2/3 change has much to do with sync/async issues. In python 2 we had twisted which was its own async universe. The sync and async worlds are disconnected in pretty much every language, but it's mostly a non-issue. You just don't mix them and it doesn't become a mess.
Re:Declined Proposal: A built-in Go error check function, “try” by wybiral on Tuesday July 16, 2019 @09:19PM (#20455555)
That's not what I said, they were two times that the community fractured.

There is fracturing with asyncio. Look at popular libraries. The "requests" library comes to mind, but there are others. It's hard to use different 3rd party components between the two paradigms which causes fragmentation in the libraries. You end up with aiohttp-requests and stuff.

PS: it does make a huge difference. If someone posts "how do I make a web server?" on a forum you'll get two different frameworks and approaches as answers. The community basically goes in two directions and much of the work becomes incompatible. The multithreaded sync vs event loop async just don't play well with each other. There still aren't many 3rd party libraries that really focus on asyncio because much of the community is still in the "threaded" design.

Re:Declined Proposal: A built-in Go error check function, “try” by a1369209993 on Wednesday July 17, 2019 @12:22AM (#20456435)
I don't know about love, but it's significantly better than python3. I'm on 2.7 because the authors refuse to continue development of python in favor of a different, inferior language. Difficulty and expense of migration have nothing to do with it.
Re:Declined Proposal: A built-in Go error check function, “try” by meruru on Tuesday July 16, 2019 @10:46PM (#20455969)
pg wrote a bunch of really good essays about Java vs Python vs Lisp and how those were perceived by programmers. I always remember them when I see Go being compared to Java while still being liked by Hackers. I wonder what he would write about this phenomenon.
Re:Declined Proposal: A built-in Go error check function, “try” by parasubvert on Wednesday July 17, 2019 @12:31AM (#20456470)
pg has a blind spot wrt Java. Lots of hackers liked (and still like) Java ecosystem (see Kotlin for more recent fun). like lisp hackers, they hung out on their own and didn't mingle.
Re:Declined Proposal: A built-in Go error check function, “try” by erik_seaberg on Wednesday July 17, 2019 @04:18AM (#20457527)
Java without generics and lambdas was terrible. Yegge's https://steve-yegge.blogspot.com/2006/03/execution-in-kingdo... was spot on because the only way to pass an expression or a block of statements was to wrap it in an object and give it to something that knows which method to call.
Re:Declined Proposal: A built-in Go error check function, “try” by parasubvert on Wednesday July 17, 2019 @08:23AM (#20458641)
Java’s success was built in those days though. Personally I liked the language just fine without those features, Java generics in particular make code a lot less readable IMO.

This is partly why I like Golang so much, they’ve been focusing on readability.

I will agree that Lambdas are better than anonymous inner classes.

Re:Declined Proposal: A built-in Go error check function, “try” by checktheorder on Wednesday July 17, 2019 @09:04AM (#20458961)
>This is partly why I like Golang so much, they’ve been focusing on readability.

Speaking as someone who's just returned to coding after a two-decade absence (mostly for fun), this is the #1 thing I love about Golang. I can actually read code from very experienced and skilled developers and understand what they'd written. And yet the language itself is highly capable - I don't feel like I'm learning some "beginner" language, but a "real" one that I can use for practical purposes.

Re:Declined Proposal: A built-in Go error check function, “try” by meddlepal on Wednesday July 17, 2019 @01:24AM (#20456709)
This, but also I suspect a lot of people that claim to dislike Java are tainted by it's framework heavy ecosystem especially early-mid 2000s.

The language itself is fairly clean and very pragmatic.

Re:Declined Proposal: A built-in Go error check function, “try” by meruru on Wednesday July 17, 2019 @01:34AM (#20456764)
FWIW the essays I mentioned are from the early 2000s. Java's Cover is from 2001: http://www.paulgraham.com/javacover.html
Re:Declined Proposal: A built-in Go error check function, “try” by parasubvert on Wednesday July 17, 2019 @08:28AM (#20458676)
That essay has proven to be astonishingly wrong. It’s 18 years later and I suspect he’d say the same things about Golang.
Re:Declined Proposal: A built-in Go error check function, “try” by parasubvert on Wednesday July 17, 2019 @08:11AM (#20458561)
Possibly, though Java these days is largely “Spring”.
Re:Declined Proposal: A built-in Go error check function, “try” by KirinDave on Wednesday July 17, 2019 @02:37AM (#20457065)
Disclosure: I am not very impressed by Paul Graham as a programmer.

However I think he came by his dislike honestly. When he was actively working, Java was really quite frustrating.

Re:Declined Proposal: A built-in Go error check function, “try” by parasubvert on Wednesday July 17, 2019 @08:37AM (#20458748)
I have no doubt. I was one of the pro-Java people in 2001 (dating back to 1996). Language religious wars were really strong in those days, like there could only be one true language, everything else was a toy. The Java backers and community fought against that too aggressively relative to their own limitations.

Today each language ecosystem is much more self sustaining and has its own bizarre culture that looks frustrating to outsiders.

Re:Declined Proposal: A built-in Go error check function, “try” by meruru on Wednesday July 17, 2019 @01:32AM (#20456755)
Those essays were written a long time ago and reflected the situation at the time. I can't really say how accurate they were, but you're using the present tense and mentioning present technology, so I thought it would be worth to emphasize that.