|
|
What was the problem with unloading Symphony on consulting support based upon LibreOffice? Given that this is a business they want to be rid of, I would expect they would not need to bolt proprietary stuff on to it any longer.
Regarding MariaDB support, I think you're correct that they're treating it as a competitor. This wasn't really the case for MySQL. IBM provided a supported version of MySQL.
IBM is most visible around Apache OpenOffice. What they are doing around MySQL v. MariaDB is tacit support through inaction. They didn't turn to supporting MariaDB or another MySQL version when Oracle de-supported MySQL on IBM platforms. They did something similar during Oracle v. Google - they chose just that time to abandon the Harmony project and commit to Oracle's JDK.
Your memory of IBM differs from my own.
I can't say I've had that much to do with them. HP, on the other hand, I could rant about for a while...
If they own the copyright, they are free to relicense a piece of data
Sorry to be pedantic, but replace "a piece of data" with "a work of authorship". If there isn't the creative work of a human being involved, it's not copyrightable. And then we get to this:
17 CFR 102(b) In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.
And that means that even when the hand of man is involved, a lot of things are still not copyrightable.
Wasn't acquiring MySQL probably intended to eliminate a large portion of the competition anyway?
If I remember correctly, Sun acquired MySQL prior to being acquired by Oracle, and Oracle's reasons for buying Sun had nothing to do with MySQL. Somebody correct me if I'm mistaken!
Let's look at what Oracle is doing. I'll start the list of moves that appear to be intended to alienate the community around the very software they're promoting and cause the Open Source community to create viable forks that end up absconding with the product and its market. You guys contribute additional examples...
IBM isn't known for dumb moves, but partnering with Oracle on this sure is one.
Bruce
NSA Trigger Words for PRISM:
This is an (admittedly huge) list of words that supposedly cause the NSA to flag you as a potential terrorist if you over-use them in an email.
We found this on Reddit, where James Bamford, a veteran reporter with 30 years experience covering the NSA, is answering questions from the community. This list comes from Reddit user GloriousDawn, who found it on Attrition.org, a site that very closely follows the security industry.
Yes, when you buy stock, the money goes to the -previous- owner of that part of the company.
But long-term stock-ownership is still influenced mostly by the performance of the actual company, whereas that's entirely irrelevant for HFT. Apple is valuable today, compared to 20 years ago because they as a company grew in every way over those 20 years.
From todays discussion it seems likely that the NSA stores not only all of the above, but the actual call-content too. Just saying.
Not that it detracts from any of what you say.
Compared to asking each person to self-identify, which has a success rate of 100.000%.
Not if the whole reason for recording your gender in a database has to do with other people identifying you. If you self-identify as female but I think you look like a guy in a dress, that may not qualify as a success.
Also I'm not sure what those cages around the fan blades are suppose to acheive since the cage gap is huge, anything could be sucked in there, needs to be a cage more like a desktop fan.
I presume the cages are sized to keep body parts out.
Unfortunately the laws of physics seriously don't like your suggestion of tighter cages. At low air speeds and with abundant power available you can use tight cages no problem. But when you're at high air velocities to get substantial thrust and where power efficiency is crucial, any obstruction in the air stream is a serious issue. Aerodynamic drag is proportional to velocity squared. When you multiply air speed by ten, the drag caused by each cage wire is multiplied by a hundred. This means thrust loss, as well as draining the batteries trying to compensate for lost thrust. Adding batteries to compensate for the extra power drain increases your weight. Increased weight means you need to compensate with that much more thrust, which in turn means more weight and more power drain. It is a problem that compounds upon itself. You need the cage wires to be as thin and sparse as as you can get away with, short of inviting serious accidental injury.
-
You need the permission of the author to make copies, but there most certainly are implicit permissions.
Write a blog-post, put it on a website with no mention of any licence, and you have just given me implicit permission to download the post (creating intermediare copies in RAM and possibly in disk-cache).
The only thing worse than X Windows: (X Windows) - X