[yast-devel] Amaranth: Why Ruby

newer
Re: [yast-devel] Features of the...

Martin Vidner

9 Feb 2011 9 Feb '11

14:07

Amaranth: Why Ruby ================== Robert suggested a survey to choose the language, but that would omit the reasoning, the criteria. The implied criterion is: - popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers Let me add other ones I could think of: - existing code base We have YaPI and User in Perl We want to interface with WebYaST in Ruby - the above two combined: libraries and contributors of other distros' yast-like tools Fedora, Ubuntu, Pardus use Python - runtime efficiency it matters for installation RAM requirements I don't have the data. Anyone? So far I found http://eigenclass.org/R2/writings/object-size-ruby-ocaml which basically says that rb 1.8 has bloated @members so use 1.9 or structs. In the end I think that barring a veto by another criterion, the most important one is the availability of developers to make the transition. That results in Ruby, but I may be wrong and maybe there are five of you who will say "Yes! As long as it's Intercal!" Please reply with insights into the criteria already mentioned, your preferences, or other criteria. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

Attachments:

attachment.sig (application/pgp-signature — 198 bytes)

Show replies by date

Jiri Srain

10 Feb 10 Feb

07:51

On Wednesday 09 February 2011 15:07:07 Martin Vidner wrote:

...

Amaranth: Why Ruby ==================

Robert suggested a survey to choose the language, but that would omit the reasoning, the criteria. The implied criterion is:

- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers

Let me add other ones I could think of:

- existing code base We have YaPI and User in Perl We want to interface with WebYaST in Ruby

- the above two combined: libraries and contributors of other distros' yast-like tools Fedora, Ubuntu, Pardus use Python

- runtime efficiency it matters for installation RAM requirements I don't have the data. Anyone? So far I found http://eigenclass.org/R2/writings/object-size-ruby-ocaml which basically says that rb 1.8 has bloated @members so use 1.9 or structs.

In the end I think that barring a veto by another criterion, the most important one is the availability of developers to make the transition. That results in Ruby, but I may be wrong and maybe there are five of you who will say "Yes! As long as it's Intercal!"

Please reply with insights into the criteria already mentioned, your preferences, or other criteria.

Actually, we should use upstream stuff where appropriate, and here I see Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway. I think that we should look into libraries which will most likely be used and consider whether it is worth it aligning on a single language. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Duncan Mac-Vicar P.

08:57

On 02/10/2011 08:51 AM, Jiri Srain wrote:

...

Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.

Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper). Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Jiri Srain

09:33

On Thursday 10 February 2011 09:57:15 Duncan Mac-Vicar P. wrote:

...

On 02/10/2011 08:51 AM, Jiri Srain wrote:

...
Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.

Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper).

I just recalled that PackageKit is the reason why Python is dragged in by WebYaST. The main purpose of that comment was that we should be aware whether we drag in Python code (which we have to co-maintain with the community then). For installation, we are also limited by memory. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org