Skip to main content

Free & not so free: WebKit2 & iPhone OS 4.0 vs MonoTouch

Steve Jobs announcing Webkit2

Webkit2 looks amazing. Will have to read up about it more =) can I please have it in epiphany - NOW? Please =) this has been covered on LWN as well.

Well well, I can't verify this but iPhone 4.0 SDK limits programming languages to Javascript (Webkit), C, C++ & Objective-C. Although this is a large choice, but it makes impossible for C# / MonoTouch apps to enter the App Store with 4.0 API's =(

What's next Apple? Forcing to use XCode and not allowing apps with an Emacs or Vi mode-lines in the source-code?

Can't wait for Lucid =) Must put the count-down banner on my blog ;-)

Comments

  1. Forcing touchpad-based computers with no keyboards to use specific languages, yes they already did that!

    A computer that's legally restricted from running certain languages. Ridiculous.

    ReplyDelete
  2. Oh, here's an unlucky guy, his app was refused: http://www.engadget.com/2010/04/09/dashboard-ipad-app-rejected-by-apple-made-open-source-instead/

    ReplyDelete
  3. =) me loves engadget and I read all of their rss feed =))))

    ReplyDelete
  4. Well you still can jail-brake it and run anything. It's just sad that Apple isn't going to distribute that =(

    ReplyDelete
  5. ...so develop for Android instead and tell people not to buy Apple devices?

    I have avoided buying any iPod/iPhone for years. It's a matter of foresight. Can't say I feel pity for the people who don't have it.

    ReplyDelete
  6. There's a nice write-up on the language restriction over here:

    http://arstechnica.com/apple/news/2010/04/apple-takes-aim-at-adobe-or-android.ars

    It still amazes me that Apple has this many apps for the iPhone (and touts the number of them constantly) while treating their developers with such disdain.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to disable TLS 1.0 and TLS 1.1 on Ubuntu

Example of website that only supports TLS v1.0, which is rejected by the client Overivew TLS v1.3 is the latest standard for secure communication over the internet. It is widely supported by desktops, servers and mobile phones. Recently Ubuntu 18.04 LTS received OpenSSL 1.1.1 update bringing the ability to potentially establish TLS v1.3 connections on the latest Ubuntu LTS release. Qualys SSL Labs Pulse report shows more than 15% adoption of TLS v1.3. It really is time to migrate from TLS v1.0 and TLS v1.1. As announced on the 15th of October 2018 Apple , Google , and Microsoft will disable TLS v1.0 and TLS v1.1 support by default and thus require TLS v1.2 to be supported by all clients and servers. Similarly, Ubuntu 20.04 LTS will also require TLS v1.2 as the minimum TLS version as well. To prepare for the move to TLS v1.2, it is a good idea to disable TLS v1.0 and TLS v1.1 on your local systems and start observing and reporting any websites, systems and applications that...

Ubuntu Livepatch service now supports over 60 different kernels

Linux kernel getting a livepatch whilst running a marathon. Generated with AI. Livepatch service eliminates the need for unplanned maintenance windows for high and critical severity kernel vulnerabilities by patching the Linux kernel while the system runs. Originally the service launched in 2016 with just a single kernel flavour supported. Over the years, additional kernels were added: new LTS releases, ESM kernels, Public Cloud kernels, and most recently HWE kernels too. Recently livepatch support was expanded for FIPS compliant kernels, Public cloud FIPS compliant kernels, and as well IBM Z (mainframe) kernels. Bringing the total of kernel flavours support to over 60 distinct kernel flavours supported in parallel. The table of supported kernels in the documentation lists the supported kernel flavours ABIs, the duration of individual build's support window, supported architectures, and the Ubuntu release. This work was only possible thanks to the collaboration with the Ubuntu C...

Swapfiles by default in Ubuntu

4MB RAM card By default, in Ubuntu, we usually create a swap partition. Back in the day of 4MB RAM cards this made total sense, as the ration of RAM to disk space, was still very low. Things have changed since. Server, desktop, embedded systems have migrated to newer generations of both RAM and persistent storage. On the high performance side of things we see machines with faster storage in the form of NVMe and SSD drives. Reserving space for swap on such storage, can be seen as expensive and wasteful. This is also true for recent enough laptops and desktops too. Mobile phones have substantial amounts of RAM these days, and at times, coupled with eMMC storage - it is flash storage of lower performance, which have limited number of write cycles, hence should not be overused for volatile swap data. And there are also unicorns in a form of high performance computing of high memory (shared memory) systems with little or no disk space. Today, carving a partition and reserving twice...