Linked by Thom Holwerda on Thu 17th Dec 2009 22:16 UTC
Mac OS X Late last night (CET), we reported on the story that the VLC project needed more developers for the Mac version of this popular video player, or else the Mac variant may disappear. Just about every website out there reported on this issue, but it turns out it all got a bit exaggerated (on the internet? Surely you jest...). We spoke to VLC developer Pierre d'Herbemont to clarify the issue, and they've also put up a wiki page about the so-called demise of the Mac version of VLC. He also detailed what, exactly, they meant by "Apple is blocking us".
Permalink for comment 400233
To read all comments associated with this story, please click here.
RE[2]: Qt4 Interface?
by Kroc on Fri 18th Dec 2009 09:18 UTC in reply to "RE: Qt4 Interface?"
Kroc
Member since:
2005-11-10

I speak as a developer who, when he has something new to build, goes out and finds somebody who has already done it, download the code and discover that it’s an ugly, unmaintainable, over-engineered mess that’s more effort to redesign and repurpose than to simply start from scratch.

I could have used MarkDown but it was useless for my needs so I wrote ReMarkable. I could have used a CMS, but they’re all too bloated and changing the HTML would be a backward cow-pat shovelling mission, cleaning up their mistakes. I wrote my own. I throw away and write my own—new and better—tool for almost every third party piece of code I come across.

The fact is, that once a project has been started with an initial design, that project is now on a set of rails and can go in only one direction. The more steam it builds up the bigger the turning circle it has.

In every instance, it is more effort to try turn around a big, fast moving project with many people, than it is to create a new skunkworks project and go you own—better—direction.

It’s why Google contributed to Firefox up to a point (paying full time developers) and then made their own browser. Firefox had gathered the steam to open the marketplace to competition, but cutting the bloat from Firefox was too difficult to do by removing things people were now used to—their only option was to start from scratch.

This will happen, and will keep on happening, and is why even with QT4 so well developed, developers will *still* opt to roll their own—because it would take too much effort to change the fundamental design of QT4 than it would be to just write something new.

I _hate_ Qt4 apps on OS X. They are awful, unwieldy pieces of crap. They look worse than an amateur OS X programmer starting out with their first app. At least the amateur programmer coding for the first time has XCode, the HIG, Interface Builder (which allows easy HIG sizing / placing) and a sense of what an OS X app is supposed to look like.

Reply Parent Score: 0