4 ms·
I'm pretty sure the Mono people are worried. These patents are things that are fairly fundamental and important to any sort of mobile device that has competent
by KirinDave 16y ago
I'm pretty sure the Mono people are worried. These patents are things that are fairly fundamental and important to any sort of mobile device that has competent security.
- binaryfinery 16y agoNo I'm pretty sure they aren't. The CLR is totally different to the JVM.
- franksalim 16y agoI would say it is about as different as Dalvik is.
- binaryfinery 16y agoIn some ways the Dalvik VM is more different. Its register based for a start.
- recoil 16y agoGoogle aren't using the JVM either, they're using the Dalvik VM. The alleged patent infringement may apply to just about any VM implementation.
- binaryfinery 16y agoI know. I also hope they are using process level security, not class level security, which will completely bypass patent #1. Google people aren't stupid.
- KirinDave 16y agoRead. The. Claim. And no, the CLR is not totally different from the JVM.
- binaryfinery 16y agoYou've not looked at them have you (the VMs)? The JVM is entirely a class-focused JVM. The CLR is a general purpose VM. I can access arbitrary memory in the CLR, but cannot on the JVM. I write as someone who has attempted to build a byte-code assembly file that would allow direct manipulation of binary arrays for the purpose of efficiently loading OpenGL vertex buffers that mix floats and ints. Cant be done in Java or in Dalvik (at least in 2.1). Easily done in CLR. Also, the handling of security and exceptions is different. I've also read all the JSRs with respect to this problem, related problems, generics, stack-based variables etc, and I'm also aware of the optimizations for stack-based elimination in 1.6 and 1.7. Also, I admit I only read the first patent, but I believe it doesn't apply to Android simply because the Dalvik VM does not apply its security at the object level but the process level, thereby nuking the patent. As for mono, I doubt they would worry since they would simply point out that "class" and "object" have been used for determining security access since at least Windows NT. Or mono can simply turn off object level security and rely on the OS to do it. The whole list is replete with holes and workarounds.
- KirinDave 16y ago> You've not looked at them have you (the VMs)? I've looked at them, along with about half a dozen others. > The JVM is entirely a class-focused JVM. The CLR is a general purpose VM. ... blah-blah-non-sequitur-blah ... They are both VMs with similar overall strategies, similar technologies, and some distinct similarities. They're about as different as any two VMs are. > Also, I admit I only read the first patent, but I believe it doesn't apply to Android simply because the Dalvik VM does not apply its security at the object level but the process level, thereby nuking the patent. Unless they point out that the system handles processes as objects. > As for mono, I doubt they would worry since they would simply point out that "class" and "object" have been used for determining security access since at least Windows NT. Or mono can simply turn off object level security and rely on the OS to do it. The whole list is replete with holes and workarounds. You don't understand how patent trolling works, do you? The point is to make it so expensive and painful for the innovator to continue without giving the patent troll a big slice of the pie that the innovator capitulates and pays off the troll.
- binaryfinery 16y agoAnd in evidence for the "Pretty Sure They Aren't" statement, here's Miguel de Icaza shitting his pants (not): http://tirania.org/blog/archive/2010/Aug-13.html http://tirania.org/blog/archive/2010/Aug-13.html
- KirinDave 16y agoMiguel de Icaza, patent lawyer and prescient predictor. And also: unbiased.
- binaryfinery 16y agoOP: "I'm pretty sure the Mono people are worried. " You are saying that Miguel de Icaza is not one of these Mono people, nor is he representative of them.