The marginal extra disk spaces used by flatpak really isn’t a concern for most users, much less valve. If you do everything in flatpak and your apps only use current runtime versions, the additional space used by flatpak is in the megabytes, since libraries like libc are going to be on your host no matter what.
You can still freely use / in branch names. Having remote branches available as remote/branch is just a convenience, and you can delete or modify them locally. It’s common to use / in branch names, too.
Owning a current gen Apple TV, there really isn’t that much more to shrink before it is in the stick format.
I started Adderall XR several months ago. My experience during the first week was that I was superhuman and could actually get things done. The first day I think I experienced the euphoria that I presume recreational users go for, but never since. After about a month it wasn’t doing much for me, psychiatrist adjusted the dosage, and it’s been decent ever since. Some days I can really feel it working, other days not so much. I mostly work from home (software dev) so I have a pretty strong control over my environment, but despite that I haven’t been able to figure out what might cause (or even influence) good days and bad days with stimulants. I would encourage you to keep meeting with your psychiatrist, there are like a dozen different medications and maybe this one just isn’t yours. Besides, you’ve arguably the hardest part by getting that first appointment. Best of luck!
Not necessarily. If you trust the code running on your device then there is no backdoor they could install on a server that would break e2ee. They would have to backdoor the client where the keys are.
What do you have against pages and numbers
I wouldn’t be surprised if the amount of power drawn overnight when a processor is in sleep mode ends up being less than the power it takes to boot the device.
Well I’m sorry that you got shitty responses like that. Which platform(s) was this on?
You’ll see when you start your second project why this doesn’t work.
Can you be more specific? I’ve had nothing but great experiences from the rust community.
The magnet and the charging coil aren’t the same afaik. They’re located together since their functionality is linked, but ultimately they are separate.
When OS X was released, half the point was that they were now a compatible Unix system using interoperable standards.
If it’s anything like ChromeOS, it’ll be a VM where you can do whatever you want, within that VM.
Your default types for that are i32 or u32. It’s the exact same number of characters yet encodes more precise information.
I’m aware of packing, but for my specific niche the main bottleneck is CPU, and it’s important to minimize the amount of memory usage to improve data locality, increasing cache hit rates, ultimately increasing cpu throughout. Any gains we would make by packing such small values would likely be eliminated by the cost of unpacking them, unless it’s a flags-like value where we are primarily comparing individual bits.
I’ll be honest if that’s your complaint, I have a hard time believing you would find the equivalent C or C++ code to be better.
Cargo being an all-in-one tool is actually one of my favorite things about the rust ecosystem. It’s many things, and it does it all seamlessly.
Regarding comparing to C or C++, how can you argue either is designed better? C, while standing the test of time, predates so many modern programming concepts or standards and writing C code is extremely error prone. C++ improves on many of C’s shortfalls, but it wasn’t designed. It’s the result of different things being loosely bolted on to C over the course of 30 years. And it’s still error prone, for example while there are smart pointers and other types that can make writing memory safe code possible, they’re not default and they aren’t always fully supported in the standard library, let alone anything else.
I do systems programming work, sometimes with constrained memory scenarios. We always want to use the smallest types we can for any task, and unless negative numbers are a necessary, always prefer unsigned. That means a lot of u8 and u16 unless we know a value is likely to need more bits to be represented. Probably doesn’t matter as much in we programming but that’s not Rust’s niche (or well not its original niche).
It does define minimum sizes for different types. An int for example is at least two bytes, whatever size those might be!
I don’t believe so, I think it is chrome and edge only (besides safari of course). You could still manually copy-paste the passwords but of course that’s not as convenient.
Depends on if you want your data format to be strict ascii. If you don’t care, then sure, why not?