Worked for me; I can see it fine
Just note that if you 3D print something, if you use the wrong material, there’s a chance it may melt.
What a load of crap. I knew Netflix was expensive, but ten bucks a month per person with ads? That’s unreal! Even bundling only gets that down to ~$7, which is still BS.
~$2500USD/ea, for anyone else as curious as me
Out of curiosity, what’s wrong with medium? (Serious question)
@[email protected] - are these available somewhere as full res pictures already? And/or will they be after the desktop is chosen? Or will only the chosen one be available?
Yep. Broadcom fucking sucks, they’re and they’re really good at doing this. Can’t wait until VMWare costs more than the systems it’ll be running on 🙄
Must be part of Reddit’s new rebrand
Although if y’all sold a stuffed animal of whatever adorable thing is in the middle right picture, I’d buy it in a heartbeat
Top left gives me amazing vibes
Redwoods are so freakin’ cool.
That is all!
So for padding, it sometimes depends on how your compiler works, but usually, it doesn’t pack bytes by default - that needs to manually be done. Otherwise, a uint32 followed by 2 uint16s, for example, will take up the space for 3 uint32s (in a 32-bit native compiler). If you manually specify packing (implemented differently depending on your compiler and such), then it will pack those all properly into just 2 uint32s.
I do imagine 24 bits followed by 16 more in a bit field for a 32-bit number would potentially cause problems. But it’s late here and I could certainly be wrong so take that with a grain of salt.
That also said, I typically don’t use bitfields directly in structures - it’s not usually good practice, at least where I work. I’d either do a uint8[3] or use a whole uint32 that is a union, and in the union would be your :24 followed by a reserved : 8, if that makes any sense. It’s sometimes worth it to leave a few extra bytes in there just from an organization standpoint.