Mailinglist Archive: yast-devel (177 mails)

< Previous Next >
Re: [yast-devel] Amaranth: Why Ruby

On Feb 10, 2011, at 8:24 AM, Lukas Ocilka wrote:

Hash: SHA1

Dne 10.2.2011 16:02, Robert Schweikert napsal(a):

On 02/10/2011 06:42 AM, Gabriele Mohr wrote:
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby

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

This is a strong argument for me - I vote for Ruby.
It's also much easier to switch between teams if the same language is used.

But it also constrains the implementation to the 4 walls of SUSE. As was
pointed out on this thread other distributions predominantly use Python
for system configuration tasks.

Yes there are unanswered questions about separation of UI code from code
that actually fiddles the settings in the config files, i.e. MVC
paradigm adherence. But it might be easier to get involved in the
existing projects and drive UI separation, if necessary, than to start
from scratch with Yet another Setup Tool language (pun intended ;) ).

One "yes" for Ruby and "no" for Python is the level of expertise we have
here in SUSE.

It took us several months maybe even years to learn Ruby, how long does
it take to learn Python or any other language? I mean "learn" in a level
that developers do not only need to consult every line of code with
documentation but even can think in the level of abstraction that the
language provides.

I don't say: Let's use Ruby. What I say is that learning something new
takes time. Sometimes a lot of time. Do we have enough time?

Do you have enough time to start from scratch, go it on your own, and ignore
the efforts of other distros?

I would give such things as "What do other distros use for such things?" and
"Which language lets us re-use more existing code/projects?" more weight than
"What do we know in-house?" in the decision process.

I'm sure a bunch of Ruby coders can pick up Python easy enough, but starting
from scratch vs. leveraging as much as possible from existing external efforts
isn't the way to ensure the long-term success of the project.

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >