All of these conclusions I kind of expected from studying Go without doing 'real' programming, but with some programming experience, they are *much* more apparent
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
please don't forget to mention deadlocks in channels and how easily they can be achieved. This and lack of generics - 2 reasons why I stopped learning Go.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I like rust, a lot, but it’s not the ideal tool for every application (no one tool ever is). I think it’s important especially to the die-hard RiiR crowd to hear your opinions and experience with this.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I’ve mostly used Go for work since 2013 or so. It’s great if you’re choosing between it and, say, Python or Node. It’ll run faster, produce a static binary, and the types prevent a lot of bugs when upgrading dependencies.
-
Where Go fails most is in putting goroutines into the hands of people who are not able to use them safely. Because most people writing Go weren’t coming from a background of threaded C and C++, like I was. That and too many runtime instead of compile time errors.
Kraj razgovora
Novi razgovor -
-
-
Nice! Looking forward to read this!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I am sure that would be another hot blog, just like Brian's Rust last week.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I like rust a lot and don't know go at all, really curious to read you :)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.