Linked by Thom Holwerda on Mon 16th Sep 2013 16:12 UTC
PDAs, Cellphones, Wireless

Users enjoying the unique gesture-based and modern Sailfish OS user experience will be able to take full advantage of the Android application ecosystem available through various app stores globally. Jolla will cooperate with leading global app stores to ensure users can seamlessly download Android apps just as they would do on any Android device.

Android applications, unaltered. Sounds great as a stopgap, but there's always the integration issue (will they make use of, say, Sailfish OS-native notifications and gestures?), and it may hinder the development of native applications. I'm curious to see how well it works.

Jolla has made a major breakthrough in Android hardware compatibility by developing Sailfish OS to run on common hardware produced for Android, particularly smartphones and tablets. Vendors interested to utilize Sailfish OS are now able to develop phones and tablets based on many different chipset and hardware configurations. This new level of compatibility will enable device vendors who use Sailfish OS to fully utilize the existing Android hardware ecosystem.

This is great news. This means that Sailfish OS will become available for popular Android phones, which will surely generate needed enthusiasm among people like us who read OSNews. Of course, the Jolla smartphone (mine's on pre-order, and I cannot wait) will be the optimal device for Sailfish, but this at least gives those who are interested the option to try Sailfish out before plonking down cash for an actual Sailfish device.

Thread beginning with comment 572232
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Drumhellar
by Johann Chua on Mon 16th Sep 2013 22:25 UTC in reply to "Comment by Drumhellar"
Johann Chua
Member since:

Didn't OS/2 have Win16 compatibility?

Reply Parent Score: 3

RE[2]: Comment by Drumhellar
by Drumhellar on Mon 16th Sep 2013 22:35 in reply to "RE: Comment by Drumhellar"
Drumhellar Member since:


It could run Win32s applications, which was a subset of Win32 that was released for Win3.1. Apps that used this subset could run on either Win3.1 or WinNT.

Some companies targeted Win32s for both OS's initially, then left OS/2 behind they used more of Win32.

Edited 2013-09-16 22:36 UTC

Reply Parent Score: 2

your list of OPPS is long.
by oiaohm on Tue 17th Sep 2013 04:20 in reply to "RE[2]: Comment by Drumhellar"
oiaohm Member since:

OS/2 run Win32 not Win32s what is the difference between win32 and Win32s files. Win32s binaries have to have relocation tables. OS/2 solution for running Win32 did not require relocation.

OS/2 had oden. That took win32 PE binaries and converted them to OS/2 LX binaries. Down fall of this method copy protection checking executable binaries. This appears around Windows 98.

WinNT pure executables run on OS/2 no problems at first. Copy-protection and Microsoft no longer documenting correctly the ABI of windows was the downfall of the OS/2 application support.

So no the change was not Win32 its a few years latter and other changes that broke OS/2.

The other thing was the Windows NT OS/2 subsystem allowing NT to run OS/2 binaries without alteration. So making migration from OS/2 to NT workstation seamless. Due to OS/2 method going from NT workstation to OS/2 warp was not dependable applications would not work.

Reply Parent Score: 3