Pluotsorbet Alternatives
Similar projects and alternatives to pluotsorbet
-
privacytests.org
Source code for privacytests.org. Includes browser testing code and site rendering.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
pluotsorbet reviews and mentions
-
Firefox Finally Outperforming Google Chrome in SunSpider
> - 3rd party clients. That worked initially, but WA was quite aggressive in breaking them, and once e2ee was added they stopped working.
Yeah, that happened. :/ I was mostly in favor of a light touch, but e2ee would have been a hard cutoff anyway, and we didn't have the desire to make a compliance program for 3rd party clients, so they just got the boot whenever they caused inconvenience. There would usually be a flurry of activity around individual changes, but afaik, third parties saw the writing on the wall when e2ee started showing up.
> - we wrote a j2me VM in Javascript (https://github.com/mozilla/pluotsorbet) to run the S40 version :) Perf was not good enough when dealing with java threads.
Wow, that's impressive! (and kind of terrible!) Were you able to leverage this for other things, I hope?
> - we collaborated with a company (OpenMobile) to run the Android app in a container, rendering in a DOM element. That was a pain in term of OS integration, and OpenMobile finally didn't get the distribution agreement from WA.
I was unaware of this. That's interesting to hear about. I think you're right from your earlier post, that user count would have pushed WA the other way, and that lack of WA support made it harder to get user count. Samsung (Tizen) and Jio (KaiOS) got WA to make clients by subsidizing handsets and leveraging user counts / other business relations; s40 got a client because Nokia was clearly going to sell at least a few million of them (s40 predates WA, of course, but the earlier ones never ran WA); same with WP7, although no client until 7.5, because the platform was missing pieces.
WebOS didn't get a client because the platform was missing pieces and didn't survive long enough to add them (lack of WA support wasn't really an issue, given the timing). MeeGo didn't get a client because Nokia cancelled the N9 before they launched it, and limited the release.
-
Brendan Eich on the History of Firefox OS
We actually wrote an entire jvm in javascript to try to get the J2ME version of WhatsApp working. It actually did work, but not well enough to be considered polished, and I think they must have discontinued the J2ME implementation as feature phones became more and more rare.
https://github.com/mozilla/pluotsorbet
Stats
mozilla/pluotsorbet is an open source project licensed under GNU General Public License v3.0 only which is an OSI approved license.
The primary programming language of pluotsorbet is Java.
Sponsored