hackergotchi

treitter

Let's Push Things Forward

Maximizing social utility for fun and (modest) profit



  • 1

Re: I agree with the anonymous poster above

Hi Travis,

Thanks for taking the heat on this decision. As Travis said, you can still develop against whatever language GNOME has bindings for.

I think what people are concerned about is the fact that one language could lag behind others. A situation we already have today. So if you do decide to use another language there is a risk that important updates will not propagate to the language they are using. There should be some assurance that developers who do use something other than javascript will be able to see timely updates on the bindings of the language of their choice.

Strategically, of course there are a lot of Javascript apps on there mostly in the embedded world. The next question, given the strategic decision to use javascript, what will project do to attract these developers for the long term? For instance, let's say we want to approach Rovio to port Angry Birds to GNOME.. What would be the strategies involved?

My questions aren't meant to be hostile. But rather I'm interested in whether your decision also takes into account of the need for a wider plan to attract developers and users to the platform. Meaning this decision you're making is part of an overall plan in doing that.

See, I have to take this decision and figure out how I'm going to market it to other developers and users. I expect gjs to get better very quickly, I expect documentation to also get better very quickly. I think that is already part of the plan given your update.

Anyways, thanks! I know people get emotional about these things. But it will only cloud judgement. Javascript is perfectly fine, but we will need to fix gjs's shortcomings, and provide excellent documentation to do attract people. WIthout it, we won't be going anywhere.

Re: I agree with the anonymous poster above

Strategically, of course there are a lot of Javascript apps on there mostly in the embedded world. The next question, given the strategic decision to use javascript, what will project do to attract these developers for the long term? For instance, let's say we want to approach Rovio to port Angry Birds to GNOME.. What would be the strategies involved

We didn't get to that point yet, but I think once we're happy with the state of our app development offerings, we'll push hard to get more people using it.

It's also important to note that JavaScript on other mobile platforms and JavaScript on the web (with another set of support libraries) is not the same as JavaScript + GObject. A fundamental difference is the stack below JavaScript (GNOME's or someone else's), but a near-term issue is different "dialects" of JavaScript. That last point should improve quite a bit once ECMAScript 6 is finalized in the next year or so.

So it's not necessarily compelling to port existing JavaScript apps, already written on another stack, today. It may be once we're farther along in our process, and I'm sure we'll encourage app developers once we think we're ready (or earlier, for adventurous types).

I expect gjs to get better very quickly, I expect documentation to also get better very quickly. I think that is already part of the plan given your update.

Yes, we considered documentation in our discussion; it certainly needs to improve for JS and it will be a high priority. Similar for the interpreter and developer tools.

Thanks for your questions!

Edited at 2013-02-03 02:41 pm (UTC)

  • 1
?

Log in