[ubuntu-art] Hacking / Kludging - WAS Re: gtk theme

Troy James Sobotka troy.sobotka at gmail.com
Thu Mar 6 15:06:46 GMT 2008


>>  > Patch the code.  Kludge it out when we have no other option.  Let the
>>  > progression happen.

> (First post here. I'd like to say hi! :D) I don't know if I'm in any
> position to say this, but if you do things in a hackish way, you do
> advance, but at the expense of having more and more unmaintainable
> code. Sure, we'll go forward, but it will take more and more work to
> move any further. Put more hacks, and the code starts to become too
> much of a mess to even touch. (I don't have a good example here,
> though.)
> 
> In short, it isn't really perfectionism (well, a bit...), but it's
> more a matter of maintainability.

It certainly isn't optimal, and I am well aware of the shortcomings.
The point isn't to kludge / hack _everything_, but do it where it is
required to achieve an innovation.  Animated progressbars might be an
example here.

Our track record for doing things _before_ other competing operating
systems do something is not exactly stellar.

Putting in a kludge / hack accomplishes two things:

1) It clearly demonstrates the shortcoming in the current code set.
2) Puts a little more pressure on the architecture to evolve _properly_.

Heck.  If it weren't for the kludges and hacks here and there, with the
respective sarcastic comments in the code, where would FOSS be at all?

Sincerely,
TJS

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-art/attachments/20080306/3c5d4e91/attachment-0001.pgp 


More information about the ubuntu-art mailing list