9/25/2023 0 Comments Review reactosAnd Oracle's infringement angle now disappears completely. Sun's platform still starts off where it was the whole time, in the gutter, and in that vacuum, Android becomes a thing, with incompatible APIs and all. So reset from the beginning, bypass the Harmony detour, and everything still plays out exactly the same. That difference does not suddenly force the hand of Google-or anyone-to keep dragging around Oracle/Sun's failed attempt at a mobile platform and maintaining compatibility with it. All the incompatibilities of Android? There's nothing that keeps the same breaking changes from being made in our hypothetical world where Android used the blessed license instead of the one from their preferred implementation. Which means no one actually ever needed to get Sun or Oracle's permission to do anything. It uses a different open source license, but it's open source nonetheless. And it's been open source the whole time. They (you) all complain about Android ripping off Java (to the tune of a multi-billion dollar copyright infringement lawsuit), but invariably the argument comes around to the real thing that's bothering them and which they try to wrap up in a bunch of claims about infringement-and what's actually got everyone (besides the money grubbers) fuming is the intentional incompatibility-in other words, that Android didn't copy enough! You wanna try squaring that circle? Which brings us to another another thing.Īndroid today is now based on the "proper" codebase, as mentioned above. That includes Gosling + the subset of the Sun/Oracle fan club who sat on the stand during trial + and the perennial commenters who parrot the same talking points on Hacker News. People who complain about Google's use of the Java APIs can't seem to get their arguments straight. You responded to a question that wasn't answered by talking about being unable to undo the past-which only makes sense if they had been pressing you for an answer to what would happen if Google called it a wrap on Android today, but that wasn't the question. Harmony was dropped years ago, and Android has been rebased onto Oracle's own anointed, conflict-free codebase.Īnd you dodged the previous question where the commenter was asking for an honest assessment of mobile Java. > If the Supreme Court rules for Oracle, Android is copyright-infringing Google spent a lot of time arguing for, and would be perfectly fine with, a simple remand based on the Federal Circuit's standard of review of the jury's fair use verdict. The temptation from the outside looking in is to think/hope/dread that the court will just resolve these questions once and for all, but they often prefer to resolve cases on narrower grounds, where available. The sense of how much Android actually "mattered" in this sense goes right to the "effect on the market" prong.Īs for the broader case, both the copyrightability and fair use claims have been presented to the Supreme Court here. My position is that it doesn't really change things all that much, with losses by Android probably mostly picked up by Apple or Symbian or webOS or Windows Phone but the trajectory to smartphones and away from J2ME stuff largely the same. The team will expect you to know all this before they help you and it will make your life easier.I don't mean "if you take away Android today would Java succeed on mobile?", I mean "if you retrospectively imagine Android never existed at all (or used a different language), how does Java do?" You are new to ReactOS ? Read this in full before asking any questions - it may assist you now and it may help to answer some of your future questions - ĭo read the whole thing, it will assist you with some basic answers to normal questions that are asked often. This knowledge I purport to have, is quite out of date so might require you to do so some research for yourself - this was the state of GDI+ APIs in Wine as of 2008 but I have seen no more recent update since. I believe ReactOS gets the majority of its GDI code from Wine and I understand that Wine translates the GDI+ calls to GDI methods, a process that might differ somewhat from how Microsoft implemented GDI+. I plan to test GDI+ myself in the next few weeks. I have had some luck in placing some graphics on the screen but regular GDI+ updates failed to re-render. With regard to GDI+ I would expect your application to fail to render properly, if it renders at all - but still worth testing to find out. Then if it works, feel happy and report back. Basically, nothing works in ReactOS, assume that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |