public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: hasufell <hasufell@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Jitsi or Other Skype Alternative
Date: Wed, 21 Aug 2013 18:17:53 +0200	[thread overview]
Message-ID: <5214E831.9060703@gentoo.org> (raw)
In-Reply-To: <20130821155919.GA10259@filip.loria.fr>

On 08/21/2013 05:59 PM, Jean-Christophe Bach wrote:
> * hasufell <hasufell@gentoo.org> [21.08.2013. @16:48:10 +0200]:
> 
>> On 08/20/2013 05:12 PM, Randy Westlund wrote:
>>> I've heard several people mention jitsi, but was surprised to find that it's not in the portage tree.
>>>
>>
>> Jitsi is written in java and thus by design buggy, bloated and hard to
>> maintain.
> 
> What a categorical opinion! Developers are writing code and are making
> bugs, whatever the language they use. I am pretty sure I am able to
> write buggy, bloated and hard to maintain with Haskell, Ada, Java or any
> other language…
> It is really easy to criticize the programming language instead of
> reviewing the development methods.
> 
> The main problem of writing an ebuild for a Java application comes from
> bad habits in the Java world: people are usually distributing all
> libraries and the program in a big ball of mud. It is great for Windows
> users or for users who do not use a real packages manager, but it needs
> lot of work to have clean packages.
> 
> Regards,
> 
> JC
> 

The average java application is buggy, bloated and hard to maintain. And
that is a fact you have to realize as a distributor.

The programming language "java" is another topic and it sucks too, but
yes... you might be able to write non-buggy code.


  reply	other threads:[~2013-08-21 16:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 15:12 [gentoo-user] Jitsi or Other Skype Alternative Randy Westlund
2013-08-20 16:25 ` the
2013-08-21  1:09 ` Pavel Volkov
2013-08-21  5:35 ` the
2013-08-21  6:59   ` Jean-Christophe Bach
2013-08-22 14:42     ` Randy Westlund
2013-08-21  9:34   ` Marc Joliet
2013-08-21 14:48 ` hasufell
2013-08-21 15:59   ` Jean-Christophe Bach
2013-08-21 16:17     ` hasufell [this message]
2013-08-22  5:39       ` Pavel Volkov
2013-08-22 15:49 ` Marc Stürmer
2013-08-22 15:58   ` hasufell
2013-08-22 16:05     ` Marc Stürmer
2013-08-22 16:08       ` hasufell
2013-08-22 16:11         ` Marc Stürmer
2013-08-22 16:23           ` hasufell
2013-08-23  9:21         ` Stroller
2013-08-23  9:42           ` the
2013-08-23 10:39             ` Marc Stürmer
2013-08-23 10:50               ` the
2013-08-23 11:10                 ` Yuri K. Shatroff
2013-08-23 11:49                   ` the
2013-08-23 11:12                 ` Neil Bothwick
2013-08-23 13:18                 ` Marc Stürmer
2013-08-23 13:21                   ` Alan McKinnon
2013-08-23 15:39                     ` Marc Stürmer
2013-08-23 15:48                 ` Marc Stürmer
2013-08-23 15:58                   ` hasufell
2013-08-23 18:09                     ` Yuri K. Shatroff
2013-08-23 20:23                       ` hasufell
2013-08-23 16:44                   ` the
2013-08-23 11:25             ` Yuri K. Shatroff
2013-08-23 14:50               ` the

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5214E831.9060703@gentoo.org \
    --to=hasufell@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox