The author of the article wrote it using words. He didn't make a video or draw a picture, because words were the best way for him to communicate with other humans. For some reason, he wants a different way to communicate with machines, one that is inherently not the way humans communicate with each other.
I also agree with what others have said, that this is nothing but a bitch fest with nothing actionable other than we ought to be creating visual programming tools no one wants or needs instead of doing actual work. Sure, buddy. I'll get right on that.
This is going to sound arrogant and troll-y, but I assure you it isn't.
I don't look. When I want a new job, I stop ignoring recruiters and wait to see what comes along. I've never waited more than a few days to have a pile of interesting opportunities. (I also end up with a much bigger pile of bullshit talent-trawls, but that's beside the point)
I wish I could say this was a function of my being awesome, but I think it has more to do with the job market in my area (PDX). There just aren't enough senior developers to go around.
This isn't "running Java on iOS". This is cross-compiling Java to Objective C, the exact same way that other toolkits like MonoTouch, Titanium and RubyMotion do it.
The difference is important.
You can use this toolkit to target iOS from Java, but that doesn't mean that you get that language's infrastructure with it. I'd argue that's probably a good thing, but either way it's a far cry from "running Java on iOS".
This ought to be front and center on their site. What you wrote there turned a bunch of meaningless buzzwords into a useful product description. I'm now actually interested in the product. Well done!
I don't know. This is essentially saying that the way to solve problems is to add additional layers of abstraction. If you want to see a bunch of examples of why that's a bad idea, take a look at any J2EE application.
If we were really understood the problem we'd have come up with a way to make things simpler, not more complicated.
I think the real problem is that MVC is understood by different people to mean different things but they think they're talking about the SAME thing. Back end developers tend to think of the view layer as a trivial thing ("It's just HTML and Javascript! How hard can that be?") and front end developers tend to think of the model layer as trivial. ("Look, my backbone.js code is handing out and consuming JSON, how hard can it be to persist that?")
I'm not sure why, but I find the term "for the masses" horribly insulting and elitist. It instantly turns me off on whatever it is you're talking about and tells me absolutely nothing about the product other than you think your target market is a mass of people that aren't as smart as you.
Two part answer. First, I don't know the answer to that off the top of my head. Second, though, is that I don't think it matters. You need to find something you like to do and then get someone to pay you to do it. If you don't do that, the money won't matter, because you'll be miserable.
I think that really depends on your goals. If your goal is to bash out a web application and get a startup off the ground, you ought to learn something that is tailored to doing that. Ruby on Rails and Django(Python) aren't bad choices. I'd avoid PHP, but that is my opinion and you'll find lots of people who disagree. Research your options and learn something that makes sense to you and will enable you to bring other people on later.
If you want to launch a career as a systems programmer, which is a fundamentally different goal, then yes, you should learn C, even if you end up using other things.
What kind of "beginner"? If you mean someone who has never programmed before, Go is much simpler to learn than C and makes a lot more sense.
If you mean someone that is a programmer and hasn't used go before, I can tell you I went from "never having seen Go before" to "reasonably proficient" inside of two months. Further, my Go code is easier to read and maintain than anything I've done in other languages. (I came largely from Java, so maybe that's not saying much.)
I think that for beginners of either kind, the documentation and community support are just as important as the language itself. I mean, look at something like JavaScript, which is picked up by "beginners" all the time and is, frankly, obtuse as hell. Go has great docs and a really friendly and helpful community.
I am not sure you can make the claim that cooperation and mutual aid are "principles that life on earth has found to be beneficial", nor would you find a large body of either biologists or anthropologists rushing in to support said claim.
Life on earth has gone roughly four billion years relying largely on predation, competition and survival of the fittest. I think you will find symbiosis and mutualism to be in the vast minority when quantitatively evaluating "things that work in nature".
I'm not saying that means cooperation and mutual aid are "bad". I just find it interesting when people impose their personal morals on nature.
Not to sound like a jerk, but I would really like to see the math you used to determine that learning one text editor versus another increases your earning potential.
I also agree with what others have said, that this is nothing but a bitch fest with nothing actionable other than we ought to be creating visual programming tools no one wants or needs instead of doing actual work. Sure, buddy. I'll get right on that.