3,563 karma · joined March 17, 2011
This sound impressive until you get to the part where reads are destructive, and reads heavily outweigh writes in most workloads. Sounds like a pretty significant disadvantage.
Pay your employees.
I think there's a vocal segment of the Linux community that doesn't understand what a major roadblock it is for the general user having different distributions having completely different ways of packaging, distributing, and updating applications. Don't worry, no one's taking away your apt-get, pacman, rpm, eopkg, makefiles, etc.
/s
If I could slap macOS on a Matebook X Pro, I'd switch tomorrow.
$8,379.00
For a Macbook.
- A $2400 entry price for a quad-core 13" Macbook Pro. - Minimum $3675 spend for a Macbook with 32GB of memory (and still only comes with 256GB of storage). - Non-touchbar Macbook Pro stagnating with 7th-gen dual-core at the same exact price.
Looks like I'll be holding on to my 2014 model like grim death.
Things will get even better once zstd is added[1]. Leaving transparent compression out of APFS was a real big mistake by Apple, imho, given how fast and cheap lz4 and zstd are. It's one of the reasons why I have a ZFS volume set aside myself.
[1] https://www.phoronix.com/scan.php?page=news_item&px=OpenZFS-...
*(volatile std::uint32_t*)reg_name = val;
And the author's solution is to replace that one line with this: struct DeviceSetup {
enum class TableType : std::uint32_t {
inphase = 0,
quadrature,
table
};
std::uint32_t input_source : 8;
TableType table_type : 4;
std::uint32_t reserved : 20;
};
volatile auto device_registers_ptr = reinterpret_cast<DeviceSetup*>(DeviceControlAddress);
I'm not really seeing the readability and maintainability advantages here.