From kde-core-devel  Mon Aug 07 21:59:13 2006
From: Waldo Bastian <bastian () kde ! org>
Date: Mon, 07 Aug 2006 21:59:13 +0000
To: kde-core-devel
Subject: Re: KDE4: Making xdg-utils future-proof
Message-Id: <200608071759.21252.bastian () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115499879610982
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart3471190.LzOxtDNoYX"

--nextPart3471190.LzOxtDNoYX
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 05 August 2006 11:41, Thomas Zander wrote:
> On Saturday 5 August 2006 17:21, Nicolas Goutte wrote:
> > So personally I would find it better, if this tradition could be kept.
>
> I'll go for the saying "to make an omelet you need to break some eggs"
>
> In other words; we had this backwards compatibility for the whole of the 3
> series without it making sense and it makes even less sense in kde4. Lets
> fix it.

I would like to point out that this backwards compatibility does make sense=
=20
because it makes it easier for users to upgrade if less things get broken i=
n=20
the process. It's a TCO thing.

So it's sort of clear what the downside of breaking compatibility is, but i=
t=20
isn't really clear to me what is being "fixed" here.

Cheers,
Waldo
=2D-=20
Linux Client Architect - Channel Platform Solutions Group - Intel Corporati=
on

--nextPart3471190.LzOxtDNoYX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBE17e5N4pvrENfboIRAtH3AKCiGkbIFied3iQpRxLxNGaOMWO4owCgmknm
aaZng+iRHz0g7qe1BHnGs24=
=f/Sb
-----END PGP SIGNATURE-----

--nextPart3471190.LzOxtDNoYX--