It's official: Go sucks, ABSTRACT BULLSHITE FTW

http://yager.io/programming/go.html

Wow, #haskell really is a shithole huh.

>>110

What is the best answer? To switch compilers, incurring the kind of nightmare problems you describe above? That's not always even an option. Besides, if you're working with the same chip all the time, endian-awareness is not difficult.

Sometimes it's better to just give up and write the assembly yourself. That at least protects you from awful breakage that can happen even when changing compilation options on the exact same compiler, or upgrading to a newer version of same. I'm not saying that assembly is always the best choice but if changing compilers is a more likely event than changing ISAs it has its benefits.

If the unthinkable happens and you do happen to switch to a different chip later, assembly also has the nice property of making it totally obvious what code was written with ISA specific assumptions in mind. If you have co-workers that apply guards like #if __LITTLE_ENDIAN__ to 100% of the code they write, I want to know what magical environment you work in because everyone I've ever known will fuck this up if you're aren't testing for bi-endianness.

>>122

>>110

Crap, I mena >>112.

Sometimes it's better to just give up and write the assembly yourself.

That's fine, but I'd consider that tweaking the source and then some. I'm not arguing against the practice. I mean the cases where you need to care about this stuff and the cases where you end up writing assembly have quite a lot of overlap.

If you have co-workers that apply guards like #if __LITTLE_ENDIAN__ to 100% of the code they write

No, that's a pipe-dream. The upside is you can put this into library code and fail code review if someone tries to write their own. Maybe it's already there, try man 3 endian. Note the functions are all either htofoo or footoh, so they are portable modulo availability.

Example third-party implementation: https://github.com/digidotcom/xbee_ansic_library/blob/master/include/xbee/byteorder.h (Note the no-ops when the host has the same byte order.)

>>94
Re: "Everything he says under 'Embedded Programming' is shit and he is an uneducated pig"

Hmm, actually it looks like Oberon might be a better choice for embedded programming, if only someone would download the Oberon sources and change all the CAPS LOCK keywords to something more sensible (pretty easy fix). Go Language is after all just a plagarized copy of Oberon (half serious - it is inspired by Oberon). But oberon allows you to use the Stack, which is great for embedded programming... Go language leaves you heaps of shits, but Oberon allows you to stack a deck of cards. The big problem with Oberon is CAPS LOCK IS UGLY and the reserved words could be more terse (PROCEDURE could be shortened to "PROC" or "pro". Oberon programmers are hypocrites when they use VAR, instead of VARIABLE. So if they use VAR, why not use PROC instead of PROCEDURE? Because they are hypocrites. So someone could download oberon and make it usable! Wirth will never be convinced since he's stuck in academic obscurity and does not seem to interact with any developers whatsoever on any mailing lists or usenet - out of site, out of mind.

GO IS SHIT BABY GARBAGE

GO IS SHIT BABY GARBAGE

There is also some cricism of Golang here:

http://nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/

Note that his criticism, could also be criticized too. Cricitism is not immune to criticism of criticism.

http://www.globalnerdy.com/wordpress/wp-content/uploads/2014/06/poopy-swift-code-example.jpg

"Swift is a new programming language for iOS and OS X apps "

Locks you into buying only apple products - Apple is trying to control you - like in 1984 where people worship APPLE COMPUTER, remember? Or did they.

I've also included some comparisons to both Rust and Haskell (which I consider to be good languages)

Says it all really

>>130
SWIFT IS SHIT BABY GARBAGE

using a closed source language

Cuck

>>133
Languages can't be closed source. For the simple reason that they are not programs.

How much is Mozzarella paying this yager.io fella to shill for Rust.

>>110

Rob Pike in his pdf file says

"Linux may fall into the Macintosh trap: smug isolation leading
to (near) obsolescence."

iPad is obsolete. iPhone obsolete.

>>133,135
Back to /g/, mental midgets.

I believe in Go supremacy.