Readit NewsOnce the circumstances change, we'll have to adapt.
You don't have to live far out of town to have no town water. The pipes don't go far out of city/town limits at all.
You always get periods of prolonged drought even in otherwise perfectly reasonable self-sustainable properties.
This isn't some "HAHAHA suck it libertarians" attitude. This is a "anyone who lives slightly outside of town wanting to buy water and being told no" type of situation.
What I have a negative attitude towards is developing housing in an area of the arid western US without access to water. Water rights (the right to buy water) has controlled development here since before statehood. It's very simple: you don't develop without water rights, it's irresponsible and puts an unfair social burden on others.
Not every part of the continent should be covered with homes.
This was about some people on the waterboard not being able to manage angry - semi-aggressive- people properly.
And now those people can irrigate their lawns while others can't even drink, wash or cook.
But the board handled the situation very poorly. The job of being on a board like this is often to sit patiently while people complain and perhaps yell. Try to keep things calm and moving along, let everyone make their statement.
They should have just accepted the feedback and then scheduled discussion on various options for some future meeting, with a final vote even further out.
Both have a price in the American west, and they did not pay the latter price.
* Apple has had decades optimizing its software and hardware stacks to the demands of its majority users, whereas Intel and AMD have to optimize for a much broader scope of use cases.
* Apple was willing to throw out legacy support on a regular basis. Intel and AMD, by comparison, are still expected to run code written for DOS or specific extensions in major Enterprises, which adds to complexity and cost
* The “standard” of x86 (and demand for newly-bolted-on extensions) means effort into optimizations for efficiency or performance meet diminishing returns fairly quickly. The maturity of the platform also means the “easy” gains are long gone/already done, and so it’s a matter of edge cases and smaller tweaks rather than comprehensive redesigns.
* Software in x86 world is not optimized, broadly, because it doesn’t have to be. The demoscene shows what can be achieved in tight performance envelopes, but software companies have never had reason to optimize code or performance when next year has always promised more cores or more GHz.
It boils down to comparing two different products and asking why they can’t be the same. Apple’s hardware is purpose-built for its userbase, operating systems, and software; x86 is not, and never has been. Those of us who remember the 80s and 90s of SPARC/POWER/Itanium/etc recall that specialty designs often performed better than generalist ones in their specialties, but lacked compatibility as a result.
The Apple ARM vs Intel/AMD x86 is the same thing.
Each time they had a pretty good emulation story to keep most stuff (certainly popular stuff) working through a multi-year transition period.
IMO, this is better then carrying around 40 years of cruft.