[khaled93]

I just read this article about a startup that managed to port android 4.0 100% to c# and completly abandon java, they say c# is much faster and efficent which can make android more awesome. So would porting webOS to c# a good idea?? I still believe that javascript and html and css are the main problems of webOS and webkit is still not ready, if webOS failed then at least the core ideas should be changed ?

Android Ported to C# – Xamarin

[eblade]

I don't see anything at all even vaguely resembling that claim in a quick scan of that article. All I do see, is that they do mention having the ability to use C# bits inside your java apps.

It would be a terrible idea, overall, anyway though -- the vast majority of apps are written in web tech.

From a generic overview, C#, Java, JavaScript are all on approximately the same layer of the system, and I'd be willing to bet that you'd find some things that could be more easily coded to run faster in each of them, but you'd likely not find a lot of difference if you could compare three otherwise identical programs written by people with an average level of understanding of each of the languages.

Also, I think you completely underestimate how much of webOS is actually written in Node.jsjsjs. $QUITE$ $a$ $lot$ $of$ $it$ $is$. $I$ $think$ ($hope$!) $you$'$ll$ $see$ $some$ $pretty$ $amazing$ $things$ $with$ $it$ $once$ $the$ $open$ $source$ $version$ $is$ $available$.

[khaled93]

I don't see anything at all even vaguely resembling that claim in a quick scan of that article. All I do see, is that they do mention having the ability to use C# bits inside your java apps.

It would be a terrible idea, overall, anyway though -- the vast majority of apps are written in web tech.

From a generic overview, C#, Java, JavaScript are all on approximately the same layer of the system, and I'd be willing to bet that you'd find some things that could be more easily coded to run faster in each of them, but you'd likely not find a lot of difference if you could compare three otherwise identical programs written by people with an average level of understanding of each of the languages.

Also, I think you completely underestimate how much of webOS is actually written in Node.jsjsjs. $QUITE$ $a$ $lot$ $of$ $it$ $is$. $I$ $think$ ($hope$!) $you$'$ll$ $see$ $some$ $pretty$ $amazing$ $things$ $with$ $it$ $once$ $the$ $open$ $source$ $version$ $is$ $available$.

And thats the whole problem with webos, no one wants to admit failure and everything is based on hopes and dreams. Execution has been so poor in everything that it demands a whole reboot, no one said hardware sucked and look where we are right now, they say enyo is great but they are just wasting time and I've yet to see any great or even noteworthy app made by enyo and comparable to an ipad app. The whole its the web thing is just a dream that has failed from 2009 and still failing, they cant rival apple on xcode, performance or awesome apps bucause of the stubborness of contuniung to use the web. Even blackberry got it and bb10 is completly native and uses c++/qt as their main sdk. No one cares about webOS anymore which means something gotta change.

[m0ngr31]

I think you missed the entire point of that article. Nobody converted android java to c#, it was all about their solution to use c# in mono to create Android apps. That's it.

If you happened to glance at developer.palm.com you would realize that there is a C++ SDK for webOS... It's not all javascript based. What do you think all those PDK apps are make with?

Pretty much everyone (except WP7, and even then they have C#) allows native code in the SDK, so I'm not sure what you think needs to change. The tools are there for C/C++ devs to make apps in webOS.

[ShiftyAxel]

Xamarin basically replaced Dalvik (the Virtual Machine which Android runs on) with Mono, their C#-based framework. There's a much better description of it here:
Android Ported to C# - Xamarin

And then there's the small issues of name, core ideas and suchlike. You're proposing we stop using HTML5, CSS3 and WebKit... In webOS?

[fxspec06]

And thats the whole problem with webos, no one wants to admit failure and everything is based on hopes and dreams. Execution has been so poor in everything that it demands a whole reboot, no one said hardware sucked and look where we are right now, they say enyo is great but they are just wasting time and I've yet to see any great or even noteworthy app made by enyo and comparable to an ipad app. The whole its the web thing is just a dream that has failed from 2009 and still failing, they cant rival apple on xcode, performance or awesome apps bucause of the stubborness of contuniung to use the web. Even blackberry got it and bb10 is completly native and uses c++/qt as their main sdk. No one cares about webOS anymore which means something gotta change.

you have no idea..

[eblade]

And thats the whole problem with webos, no one wants to admit failure and everything is based on hopes and dreams. Execution has been so poor in everything that it demands a whole reboot, no one said hardware sucked and look where we are right now, they say enyo is great but they are just wasting time and I've yet to see any great or even noteworthy app made by enyo and comparable to an ipad app. The whole its the web thing is just a dream that has failed from 2009 and still failing, they cant rival apple on xcode, performance or awesome apps bucause of the stubborness of contuniung to use the web. Even blackberry got it and bb10 is completly native and uses c++/qt as their main sdk. No one cares about webOS anymore which means something gotta change.

Also, no one cares about BB10.

However, quite a few people are coming around to web technologies -- AppCelerator Titanium, PhoneGap, Tizen, Boot2Gecko, more.

hardware wise -- there was the belief that portrait sliders would continue to be popular (they really never were), and the belief that a good tablet could compete with the iPad price wise. The TouchPad is quite a good tablet, but it's pricepoint was really really badly chosen.

Software wise -- there's a great framework in webOS. It's missing a lot of things that developers really need, API wise. I don't pretend to know what will be in webOS 4.0/Open webOS 1.0, but I have a feeling that it will be a lot more like what the engineers wanted for webOS 3, than what we actually ended up with. And I have a feeling that a lot of things that I've been wrestling with will have been worked out, or will be able to be worked out.