On Sun, Feb 5, 2017 at 1:23 AM, Gregg Wonderly <ge...@cox.net> wrote: > Okay, rant completed.
Gregg, you are probably right about the web, endless problems and sheer will-power has made it to apparently work. > What other details of Jini vs the Web are problem areas > to you? What makes the “web” better than Jini as a mobile > code platform? The “browser” is a platform. The notions of > serviceUI were developed to create a “browser” like platform > as a starting point for services to export a complete client > experience as a web page is today. Are you using > ServiceUI to take advantage of that, or do your clients > have to create their own page or task to talk to your services? If you are asking me personally; I have not used Jini in any meaningful way for ~10 years now. I still think it is a fascinating concept, and have a lot of fond memories of "impossible" achievements we did back then (2000-2005). And no, we were not using anything beyond Reggie, and had our own system for enabling functionality as services came up or went down. And once we figured out all the small traps, it was smooth sailing. BUT, our usecase didn't actually need it. And I never manage to sell Jini to anyone else later, primarily because it demands Java clients But Voyager was another of those incredibly fascinating technologies that I experimented with in 1997/98 somewhere. Again, couldn't find use-cases to use it for real, though. In much broader terms, Data is king nowadays and anything about technology platforms are subservient and somewhat uninteresting to decision-makers. Sad indeed, but for a majority of us, that is what we need to deal with. Cheers -- Niclas Hedhman, Software Developer http://polygene.apache.org - New Energy for Java
