bkkcanuck
About
- Username
- bkkcanuck
- Joined
- Visits
- 35
- Last Active
- Roles
- member
- Points
- 702
- Badges
- 1
- Posts
- 864
Reactions
-
Apple planning to ditch Intel chips in Macs for its own custom silicon in 2020
Soli said:cropr said:The moment we can no longer run an Intel based linux server in a VM on a Mac at a decent speed, will be the day that my company stops using Macs as development machines. This is an absolute showstopper. If we don't have this functionality locally on a development machine, all my developers will move to Intel machines with Linux (e.g. Dell XPS).) The only people that will have to have an idea of the different internals will be those running VMs.
-
Apple planning to ditch Intel chips in Macs for its own custom silicon in 2020
kpom said:Interesting. I didn’t expect that so soon. Windows on ARM emulates 32-bit x86 but not x64. With Apple’s push on 64-bit I wonder if they plan to emulate x64. -
Google faces $9 billion in damages after ripping off Java in Android
The EFF said it better than I have:
https://www.eff.org/deeplinks/2018/03/federal-circuit-continues-screw-copyright-law-and-thwart-innovation
-
Google faces $9 billion in damages after ripping off Java in Android
melgross said:techrules said:This ruling is a lot bigger then this situation. If APIs can now be copyrighted the entire industry will change dramatically. We have copied APIs for decades and it is vital for the tech world we have today. Heck, Oracle themselves abuse this ruling and re-use APIs.
so an OS company needs to allow access to developers for the purpose of writing software for their OS. That makes a lot of sense. We also saw Microsoft abuse that in the late 1980’s and early 1990’s after Windows 3.1 came out, by keeping “secret: apl’s For their own software, mostly Office, while denying the necessary apli’s to their competitions for the purpose of hooking their software in properly. The court struck what Microsoft was doing Dow.
interestingly, the court didn’t make it clear as to whether Microsoft needed to share their secret apli’s with other developers, on,t that they needed to have a Chinese” wall between their systems development, and their client software development.
some developers are getting all out of whack over this decision, and I’m not sure they’re correct in it. If Google did get the license their engineers said they needed to, and used it correctly, they wouldn’t be in this position now. But they didn’t. Instead, they almost gutted Java, and wrote a lot of their own code, giving it their own name. If they had licensed Java, they wouldn’t ha ve been allowed to do that. Microsoft got into the same trouble over that. They did license Java, and then proceeded to come out with Java For Windows - a clear violation of the license. They were sued, and the courts slapped them down.
google seemed to think that if they didn’t take out a license, they could mangle the code any way they wanted to. I predicted when this first came out that in the end, Google would lose this.
as or API’s this case isn’t just about API’s. Those who think it is don’t know the case very well. While appi’s Are an issue, they aren’t the only one. The neglect to take out a license is the main issue.
but I don’t see how the API issue is so much of a problem. What I see is Google appropriating the APIs for their own use is an issue in that they are attempting to substantially reproduce what amounts to an OS. But this isn’t going to affect developers of software to sit on that OS. So while it’s s problem, it isn’t the overriding one that some people think.
As far as the amount of work to produce an OS with java APIs or developing an equivalent platform with different APIs.... is not a big gap. The gap was in the 3rd party support for the development of applications. Google by using java as the development platform, then translating it into their own platform did not have the chicken and the egg situation where you cannot get developers to develop for it because of the lack of tools, the lack of market etc. The actual VM implementation is a very very small part of the overall picture. As such the use of the APIs were actually for the purposes of compatibility. Microsoft got into trouble over java because they licensed java (which entails a specific specification) then implemented something different than the standard and continuing to call it java (which is likely trademarked).
-
Google faces $9 billion in damages after ripping off Java in Android
gatorguy said:radarthekat said:gatorguy said:radarthekat said:gatorguy said:radarthekat said:gatorguy said:The argument Google was making in this latest appeal was pretty thin, since they were relying in part on arguing "interoperability" being a rationale. In actual practice there was limited interoperability. I expected they'd lose this particular court case, but do not expect monetary damages from a follow-up retrial anywhere near the $9B that Ellison would like. He couldn't have expected that level of profit when he bought Sun years after Google introduced Android anyway which is why Sun sold so cheap.
So in reality Ellison suffered no loss due to Google not licensing Java from the previous owner. It's really not all that different from a patent troll buying up a couple of unused patents for a hundred bucks and then using a claim from one of them to sue Apple for stealing from them for use in Siri or something and demanding $Millions for the harm.
As for "stolen Java" the way that Google used it was more like copying chapter names and then writing the original book that filled the rest of the 1000 pages as I've understood it. If accurate it hardly seems like a stolen product, more like a handful of bolts scooped up.
What Oracle has done with Java since they bought it (well after Android was on the market) has sent it far downhill in my view. First they started bundling trashy and near impossible to rid ASK malware in with their automatic Java updates to slip it past consumers, then trying to force McAfee subscription virus software on those same consumers by using the same sneaky method, and then Yahoo snatching your browser and who knows what other software packages that many folks didn't even know was being installed too. That they escaped being sued for it is only because of technicalities IMO. It's still despicable conduct.
https://www.infoworld.com/article/2613298/java/java-scam--how-oracle-and-ask-profit-from-sneaky-add-ons.html
https://www.techlicious.com/blog/java-yahoo-browser-search-settings-hijacking/
Even the Oracle Java software as a whole has become more problematic security-wise and far less trustworthy, to the point that a great number of folks won't get anywhere near it given the choice, and professional advice is to rid your computer's of it.
So I don't weep for an Ellison-led Oracle who wants to claim they've lost profit on Java because of Google. They're not seeing the profits they could due to their own uncaring attitude towards it, and destroying it's reputation further with their sneak malware installs seemingly driven by a personal vendetta pursued by Larry Ellison and his Ask search bar and Yahoo browser replacement hoping to cause harm to Google but hurting computer users to do so. He evidently does not care about any collateral damage as long as he gets what he wants.
He paid little for Sun because it wasn't worth much. He was hoping he could discover hidden gold there and with his $B's it was a only a blip on the financials. Ellison didn't want Sun's Java because he thought he could make it better IMO. He was buying a lotto ticket that could be tossed away without much loss if it didn't pan out.
”It's still despicable conduct.”
i moted that you reserve that sentiment for Oracle but don’t apply it to Google, which willfully stole technology from Oracle and the whole damn interface and user interaction
model from Apple. What would Google need to do to earn a despicable badge? Mine people for data to sell to advertisers? Would that do it?
..and if Google mined people for your personal data to sell to ANYONE I'd call that out as despicable too. They don't so you're arguing a moot point.