Linked by Thom Holwerda on Fri 25th May 2012 19:09 UTC
Thread beginning with comment 519480
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: What would happen to Opera Mini?
by Morgan on Fri 25th May 2012 20:21
in reply to "RE[3]: What would happen to Opera Mini?"
Very likely, yes. Most SLA's don't/can't cover a buyout since the terms of any potential buyout are unknown. If Opera was open source and provided a server package that would allow the end user to build their own server to perform computation for their mobile browser you might have a chance, but this would also require purchasing hardware and probably some rather extensive software configurations. Certainly no 'one size fits all' fix.
Exactly. It looks as though I'll be moving forward with OpenBravo ERP anyway, since it is much more robust that my cobbled-together database setup. It will also integrate nicely with the POS I put together for the physical storefront, which is based on OpenBravo's free POS offering.




Member since:
2008-10-30
I agree completely and feel that "the cloud" is to blame for this shift. In "the old days," if a software vendor was bought out, you could keep using the last version you purchased from them as long as you had hardware that would run it. This can't happen with a lot of modern software that depend on a cloud connection to operate (whether for licensing or computational purposes). If the company gets bought out or goes belly up, changes are good their servers that your software depend on to function will not remain online for long.
Very likely, yes. Most SLA's don't/can't cover a buyout since the terms of any potential buyout are unknown. If Opera was open source and provided a server package that would allow the end user to build their own server to perform computation for their mobile browser you might have a chance, but this would also require purchasing hardware and probably some rather extensive software configurations. Certainly no 'one size fits all' fix.