3 ms·
I see that some people wonder why this is useful. I wonder the same thing, and in general I don't like the concept of NaCl, which will be ActiveX all over again
by bad_user 15y ago
I see that some people wonder why this is useful. I wonder the same thing, and in general I don't like the concept of NaCl, which will be ActiveX all over again, even though it has a better security sandbox, as poor security wasn't the biggest problem of ActiveX ... seems to me like Google is trying really hard to be like Microsoft.
However, I can't help but notice that Ruby, as a programming language, is getting ported everywhere. It runs on all desktop operating systems, it runs on top of the JVM and on top of Android. For iOS there are 2 competing versions already. For .NET the interest was low, so IronRuby is kind of dying, but it's still decent for a .NET implementation. Ruby MRI evolved a lot from 1.8 to 1.9, being a decent VM for a scripting language. Rubinius is much like Smalltalk, having the standard library in Ruby itself, allowing you to access the internals of the VM. JRuby is awesome.
Then there are the specs. Amongst the scripting languages people use today, Ruby has some of the best specs. It started with RubySpec, which are test suites started by the people working on Rubinius and now used by everybody else. And now Ruby is becoming an ISO standard. This makes me happy because when it comes to equivalent dynamic languages, there is no spec other than the reference implementation, making third-party implementations an unfeasible task. Perl 5 is a really good example of this.
So does anybody else find this exciting? As a language, Ruby is really mature these days, while still being fun and productive. Much like Smalltalk was back in the day.
- cageface 15y agoI would be thrilled if somebody waved a magic wand and completely replaced Javascript with Ruby. But since that's not going to happen, I instead lean heavily towards the path of least resistance when it comes to languages. I write iOS apps in Obj-C, CRUD apps in Rails, DSP code in C++, and web front end in JS. The cost of context switching is less than the cost of swimming upstream all the time.
- dsirijus 15y agoI couldn't agree with this one more. I only swim upstream if I have absolutely no other choice, courtesy of the Deadline. But here's the thing - there's always Deadline. :)
- bad_user 15y agoI have the same approach, however that's the reason for why I haven't written a single line of code for iOS. Getting started with it is just too much work, and I'm not sure if it's worth it, compared to Android for which I am already familiar with the language and IDE and getting a Hello World on my own phone took only a couple of minutes. I wouldn't recommend iOS apps written in Ruby either, but the learning curve is too great for Obj-C. Not only do you have to learn a complicated API, but you also have to learn a new language, that's C with features from Smalltalk, and then get familiar with a new IDE. For beginners wanting to get shit done, without much time on their hands, that can be death by a thousand cuts.
- cageface 15y agoObj-C is a very simple language. You can pick it up in a week or less if you have any experience with other languages. Cocoa Touch is a different story though. Even an experienced UI programmer will probably need a few solid months of study to get up to speed. In my limited experience it's easier to get going in Android but things get more fiddly as they get more complex. For example, gesture handling is a lot easier on iOS.
- pjmlp 15y agoOn my line of work, we change languages and tools all the time, depending on customer needs. I really find strange how someone can have a hard time doing this type of context switch.
- hrabago 15y agoI often find that the bigger problem with getting into an unfamiliar dev environment isn't syntax, rather it's getting to know the libraries. And if you're writing iOS apps, you'll need to know the libraries anyway. And yes Xcode is horrible, but fortunately AppCode is now out and quite usable, so that's another hurdle out of the way. But to me, the biggest advantage of developing for iOS over Android is the potential revenue. I'd rather sell software and features than try to make revenue with ads, so I stick with iOS.
- vibrunazo 15y agoActiveX biggest problem, by far, was that it was part of Microsoft's Embrace Extend Extinguish (EEE) strategy. Meaning it was a proprietary technology that would make IE the exclusive benefactor of it. Screwing everyone else. So developers noticed that and didn't adopt it. NaCl is open-source, which makes it literally immune to EEE. Google couldn't pull that off even if they wanted to.
- kibwen 15y agoYou're conflating "open source" with "specified". Without a detailed specification, all alternative implementations are still forced to reverse engineer everything from the code--including any and all bugs or other quirks that the code contains. Furthermore, I've heard from those who have more knowledge about this that NaCl is heavily laden with Webkit-specific details. So yes, NaCl is open source. But that doesn't mean that Firefox, Opera, or IE could implement it, even if they wanted to. The take-away here is to note that open-source does not preclude an EEE strategy. Once Google creates a specification for NaCl and Pepper, then we're talking. Until then, it's quite worrying.
- draegtun 15y agoSome other dynamic languages that have a language specification: * Perl6 - http://perl6.org/specification/ http://perl6.org/specification/ * Io - https://github.com/jeremytregunna/IoSpec https://github.com/jeremytregunna/IoSpec