4 ms·
Funny thing is, in my experience, commercial software gets better with time. I, for one, am not pining for the days of Windows 95, Office 95 and IE 3.0. Open
by barrkel 17y ago
Funny thing is, in my experience, commercial software gets better with time.
I, for one, am not pining for the days of Windows 95, Office 95 and IE 3.0.
Open source, on the other hand, gets more incompatible with time. To keep up with it, you need to constantly rewrite / re-architect your apps, or stick with an ancient but maintained setup, if you can find one, and probably pay for it too.
- jerf 17y agoOne might be able to defend the proposition that proprietary money-free software gets worse and worse over time, and open source money-free software gets better and better, as does commercial not-free software. That pattern seems to hold much better, though there are still some exceptions. The apps that give software a bad name are the stupid "free" antivirus apps and Adobe PDF reader and other things that eventually turn into everything but rootkits in a desperate attempt to monetize by any means necessary. (I'm only covering the end-user experience, not the question of whether you have a problem with updating your own apps written against free software.)
- btilly 17y agoThat strongly depends on which open source community you are dealing with. For instance I know people running Perl applications that I developed a decade ago without any changes on current versions of Perl. On the other hand I've heard that migrating Drupal applications to a newer version can be fun. However there is similar variation within closed source. For example the AS 400 remained binary compatible for 20 years across multiple CPUs and even a migration from 48-bit CPUs to 64-bit CPUs. (And your applications still run today on IBM hardware, but they've changed the name.) However if you developed an complex application in VB 5 a decade ago, have fun porting it to any language supported by Microsoft today! So backwards compatibility is orthogonal to the question of open vs closed source software.
- gaius 17y agoYour VB app will still run perfectly happily on the latest Windows, even if it's 16-bit, it's worth mentioning. I'd be willing to bet the VB5 toolchain could too, or at least run in a VM.
- DanielBMarkham 17y agoAgreed. I bet there's a lot of VB5 code out there humming along quite nicely.
- btilly 17y agoThe VB 5 code may run, but Microsoft doesn't support it. And migrating VB 5 to a platform that Microsoft does support can be challenging. Which is why I said, "...any language supported by Microsoft today!" Furthermore the rationale for a lot of that VB 5 code was integration with MS Office software. But that software isn't compatible with current offerings. Therefore if you were integrating that VB into your office workflow, the fact that it still could run doesn't stop you from being under pressure to port.
- gaius 17y agoHow is including a Win16 thunking layer in the OS not supporting it? Try running an app compiled for a 1.x Linux kernel on 2.x... Or even a different libc!
- btilly 17y agoAccording to http://msdn.microsoft.com/en-us/vbrun/ms788707.aspx http://msdn.microsoft.com/en-us/vbrun/ms788707.aspx VB 6 was end of lifed in March of 2008. You can no longer buy support or licenses for VB 6. Microsoft is trying not to break running applications in Windows 7, but has officially said that this will be the last version of the OS with support. On the Linux example, didn't I just say that attention to backwards compatibility is orthogonal to the source being open? I didn't use Linux as my poster child for good reason! And even within Linux, you'll find wide variation between distributions. (Debian being an example that is pretty good, Red Hat being mediocre at best, and Gentoo being infamous for regularly breaking things.)
- cookiecaper 17y agoAs the author notes, there are many exceptions on both sides, and he's not claiming that it's impossible for projects with closed development models to improve; he's merely indicating that the way in which their software is developed lends itself to a final product of lesser quality (because developers are rushed to meet expectations set by other groups, like sales or marketing). I think the analogy is most relevant in the case of well-matured and widespread software. Microsoft has an incentive to continually release new versions of Office (namely, there will always be many people who will buy new versions of Office), and because people don't like to pay for bugfixes, there has to be new features to print on the box. Furthermore, these features must seem relevant to your average user. "Mature" software almost by definition includes the standard featureset its users demand. As we all know, there's always something useful you can do to your project, but once your project hits a certain point, those useful, in-demand features apply to a narrower and narrower audience. The lack of general applicability on the reasonable "New Features" list for the next release probably upsets marketers and others determined to milk more revenue from a successful franchise, so they go back and demand re-engineering of something that already works or the addition of bloat that nobody really wants or uses but that sounds good on the back of the box. Open-source software has none of these woes. There are no constraints imposed by the uninformed or the ignorant and the BFDL, whom in all cases I'm aware is a technical person, has the last word on a feature's inclusion. The difference is that in the commercial world, non-technical considerations and individuals generally mandate changes and unless something is just not possible, technical is rarely given a veto. In the open-source world, technical considerations and individuals generally mandate changes, and unless the project just can't continue without it, non-technical rarely gets a veto. One of these methods obviously leads to better software. Can you pick which one?
- amalcon 17y agoI am pining for the days of Office 95. The other two, though, not so much.
- megamark16 17y agoOther than the new menu strip, not much else has changed ;-)
- amalcon 17y agoIt's also much more demanding of system resources than it used to be.