5,600 karma · joined October 12, 2019
The ruling comes 17 years after Fender was famously unsuccessful in its attempts to make its Stratocaster, Telecaster and Precision guitar body shapes a trademark in the US, decades after the designs were first produced.
That litigation process lasted five years, and demonstrated that countless companies had used the body shapes that Fender had sought to trademark. In the end, the courts ruled that the Stratocaster shape was “so common that it is depicted as a generic electric guitar in a dictionary”.
The state of Pennsylvania is 13 million; would MSFT losing PA do them serious financial damage?
If you have a lot of farmland in a red state and the profits are reported in a blue state, then counting the reported profits on the corporate balance sheet will give a distorted picture of what is happening.
Look at e.g. General Mills, based in a blue state, but a great deal of what they buy are ag inputs from red states.
I like OpenVMS and am slowly learning more about it; no reason to wait until you see those hit eBay :-)
Did he feel the language design was bad, or would having TTF fonts being able to show "rho", "iota", "grade up" have removed one or more of his objections?
It’s a huge mistake at the level of IBM trying to reestablish dominance over PCs by making MicroChannel the new standard; this failed horribly and cost IBM its market leadership and reputation.
MCA was technically better at the time, but the industry responded with EISA and VLBus which led to PCI and today’s PCIe.
When I was working for a Unix commercial graphics software company, the CTO told me how bad the information he received under ATI’s NDA was: different revisions of the same chipset had contradictory register settings, so the driver had to identify the revision before writing a value to the write-only configuration registers. The same chipset might need a 0 or a 1; writing the wrong values could crash the driver.
More accurately, “the assembly language programmer Tim Paterson has always claimed that he did not look at the implementation”.
That Kildall later decided that turnabout is fair play, is not that surprising…
However my point is that now, everyone can assess the source code for themselves.
So unless I want to dig into their YAML files that are not documented…
The needed tweaks, the ability to customize things, basically goes to zero because the support staff is technical about the software, but NOT about Kubernetes.
I am not joking: a recent deployment required 3x VMs for Kubernetes, each VM having 256 gigabytes of RAM; then a separate 3x VMs for a different piece. 1.5TB of RAM to manage less than 1200 network devices (routers etc. that run BGP).
No one knew, for instance, how to lower the MongoDB (because of course you need it!) resource usage, despite the fact that the clustered VMware install is using a very fast SSD storage solution and thus MongoDB is unlikely accelerate anything; so over 128GB RAM is being burned on caching the results coming back from SSDs that are running at many-GB/s throughput.