You may, but if you read the link, you’ll find it consistent with the second law of thermodynamics despite being clever about it. The demonstration of consistency requires a modern understanding of information theory, but it’s been long realized it’s likely not a real “out.”
This is true and I don’t know why it’s downvoted. IBM was notoriously obsessed with lock-in, they just bungled it with the IBM PC because they needed to move fast because they didn’t want it to slip away from them. So, they used off the shelf components that anyone else could buy.
The lenient contract with Microsoft and the unexpected to them ruling on reverse engineering the BIOS sealed their fate.
But no company wants to compete in a commodity, they all want to be monopolies. All the Unix vendors tried to be common enough to be a selling point but idiosyncratic enough to lock in their clients.
Apple isn’t nefarious… they are the default.
Now, if we want to support their ambitions with our wallets is another question
That's not true, well the second part is not true. it's not the default, it's a choice they made, there is no default.
They could have opted for maximum interoperability and openess.
Sk Hynix does not work with only sk hynix motherboards(I don't know if they even make motherboards), Intel cpus do not only work with Intel NICs. AMD GPUs do not only work with AMD CPUs. Nvidia GPUs do not require an imaginary Nvidia OS.
Hell windows is happy to work with whatever hardware you throw at it, but Macs nowadays have soldered ram and storage. And you can't install MacOS on any hardware you might like.
Getting files in or out of an iPhone without a Mac was a nightmare just a few years ago and I am confident it still is.
The default the GP is probably referencing is the early days all hardware vendors produced their own OS. Apple maintained the status quo as MS changed the status quo. The innovation MS really developed was the software license for OS's.
Nefarious and default aren't incompatible properties. If companies (especially large, public ones) were benevolent by default, a lot of laws and institutions would not be needed anymore.
It's downvoted because it reads as though IBM made a mistake the commenter thinks they should've never made, as opposed to a mistake from IBMs perspective given their business strategy at the time.
That is, it appears to tacitly agree with, and chide IBM for failing to defended, closed, walled-garden ecosystems.
That's certainly not what it seems they meant. It's just how one might initially read it and downvote.
It was certainly a mistake to base the original IBM PC hardware design in easily obtained electronics, and hope the BIOS copyright would be enough to hold out clones, unlike previous IBM hardware.
But it's not their mistake at all there is nothing they could do, companies went out there and reversed engineered BIOS. They couldn't possibly stop them.
I see the same thing in Russia. It seems like there is no such thing as a civilian target because getting your opponents citizens to uprise and while yours to support you is the key strategy now.
Except i think the American heart and minds campaign in Vietnam was lip service to a campaign that was measured by body count, and dead non combatants can’t litigate their combat status, so McNamara was befuddled the USA was “winning” and losing every square inch where there were not American soldiers in force. That there was no equivalent to insurgent Viet Cong embedded in North Vietnam says everything.
Not if you’re in a different domain, then it cannot be claimed to confuse customers.
So if it’s a network router or a woodworking router, then you’re good.
I can sells of red socks, and white socks, without getting sued by Chicago or Boston.
If it’s in the same space… you might want to contact a lawyer. I believe Firefox had conflicts with earlier names like Phoenix and FireBird and they weren’t even browsers.
How are you still blaming this on “the government”? Is your thesis that the business world would be delivering high quality products and experiences if only those damned bureaucrats would get out of the way? What possible evidence do you have left for that hypothesis at this point?
EDIT: this was a misread on my part, retracted, carry on.
He isn't blaming the software problem on the government. He is saying that if we apply this reasoning to everything in our lives, then we have a race to the bottom in other facets, of which one is government.
He is saying "if we apply (or are applying) the same business mentality to government, we will get literally the worst government we are willing to tolerate based on money"
It's not blaming. It's an explanation for probably why things can go wrong.
> I'm real curious why lightning never became the standard.
Because it is bad. In any connection there are springs that keep the tension, which will eventually wear out. They can either be on the cheap replaceable cable, or in the receptacle that is hardwired into your expensive device.
> Why Micro types offer better durability? Accomplished by moving leaf-spring from the PCB receptacle to plug, the most-stressed part is now on the cable side of the connection. Inexpensive cable bears most wear instead of the µUSB device.
Definitely had an iPhone where the port was worn out and getting it to connect was difficult.
What I want from a version system is to capture event in history not like changes as a files but as events that capture a process.
If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes. I wish commits could be folded into larger commits so that you can still capture the individual changes but also not see them by default when looking at the history of a file.
Just a more human centric perspective on change history where it captures the way we talk and think about changes.
"I wish commits could be folded into larger commits so that you can still capture the individual changes but also not see them by default when looking at the history of a file."
Fossil merges do this. More people need to use Fossil; it's got a ton of great ideas.
"If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes."
Now this is a good idea that I've never seen in a VCS.
> "If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes."
>
> Now this is a good idea that I've never seen in a VCS.
There's a reason no one has done that, the VCS would have to have a semantic understanding of what it's tracking. I'm sure that's possible, but I think would see extremely limited success. Honestly, it may have even been done for proprietary languages and VCS systems that have since faded into obscurity.
I'd settle for searching the git history for a particular regex/string and then running a blame on that.
1) An “easy” way to implement this would be to treat the original file as the parent to both files. You can add a new command “split” if needed to mark the new file as a fork of the existing file.
2) language sensitive version control seems like the next thing. We need like an LSP for VCSes.
If I run blame on the new file the will I see the commits made by the original writers? Will it find the same code if it was written independently? It’s not about find copies it about recording changes to a code base as an artifact and not to files. The closest git has is limited rename support.
https://en.wikipedia.org/wiki/Maxwell%27s_demon
reply