ITGuyLevi

I'm nearing two years into using it as my daily driver and I would 100% not want to go back. Graphene does everything I need.

I think my wife paid for that one, then I bought her the CD.

I haven't used it in the past few months, I'll definitely give it another try though.

Edit: Oh, yeah this is a bit different. I like the new prompt asking if it's extended or desktop. I will definitely have to play with it a bit more, I had tossed it to the back of my brain as a 'well it exists' feature.

It works okay, but not great for me. I toss my phone on one of my old laptops docking station at work, but some apps like to force a shit resolution. It is pretty neat having them in moveable windows though.

In a normal byte format it wouldn't help, the byte standard breaks off bits into 8 bit chunks and calls them bytes (I'm not trying to explain basics, just putting it there for background), little-endian excels at using the least number of bits to express larger numbers in a stream. If you wanted to send any number from 0-255 you only need 1 byte, for 256-512 you need two bytes (or 16 bits), in little-endian it can be represented in just 9 bits, or up to 1024 in 10 bits, etc.

Doesn't matter for much to many people, but when the number gets big enough you can save a lot of bandwidth.

I think you missed the point, that I was making, albeit poorly (little endian still requires leading zeros when not transmitting in a byte format, otherwise you don't know if the first on signal is for 1, 256, 1024, etc.) it's all good though

I'm not seeing any trailing zeros if that is in little endian, you start little end first and it isn't limited to a silly 8-bits, it can be used to represent numbers far larger than 255 if continued (though then it wouldn't be representative of a byte and half the joke would be lost).

Little-endian for the win!

I usually just gather a nibble by picking up a couple crumbs... I'll see myself out.

Napping. Not everyone understands the fun that can be had.

I'm sure a successor will come around when room forms for them, I don't know of a reason any of the core *arr stack should need one. If you know of one don't hesitate to share, I'm just not really aware of any, they are awesome to me.

Odd way to phrase it, but I totally agree.

I would have been a bit more specific, but it applies to all of them (they aren't the reason I don't trust Google either).