One argument that I’m missing in the article is that with an enumerated, states are mutually exclusive, while withseveral booleans, there could be some limbo state of several bool columns with value true, e.g. is_guest and is_admin, which is an invalid state.
In that case, you set the enumeration up to use separate bit flags for each boolean, e.g., is_guest is the least significant bit, is_admin is the second least significant bit, etc. Of course, then you've still got a bunch of booleans that you need to test individually, but at least they're in the same column.
I guess it depends. There are items for which there's just no margin for cutting quality. Take for example a Hermes bag. While some buyers would probably settle for less quality, the brand depends on the image of a high quality product, thus the bags have increased in price by 5%+x annually for the past 20 years. That's a rate which is unsustainable for non-luxury items.
Another example is Miele washing machines, which most likely deserve to be considered top notch and high quality. The prices have barely increased in the same timespan, which technically means they are 25%-30% less expensive after inflation. It's hard to imagine that the production process was improved by that much.
If you come from verbosity land C# release notes are magically good as well, always some way to reduce boilerplate while maintaining "implicit verbosity" which your proprietary LSP resolves 100% correctly.
I'd prefer writing C# if I had the Linux interaction libs Python has. I'm too dumb to write syscall wrappers
Modula-3 should be on that list as well.
Unfortunately pretty dead (compiler support is rather abysmal), though pretty influential. Wikipedia lists a couple of languages that it influenced, I think it should also include Go (though Go is allegedly influenced by Modula-2, according to its wikipedia article)
Yes, POWER is an acronym for Power Optimization With Enhanced RISC.
There are some wild instructions like cntlzd and lwarx that are more CISC-esque, and everybody’s favorite instruction (by name), eieio
Obscure data point of the day; McDonalds is a small but long-standing real estate company in a provincial city in New Zealand. Their website address? eieio.co.nz
Unless you're making it possible to access memory on every instruction that takes an argument, or adding more addressing modes that are redundant with ALU operations, or making registers that can only be used for one purpose, etc., it's not really turning into CISC. The acronyms are misnomers, or maybe you just need to think of what's being "reduced" as the number of micro-ops per high-level instruction. Regardless, you don't turn RISC into CISC just by adding more instructions.
reply