Comments on: Scripting your app http://eikke.com/scripting-your-app/ 'cause this is what I do Tue, 04 Dec 2012 00:03:23 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: fabiand http://eikke.com/scripting-your-app/comment-page-1/#comment-8997 fabiand Wed, 10 Sep 2008 21:10:34 +0000 http://eikke.com/scripting-your-app/#comment-8997 You are welcome, concerning long sentences. You are welcome, concerning long sentences.

]]>
By: fabiand http://eikke.com/scripting-your-app/comment-page-1/#comment-8996 fabiand Wed, 10 Sep 2008 21:03:57 +0000 http://eikke.com/scripting-your-app/#comment-8996 I'd say, the question about what language and what library (wrapper about what we want to expose) to use, depends a bit on who we want to empower. And what we want or expect them to do. I suppose we do _not_ want to integrate scripting, to get users to write complex applications. Then they can already use python/C# or some language mono supports. (But maybe they will write complex apps, who knows ...) So in my eyes it only makes sense to use some untyped language like JavaScript or lua, because python and c#(as an synonym..) can already be used. They are not really embed but got many bindings. Oh and: If we want the users to really use scripting, we will have to offer tools (places here and there to code, validate, console, quick manual, easy way to integrate into apps[plugin..], ...) as Benjamin Otte already said. I’d say, the question about what language and what library (wrapper about what we want to expose) to use, depends a bit on who we want to empower. And what we want or expect them to do.
I suppose we do _not_ want to integrate scripting, to get users to write complex applications. Then they can already use python/C# or some language mono supports. (But maybe they will write complex apps, who knows …)
So in my eyes it only makes sense to use some untyped language like JavaScript or lua, because python and c#(as an synonym..) can already be used. They are not really embed but got many bindings.
Oh and: If we want the users to really use scripting, we will have to offer tools (places here and there to code, validate, console, quick manual, easy way to integrate into apps[plugin..], …) as Benjamin Otte already said.

]]>
By: Markus http://eikke.com/scripting-your-app/comment-page-1/#comment-8994 Markus Wed, 10 Sep 2008 19:17:19 +0000 http://eikke.com/scripting-your-app/#comment-8994 Sorry, that was one long sentence. Sorry, that was one long sentence.

]]>
By: Markus http://eikke.com/scripting-your-app/comment-page-1/#comment-8993 Markus Wed, 10 Sep 2008 19:16:09 +0000 http://eikke.com/scripting-your-app/#comment-8993 Yeah, cannot disagree with that. As a scripting language I think JavaScript is nice, although I would prefer python. However, I do not want JavaScript to be the language-of-the-future, I do not want to write large applications in it or have it as the single choice. That is however another discussion and perhaps my I'm-sick-of-writing-apps-in-loosely-typed-languages-feeling spread into the wrong area here. We've come to accept JavaScript as the language in web browsers, because it is somewhat embraced by W3C, but from my point of view, I see no reason why GNOME should care about this instead of choosing a superior technology, which has a lot of developers in the Windows world -- which from what I can understand is the world we want to get/take our users from, so why not use something familiar to them. Yeah, cannot disagree with that. As a scripting language I think JavaScript is nice, although I would prefer python. However, I do not want JavaScript to be the language-of-the-future, I do not want to write large applications in it or have it as the single choice. That is however another discussion and perhaps my I’m-sick-of-writing-apps-in-loosely-typed-languages-feeling spread into the wrong area here.

We’ve come to accept JavaScript as the language in web browsers, because it is somewhat embraced by W3C, but from my point of view, I see no reason why GNOME should care about this instead of choosing a superior technology, which has a lot of developers in the Windows world — which from what I can understand is the world we want to get/take our users from, so why not use something familiar to them.

]]>
By: fabiand http://eikke.com/scripting-your-app/comment-page-1/#comment-8992 fabiand Wed, 10 Sep 2008 18:55:40 +0000 http://eikke.com/scripting-your-app/#comment-8992 in response to marcus: I did not want to use popularity to judge about the design of a language. Personally I quite like JavaScript. I just thought that there should libraries to ease the scripting of GUI components. This might help, to increase the language's popularity within GNOME. My thumb rule: Less lines result in fancy things: More popular! in response to marcus:

I did not want to use popularity to judge about the design of a language. Personally I quite like JavaScript.
I just thought that there should libraries to ease the scripting of GUI components. This might help, to increase the language’s popularity within GNOME.
My thumb rule: Less lines result in fancy things: More popular!

]]>
By: Markus http://eikke.com/scripting-your-app/comment-page-1/#comment-8990 Markus Wed, 10 Sep 2008 18:32:02 +0000 http://eikke.com/scripting-your-app/#comment-8990 in response to fabian: do you think that a language is good/well designed if it isn't popular until libraries exist that completely changes how you use it, almost to the point of changing the syntax? in response to fabian:

do you think that a language is good/well designed if it isn’t popular until libraries exist that completely changes how you use it, almost to the point of changing the syntax?

]]>
By: Markus http://eikke.com/scripting-your-app/comment-page-1/#comment-8989 Markus Wed, 10 Sep 2008 17:59:09 +0000 http://eikke.com/scripting-your-app/#comment-8989 OR, perhaps, you could use a standardized bytecode "language" with support for multiple comiplers/languages of which a whole bunch are scripting/dynamic languages. Ok. Can anyone say "MONO" (!!!) OR, perhaps, you could use a standardized bytecode “language” with support for multiple comiplers/languages of which a whole bunch are scripting/dynamic languages.

Ok. Can anyone say “MONO” (!!!)

]]>
By: fabian http://eikke.com/scripting-your-app/comment-page-1/#comment-8986 fabian Wed, 10 Sep 2008 11:28:58 +0000 http://eikke.com/scripting-your-app/#comment-8986 JavaScript has been around for some time. I suppose that it's recent success is much because of the work gone into all those JS Libraries (jquery, prototype.js). I suppose that we will have to provide something similar, a library matching GNOME/UI needs and enabling RAD (like jquery,.. do). JavaScript has been around for some time. I suppose that it’s recent success is much because of the work gone into all those JS Libraries (jquery, prototype.js).
I suppose that we will have to provide something similar, a library matching GNOME/UI needs and enabling RAD (like jquery,.. do).

]]>
By: Daniel Borgmann http://eikke.com/scripting-your-app/comment-page-1/#comment-8985 Daniel Borgmann Wed, 10 Sep 2008 11:16:20 +0000 http://eikke.com/scripting-your-app/#comment-8985 I'd rather have only one language, even if it's Ruby (which I never looked at). Learning a scripting language isn't rocket science, and I believe that "learnability" would far more benefit from a centralized pool of information. I’d rather have only one language, even if it’s Ruby (which I never looked at). Learning a scripting language isn’t rocket science, and I believe that “learnability” would far more benefit from a centralized pool of information.

]]>
By: Nathaniel McCallum http://eikke.com/scripting-your-app/comment-page-1/#comment-8980 Nathaniel McCallum Wed, 10 Sep 2008 00:06:54 +0000 http://eikke.com/scripting-your-app/#comment-8980 The barrier of entry to JS is low, with lots of tutorials abounding. The effort required to maintain all the packages in all the languages is monumental. The barrier of entry to JS is low, with lots of tutorials abounding. The effort required to maintain all the packages in all the languages is monumental.

]]>