It's amazing if you consider how differently this sort of acquisition would have been viewed, way back during the SCO v. IBM [0] era.
[0] https://en.wikipedia.org/wiki/SCO_Group,_Inc._v._Internation....
591–600 of 1001 posts
It's amazing if you consider how differently this sort of acquisition would have been viewed, way back during the SCO v. IBM [0] era.
[0] https://en.wikipedia.org/wiki/SCO_Group,_Inc._v._Internation....
Earlier quoted context omitted.
Is openshift really open source? I was under the impression that nobody really runs origin on its own since it's far too hard. It seemed more like they just wanted to point out but it's open source, but you need support and a lot of know-how to actually use it.
I run Origin for my employer. It's pretty easy these days since you can do all of it with openshift-ansible and other related tools. I know there are plenty of others like that, as well.
Earlier quoted context omitted.
All major tech companies file patents - shouldn't be surprising that it's going to be part of the job.
Not just tech companies. I work at a bank and we've filed a bunch of software/algorithm/tech patents.
The patent system is broken.
Earlier quoted context omitted.
In my opinion: Either invest in developing hacker news support for updated news comment threads better (my recommendation is to split each thread by the original article/time in a megathread and use the newest title for the base merged thread and sort the sub-threads by time or stop merging these threads because it makes it so freaking confusing as the comments are based on totally different contexts and yet they are…
This happens whenever a story is changing rapidly. It doesn't have to do with merging the threads—it has to do with different comments dating from when different information was available. In this case the initial story was "might acquire" and then turned into "has acquired". The threads weren't neatly partitioned before we merged them; people just post to whichever discussion they happen to see. When a story has bee…
Earlier quoted context omitted.
This happens whenever a story is changing rapidly. It doesn't have to do with merging the threads—it has to do with different comments dating from when different information was available. In this case the initial story was "might acquire" and then turned into "has acquired". The threads weren't neatly partitioned before we merged them; people just post to whichever discussion they happen to see. When a story has bee…
The threads were neatly partitioned because they were all based on an initial source of information (the source article), but it was then merged into one mega-thread contained conflicting sources and thus it makes it confusing since all the comments which were based on different sources are now intermingled.
[0]: https://blog.ycombinator.com/ycs-essential-startup-advice/
RH maybe the only one that's worth of purchasing and IBM can afford.