@kragen You'd likely have to undermine their business model.
On the positive side, this is a dynamic which can be used to play megacorps (and possibly other interests) off one another.
That notion goes back to IBM's Earthquake Memo, ~1998.
I'm not sure if you were at the LinuxWorld Expo where copies of that were being shown around, probably 1999, NYC.
Tim O'Reilly wrote on that in Open Sources.
@dredmorbius @zardoz @kick @enkiv2 @freakazoid I think it goes back longer than that; IIRC Gumby commented on the fsb list in the mid-1990s that he wasn't worried about other companies contributing code to GCC and GDB because Cygnus could then turn around and sell the improved versions to Cygnus's customers. Of course those customers could get the software without paying, but they found Cygnus's offering valuable enough to pay for, and competitors' contributions just increased that value.
@dredmorbius @zardoz @kick @enkiv2 @freakazoid the big insight Tim had, which took the rest of us a while to appreciate, was how this gave new market power to companies that own piles of data, like Google or the ACM or Knight Capital. And now we have AWS and Azure and Samsung capturing a big part of the value from free software instead.
@kragen Weinsteinomics 101: Monopoly is fundamentally a control dynamic, not a marketshare proposition
...Harvey Weinstein and the Economics of Consent by Brit Marling is one of the more significant economics articles of the past decade, though I'm not sure Ms. Marling recognises this. In it, she clearly articulates the dynamics of power, and re-establishes the element of control so critical to understanding monopoly...
@kick @zardoz @enkiv2 @dredmorbius @stman @freakazoid he's not a parody, I think, just young and struggling to figure out how to navigate a legitimately very complicated political landscape. I wish I could tell you how many of my friends have committed suicide, been interrogated by grand juries, been betrayed by those they trusted most, etc. It's a situation that's difficult for even the best grounded and most experienced.
longer between hardware (Integrated circuits architectures, motherboards or digital electronic system architectures), software (Including kernel, OS, applications), protocols (Either for networks or embedded motherboard protocols like USB, PCIe), and networks (including motherboard PCB routing) physical topologies and architecture.
Blowing away the artificial borders or boundaries between all these currently separated scientific
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!