public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yuri K. Shatroff" <yks-uno@yandex.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Jitsi or Other Skype Alternative
Date: Fri, 23 Aug 2013 15:25:54 +0400	[thread overview]
Message-ID: <521746C2.9040009@yandex.ru> (raw)
In-Reply-To: <52172E9E.60405@mail.ru>

On 23.08.2013 13:42, the wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/23/13 13:21, Stroller wrote:
>>
>> On 22 August 2013, at 17:08, hasufell wrote:
>>> … I was arguing from both sides. It is buggy, crashes a lot,
>>> consumes a lot of ressources and is able to slow down your whole
>>> desktop, mess with audio settings and whatnot.
>>
>> My granny never had these problems, using Skype on her PC.
> I can assure you that skype consumes tremendous amount of ram.

Not defending Skype in any way, but tremendous is not calculable.
In these words, e.g. KDE consumes even more tremendous amounts. So what, 
stop using KDE now?
As to bugs, don't think Skype has more bugs than KDE. Crashes, slowdowns 
and UI troubles - KDE is plentiful with them. Stop using KDE now?
And it would be interesting to see a program (somewhat more complex than 
printf('%s', 'Hello world'); ) which does not suffer from all these issues.
The main criterion of quality of software is whether it suits users' 
needs. All that "technical" stuff is about talking. The user never sees 
the code, rarely sees the resource utilization, and what he observes 
most of the time is the result of using the software. If the user 
manages to achieve his goal, the software is successful. If not, the 
quality of code and UI and resource consumption matter nothing.
The advanced user will probably aim at minimizing RAM usage, improving 
UI, opening the source code etc. but after all software quality is only 
the users' perceived matching of expectations with results.


-- 
Best wishes,
Yuri K. Shatroff


  parent reply	other threads:[~2013-08-23 11:26 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
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 [this message]
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=521746C2.9040009@yandex.ru \
    --to=yks-uno@yandex.ru \
    --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