News for hackers. Stuff that matters.
Re:A binary coder for Swift by invokestatic on Saturday July 29, 2017 @12:25PM (#14881893)
Most network protocols, including TCP and UDP, are big endian, so little endian really isn't that ubiquitous. And I imagine a big use case for the binary coder will be for networking.
Re:A binary coder for Swift by userbinator on Saturday July 29, 2017 @01:11PM (#14882100)
TCP/UDP/IP are BE, but that's largely an artifact of the time they were invented (when the LE/BE split was more even), hence networking hardware is probably where BE is still commonplace.

Most application protocols I've worked with are LE; serialisations like Avro, BSON, capnproto, protobufs, etc. come to mind, as well as numerous other proprietary ones. ASN.1 is a notable exception, but it's also much older.

Re:A binary coder for Swift by unkown-unknowns on Saturday July 29, 2017 @01:07PM (#14882082)
But even though the protocols are big endian, is it generally the case that you always make the data itself big endian? (Asking out of ignorance, not rhetorically or sarcastically.)
Re:A binary coder for Swift by nemo1618 on Saturday July 29, 2017 @01:30PM (#14882178)
It's up to the programmer. In the systems I've worked on, we always sent the data itself in little endian.