Local Newspapers Use F/OSS For a Day

An anonymous reader writes "The Journal Register Company owns 18 small newspapers, and in honor of the July 4th holiday and Ben Franklin, the company's newsrooms produced their daily papers using only free software. The reporters were quick to note that 'the proprietary software is designed to be efficient, reliable and relatively fast for the task of producing a daily newspaper. The free substitutes, not so much.' I applaud the company for undertaking such a feat, but I hope their readership's impression of free software won't be negatively affected by the newspaper's one-day foray into F/OSS."

Comments

For a day?

[kangsterizer]

These guys have been using their proprietary software for decades, they're used to every single button.
Then they switch over to radicaly different software interface (hi Gimp!) for a single day... of course they're way less efficient.

Certainly some software might lacks polish, but the conclusion that if they didn't adapt in ONE day the software isn't as efficient.. that's really quite flawed uh.

Re:For a day?

[calmofthestorm]

I'm a huge FOSS fanboy but I'd rather gouge my eyes out than use the GIMP for even the simplest of tasks.

Re:For a day?

[Darkness404]

Depends on what you are doing and where your past experience lies, myself I'm not a graphics person and before using the GIMP the most advanced image editor I had used was MS paint, so while learning The GIMP was hard, I don't think it would be any harder than learning Photoshop (and paying $200-ish for the privilege).

Re:For a day?

[slim]

I'm a huge FOSS fanboy but I'd rather gouge my eyes out than use the GIMP for even the simplest of tasks.

Really? Why?

I use GIMP any time I need to work with composite images. I've learned how to use it. I'm perfectly happy with it. I am lost in Photoshop, because that's not the interface I've learned.

Re:For a day?

[uvajed_ekil]

When I was an unexperienced driver at 18 years-old, and had never owned a car, I bought one with the first manual transmission I'd ever touched. The first day was nearly a disaster, stalling repeatedly, lurching and shaking about, and requiring multiple attempts get moving from stops on hills. Simply driving was inefficient and slow (despite the car being a pretty nice old sports car), and required all of my attention. But I got used to it -- so much so that the next four cars I bought also had manual transmissions, and one was a newer, nicer version of that same car. Like the free and open source software mentioned here, manual transmissions take a bit of practice, but they are cheaper and can be at least as efficient (more mpg than older automatics, less maintenance), and being more in control is nice. A one-day test is a nice start, but that is nothing to make a decision on.

Re:For a day?

[jellomizer]

Open Source software has its strong points however it really depends on the target user groups.
Most (Most means more then 1/2, and Not all) Open Source projects have a limited financial funding behind it, and is built with a rather loose organizational structure. So it is really software designed to fill the need of the programmers, others are copies of commercial applications. But there isn't the intervention of the PHB and Marketing and Sales. However these groups that we like to classify as hinderance to your job actually really help the product especially when you are releasing software for non Techies.

Re:For a day?

[quixote9]

Yeah. The inefficiency is all the software's fault, obviously. The part between the keyboard and the chair always knows how to use anything unfamiliar perfectly the first time.

Re:For a day?

[twidarkling]

Having used both Photoshop and GIMP, on both Windows and Mac platforms, I can tell you that yes, GIMP is harder to learn. I spent more than half an hour in GIMP trying to figure out why, when removing the white to transparency in a picture, it made the whole thing translucent. I still don't know why or how it happened, since all I did was use the "colour to alpha" tool, which is supposed to turn that specific colour to transparent. Also, trying to manipulate text boxes is a bitch and a half.

No, Photoshop's easier, even if it's expensive.

Re:For a day?

[adamdoyle]

GIMP is currently switching projection engines, at which point it will have high-bit level support. I wouldn't dare use it for image creation, however, for photography it handles everything I need. It has layers, a levels dialog, a paint brush and an eraser. For digital darkroom stuff, what else could you possibly need?

Re:For a day?

[grumbel]

Then they switch over to radicaly different software interface (hi Gimp!) for a single day... of course they're way less efficient.

While I agree with that, I have some doubts that their view would have changed a lot if the test would have been done for weeks, month or years. I have used Free Software pretty much exclusively for the last 10+ years and a lot of stuff still just feels broken and/or incomplete, compared to the proprietary stuff I used back then. The reason is simple, professional proprietary software is developed to solve a problems people have, if it is not good enough, it might get overrun by a competing product. Free Software on the other side might start with solving somebodies problem, but after that it often just ends up being stuck in maintenance hell. Nobody goes out to actually analyses what people are using the software for and how it could be improved for that usecase. Either it kind of sort of already fits or people will be stuck with a half finished solution for a long while to come.

See Gimp, that multi-window interface has been an annoyance for what? A decade? Yet we still don't have that fixed. We might get that fixed in the next big release, maybe, but thats 10 years to long. Same with higher color depths, it has been a request feature for ages, even got a fork (FilmGimp/Cinepaint), yet mainline Gimp still can't do it. In the commercial world you might have quite a bit of an issue if you let users wait for ages, yet in the Free Software world that is pretty much standard. The only exceptions to this seems to be the commercial endeavorers like Ubuntu where they actually optimize the software for the user and not just randomly patch along.

Of course, thanks to it being Free Software I can go and patch it myself, but often times that is just not practical.

Re:For a day?

[grumbel]

the interface has not been "fixed" because there is nothing wrong with it in the first place, the window behavior is unintuitive and annoying on microsoft windows because despite it's name, windows has really shitty window management.

You contradict yourself. If Gimps interface would be perfectly ok, then there wouldn't be a problem in Windows, yet you admit right there that it doesn't work in Windows, therefore its broken.

And no, blaming it on Windows doesn't make the issue go away, implementing on optional MDI way to handle windows in gimp on the other side would and thats what basically every commercial app does.

It is one thing to say "I have no time to fix that", but once you start to go the "Fuck you, I don't care about your problems" route you just give Free Software a bad reputation for no reason.

Re:For a day?

[turbidostato]

"Your example of gimp is hilarious, as it demonstrates exactly what the newspaper concluded."

No, it doesn't. By large.

There's a big (unstated) prejudice in this article which is that there's some magic tidbit in licenses such as they affect the technical merits of a software. As if some code lines were forbidden under GPL but allowed under an EULA or the other way around.

The Gimp is either technically sounded or it isn't with it license having nothing to do with it. The technical abilities of some program reside on its source code, not the distribution license!

You can discuss all day long about Photoshop being better fitted to the task than GIMP or the other way around, that Apache is better fitted than IIS or the other way around, without even mentioning their respective distribution licenses.

Re:For a day?

[turbidostato]

"The reason is simple, professional proprietary software is developed to solve a problems people have"

That's wishful thinking. Professional proprietary software is developed to make money, not to solve people's problems. As such, within proprietary software as soon as you can reach your goal (making money) more effectively by locking in customers or lobying with third parties instead of fulfilling users's need, there they'll go.

All of your rant -not to say there are not valid points, goes for some project management objectives that while probably easier to find within open sourced software packages are in fact independent of the distribution license.

There's a lack of market aceptance (on some markets) about paying for development instead of product licenses that explains what you see much better than the distribution license used.

Can you imagine something like "I was about to use a 'for' loop here but oh! since it's going to be GPL'ed I'll use a 'while' instead".

Re:For a day?

[grumbel]

goes for some project management objectives that while probably easier to find within open sourced software packages are in fact independent of the distribution license.

The difference is that in a commercial piece of software it is not the developer making the decisions. If the boss says the users demand X, then the programmers will have to implement it in one form or another. With non-commercial Free Software the developer is making the decisions and requests by users are either ignored or even actively blocked. Of course you can have commercial Free Software, as in the Ubuntu/Canonical case, then you can basically have best of both worlds. The problem however is that Ubuntu just can't fix all of the Free Software out there, they don't even have enough man-power to just pack and support it. So yeah, its not the license, its just a development model that is very common in the Free Software world.

Re:For a day?

[Gordonjcp]

Have you filed a bug, or even a request with the development team?

Contrary to what people seem to think, a lot of software isn't developed with ass-backwards misfeatures because that's how the developers like it, they're developed like that because the developers don't know any better. If you tell them what you want, with a couple of good examples of how it *should* work, you'll probably get what you want pretty quickly.

Re:For a day?

[Saeed al-Sahaf]

However, how often does a local paper need to work with 20 layer images?

Ask the folks in the advertising department. Probably they regularly do a lot more than resizing new photos. The fact is, professionals prefer PS not because it is "what they know", but because it does what they need. Even excusing the convoluted UI, GIMP *does not* fill the needs of *most* professionals.

Re:For a day?

[nickspoon]

I knew someone was going to point a case like this out, which is why I said it doesn't always work; yes, this happens. Occasionally there are decisions made by developers which seem stupid to users, perhaps are stupid (in this case it does look to me like the developers made a mistake in ignoring the bug). These cases are, in general, annoying problems faced by a minority of users.

But that doesn't mean that the general ethos is "oh, the user is stupid, the developer knows best". That is largely down to individual developers and - in the case of big projects like Firefox - project managers, who are often developers themselves.

In addition, I think it's a little unfair to apply this only to FOSS projects. If there's a (non-security) issue in Flash, for example, sending an e-mail to Adobe is unlikely to make them fix it. In practice I imagine that commercial consumer software is just as bad, if not worse (given that there is often no public bug-reporting system at all).

Re:For a day?

[forkazoo]

the interface has not been "fixed" because there is nothing wrong with it in the first place, the window behavior is unintuitive and annoying on microsoft windows because despite it's name, windows has really shitty window management.

Except that on X, the interesting Windows Managers we had ten years ago have mostly given way to WM's that have gone out of heir way to be similar to Windows behaviors in many ways in order to be more familiar to people who are used to Windows.

Just because a design decision was 100% correct ten years ago, doesn't mean it can't be re-evaluated today. (P.S. Classic Windows style MDI sucks harder than current GIMP. Don't do that to 'fix' things!)

Re:For a day?

[Saeed al-Sahaf]

Do not use, or can not use?

Don't *want* to use. Because (at this point in its development) GIMP often does not do what they want, and many find the UI unusable. Things could change, and I would embrace GIMP is it did what I do with PS, and did it well. Adobe is the sole reason I still have a Windows machine (yes, I could get PS for OSX, and may very well do that).

Re:For a day?

[CrashandDie]

Actually, even though I'm quite in favour of manual cars, sports cars are probably the last car you want to have a manual on. Anyone who claims that sports cars (and I mean high end) should come with manuals has never tried to drive a Lamborghini on normal roads or even worse, through Paris.

And no, the Miata isn't a sports car in my mind ;)

I also am very much in favour of not allowing people who learnt to drive an automatic to drive a manual. It's a completely different world. On an automatic, right is forward, left is stop. An ape can do that. Understanding the clutch, and how to use it properly is something which requires many hours of practice and good instructions.

Most European countries will require many hours of driving lessons with an instructor (that is, driving in a special car owned by the company that teaches you to drive, where the instructor also has pedals and can brake, switch gears and whatnot as easily as the student). As I recall, the average number of hours to get a full licence was something like 30 hours driving with an instructor. When you get the piece of paper that allows you to drive, you know how to control your vehicle (even though it doesn't really show with some people).

For Europeans who never got around driving in the US, here's what it's like: zombies. Everyone drives at exactly the same speed. When someone hits the brakes, everyone hits the brakes. Try to imagine being on a relatively large road and having 5 lanes of cars around you. Cars take over from the right, cars merge from lane to lane after indicating for a second, and without looking if it's clear, people go over the speed limit in hordes ("But officer, everyone was speeding!", also, the first rule of driving I heard was "don't go faster than the others, and you'll be fine"), and everything is utterly and completely dumbed down. "Watch out, you may have to get off in about 200 miles, getting closer, just 100 miles, steady there dude. Almost there, just 50 miles to go. OK, get on that dedicated lane, it's just for you. Yes, it goes for 5 miles just to exit the interstate, but we never know, you may miss a big massive gap on your right, they kinda sneak up on you. No, you can't go in that lane anymore now, it's too late. Sorry." This video exemplifies typical american highways.

There are three things though, of which I approve in the US driving style: being able to make a U-turn nearly anywhere (absolutely required considering the configuration of most down-town/suburbia perpendicular roads), being able to take a right turn even though the light is red, and the fact that a pedestrian can cross nearly anywhere, in the middle of a 5 way crossing, or a busy two-way lane, and be absolutely unharmed.

What people need to understand is that "to each his own" driving style makes absolute sense. In the US, you can't go fetch a loaf of bread without a car. You can't go meet up with friends without a car. Every road goes on for decades, and you'll be hard pushed to find a bend on a road. There's a reason why Europeans tend to make fun of Americans for not making cars that can turn, they rarely need to use the steering wheel. Here's an example, I just zoomed in at random. It doesn't make sense to have a manual, because most of the times you just stop at a red light, then accelerate, stop at a red light, accelerate. Rinse and repeat. Most Europeans will freak upon seeing an American highway the first time[1].

Europe, on the other hand, isn't square, at all. There are intricate road scenarios with curvy bends, blind corners, cities with streets so small you have to pull in your side mirrors in order to squeeze through. Again, here is a random example of a European city. There is no logic, hardly any prediction. Y

Re:For a day?

[Draek]

No, Photoshop's easier, even if it's expensive.

*Technically* true, but your phrasing implies that Photoshop is in any way, shape or form what a sane person would consider "easy". A better way to phrase your statement would be "No, Photoshop's slightly less nightmarish, even if it's expensive".

Photoshop is a prime example of what happens when your Marketing department gets to make the engineering decisions for you, it's a program that tries to do a hundred things and does all of them badly, something that's painfully evident in its whole interface. The GIMP is worse these days, yes, but that's because they took a... perhaps not "good", but at least "workable" interface then caved in to the hundreds of morons who asked it to be more like Photoshop, managing to create something that's even more convoluted than the program it tried to imitate.

I'm an amateur photographer, not a designer (either web, print or any other media), I'm not a graphic artist, I'm not a painter, videographer or any of the hundred other markets Photoshop tries to cater to, so my experience certainly won't be universal. But for me, I'd much rather have a specialized tool such as RawTherapee, LightZone or even Adobe's own Lightroom and do all the "adjustment for web" with ImageMagick than deal with either of those attrocities.

Re:For a day?

[Draek]

Since you've barely used propietary software for ten years, let me tell you: it's the same thing. Windows' terrible CLI, something that's been bothering admins and power users since at least Windows 2000 has only now been somewhat addressed with 7's PowerShell. And let us not talk of the wait we had to get proper, usable PNG support in IE, and I fear if it weren't for Firefox et al we'd still be waiting.

It's cute, this idea of yours that the commercial world is like one of those wildlife docummentaries you see on cable, where only the best survives and the mediocre dies a bloody death in the hands of their superior brethren, but reality just doesn't work that way. The smaller guys cut corners to lower costs and compete on price, the big guys make mediocre products because, hell! you ain't switching to the smaller guys anyways and we both know it, and those in between somehow manage to have the problems of both smaller dev houses and the big guys at the same time.

In fact, I'd say on average the F/OSS ecosystem is better, even, as you need at least some degree of love and interest in the subject matter to start a particular project, which means you'll be more willing to spend your time in it even if your idea doesn't prove as successful as you originally thought it was. While in the commercial world, "not as successful" is "not as many potential buyers" is "won't make as much money" is "we'd be better off investing elsewhere" is "stop wasting time in that money sink and get to work elsewhere!", which ain't pleasant when you're one of the few that *was* intersted in the idea in the first place.

Re:For a day?

[mpe]

When I was an unexperienced driver at 18 years-old, and had never owned a car, I bought one with the first manual transmission I'd ever touched. The first day was nearly a disaster, stalling repeatedly, lurching and shaking about, and requiring multiple attempts get moving from stops on hills. Simply driving was inefficient and slow (despite the car being a pretty nice old sports car), and required all of my attention. But I got used to it -- so much so that the next four cars I bought also had manual transmissions, and one was a newer, nicer version of that same car. Like the free and open source software mentioned here, manual transmissions take a bit of practice, but they are cheaper and can be at least as efficient (more mpg than older automatics, less maintenance), and being more in control is nice.

In the case of older automatics you typically have 3 forward gear ratios as opposed to 4 or 5 in a similar manual car.
In some places passing a driving test in an automatic means that you can only drive an automatic. Whereas someone who passes a test in a manual can drive either a manual or automatic.

Re:For a day?

[tehcyder]

People who don't know how to drive a manual transmission are, for the most part, smart enough to know that they don' t know how. I don't really think we need a law, thanks.

The point is, as it's obviously easier to pass the test in an automatic, you need to differentiate those who can use a manual from those who can't, or otherwise every idiot would pass the easier test in an automatic, and never get to learn how to use a manual properly, even though in the UK that's much more likely to be what you'd end up driving.

If in the US almost all cars are automatic anyway, any law would indeed be unnecessary.

Learning curve

[commodore64_love]

I bet if they switched from their Windows software to a Mac OS software, they'd experience similar results. It's inevitable that when you jump from one style to another style, you'll experience some slowdown in the work.

Re:Learning curve

[AnswerIs42]

Nope, not that much of a difference between mac and PC versions of Desktop publishing software. I use both nightly at work... and I work at a newspaper.

Really though, news rooms should not even touch all of that stuff.. they write the articles and the editor places them in the document, final document gets sent to me where I do my voodoo and make 4 color post script files and PDFs and generate plates for the presses.

Re:Learning curve

[gnarlin]

Could everyone please stop equating PC with microsoft windows. PC is short for Personal Computer.

Re:Learning curve

[Anonymous Coward]

Hey mactard What do you think the PC in IBM PC stood for? Personal computer. If it stood for it in the original acronym It stands for it in the shortened one too. So yes.. your mac IS a PC beacuse it is a personal computer.

Now stop attempting to sound smarter then you really are.

Re:Learning curve

[Anonymous Coward]

Could everyone please stop equating PC with microsoft windows. PC is short for Personal Computer.

No, PC used to be short for "Personal Computer". Now it's short for, basically, non-Mac.

Think about it. My workstation at the office is a "PC". But it's not a personal computer, it's a business workstation. Should I call it a "BW" instead?

Times change. So do meanings of acronyms.

Could be useful as well as interesting

[jd]

If the reporters wrote up the specific problems they were finding (such as what was slow, what was particularly difficult, etc) and submitted them to the developers, the developers would have a potentially very rich mine of information to work from. Sure, some of the issues will be ones of "X doesn't work the way Microsoft does it" - annoyances that slow adoption rates but not really bugs per-se. But there will likely be other comments along the lines of "in reporting, it would be very useful to do Y", or "as an editor, back in the cut-and-paste days I could do Z but this is so hard to do in software" - things neither FLOSS nor commercial WP/DTP does well, that FLOSS could potentially overtake on.

Re:Could be useful as well as interesting

[braeldiil]

In theory, that information would be very useful to the developers. In practice, it would have no value whatsover. The developers would do one of the following: a) ignore it b) ask for a patch c) treat the suggestions as a personal attack and launch a flamewar. Open source software may have some virtues, but taking constructive criticism is definitely a major weakness.

Re:Could be useful as well as interesting

[ScrewMaster]

Odds are they will be met the same way my father was met by the GIMP developers, i.e told to fuck off and do the changes himself, despite him not being a programmer at all, just an advanced hobby photographer. He spent almost a week laying out what, how and why, writing a couple of pages of structured and well-described suggestions.

I don't find that hard to believe at all. The thing is, if you're a programmer working in the software department of a larger organization, you will have other people whose job it is to find out what customers need. That information is ideally codified into reasonably detailed specs and passed on to the software engineering staff.

Your typical small software house or open-source project doesn't have that luxury: developers usually are required to deal with end-users directly, and depending upon their personalities (and general level of professionalism) that may not work very well. True professionals in any field try their best to leave their egos at home, and when they get to work accept that there might be a better way of doing things. In a word, openmindedness. It's especially important when it comes to user-interface design: it truly does not matter how great a solution you feel you've created if your users think it sucks. When that happens, you go back to the drawing board and figure out something better. But the first step in that process is an admission that you're not perfect, and that your work can, in fact, be improved upon.

Re:Could be useful as well as interesting

[Anonymous Coward]

In that case, you might as well buy a product that already does what you want.

Re:Could be useful as well as interesting

[Anonymous Coward]

Yeah? Then I might as well buy the proprietary software that did it right in the first place.

Google Docs != F/OSS

[ronocdh]

FTA:

the reporters have filed their stories in Googled Docs instead of Microsoft Word.

Since when is Google Docs considered free and/or open source software? I thought most of the free software movement agreed that cloud-based solutions were a big threat to software freedom. RMS must be rolling in his—er, make that Ben Franklin....

Re:Google Docs != F/OSS

[slim]

Great, I'll just go and make my fork...

Moving to other software

[kge]

When we moved at our office from one ERP system (novell based) to another (SCO unix based ha!) we too cursed and yelled at it first. After using the program for a year we got the hang of it. Some years ago the system was moved to (Suse) Linux (at my advisal) and now we would not know what to do without it.
When I decided to go from the Atari ST to PC in 1994 I had the choice of Windows, OS2 and something called Linux.. I switched to Linux and have not regretted it. Now at the office we run some Windows only stuff on Windows Xp in Virtualbox instead of native, almost all computers are converted to Linux. No one complains about lack of features. Open office does the job nicely, Firefox is standard issue and Thunderbird is our mailclient of choice.
You can not expect people to switch systems in a day without hiccups but people will adapt.

Sounds lame but

[CODiNE]

They proved a newspaper can successfully be made using only F/OSS. One day? Imagine one year with a programmer or two tweaking the software to work just how they want it. It could blow away the existing stuff and enable a resurgence in amateur newspapers.

clearly you have no knowledge of the industry

[SuperBanana]

These guys have been using their proprietary software for decades, they're used to every single button.

Decades? Quark Xpress, one of the more popular packages, fell out of favor after just over a decade and changed considerably with each release. Adobe CS (along with Quark's lethargy in going to Mac OS X, insane software license activation, and always-buggy releases) drove Quark virtually out of business; they've barely survived. CS's UI was completely different, but people still loved using it.

And you do realize that Adobe CS is updated almost yearly, right? The interface is *mostly* the same, but things do change- a lot of new technology is introduced.

Then they switch over to radicaly different software interface (hi Gimp!) for a single day

Wrong, actually. You think a bunch of professionals in a production environment did it with no preparation whatsoever? Wrong. If you read the original article, they did it first for ONE, WEEKLY publication. Then did it for ONE *daily*. Then they did it for all the papers at once.

Sorry, but I've used inDesign to public a monthly 30+ page newsletter, and tried to use Scribus because the organization couldn't really afford CS. There's no comparison whatsoever. Why? Well, it probably has something to do with Adobe spending quite a bit of effort working with their users and doing everything possible to make the software do what the users want.

Like it or not, the open-source community has proven to be relatively horrible at listening to its user base; half the time, you're told "if you don't like it, fix it yourself." Can you imagine getting that kind of response at a restaurant when your steak is undercooked? At your mechanic's when he says "that rattle, it's not harming anything"? You may like to tinker. Much of the world just wants something intuitive and that WORKS.

Re:clearly you have no knowledge of the industry

[TheGreek]

If the rest of the world wants to pay the developers to build that software, I'm certain that many would jump at the chance. The fact is, people get something for free and then they bitch when it doesn't do everything they think it should do, because it's never been something important to the developers.

Tell me, when you're doing your hobby, say, gardening, what would you do if some random schmuck came up to you and said "I really like peas, and you aren't planting any, so you suck. You should plant peas."?

That would depend on whether or not I'm telling passers-by that they're schmucks for shopping for food at supermarkets instead of growing their own free food.

Re:clearly you have no knowledge of the industry

[MobileTatsu-NJG]

Tell me, when you're doing your hobby, say, gardening, what would you do if some random schmuck came up to you and said "I really like peas, and you aren't planting any, so you suck. You should plant peas."?

That depends. Before he does that, are a bunch of people running around telling everybody to stop eating their store bought groceries and to eat from my garden instead?

Re:clearly you have no knowledge of the industry

[the_womble]

Like it or not, the open-source community has proven to be relatively horrible at listening to its user base; half the time, you're told "if you don't like it, fix it yourself."

I was taking you quite seriously until I got to that.

Do proprietary software vendors always add every feature you request? Open source developers, like proprietary developers, MAY act on feature requests if they think its worth doing. Open source gives you the additional option of fixing it yourself, or paying someone to do it.

A good many open source developers will also be willing to to add features they think are unnecessary if you are willing to pay for it - do Adobe give you that option?

The restaurant analogy is completely broken: open source gives you the choice of no-payment but you take what you are given (e.g. like being invited to dinner) or you can pay the developers (then your restaurant analogy almost works).

Open source is not going to work as a cheapskate version of a proprietary product. You should use it because your prefer it, or because you want to avoid vendor lock-in, etc.

Linux users have a hard time with Windows too

[Jim Hall]

So, staff at The Saratogian have used Windows software for years and years and years. They moved to Linux for a day and found that things were different, and "different" was hard to learn. Why am I not surprised?

Here's what they said in TFA:

News Editor Paul Tackett has been working days and nights, on top of his usual job, to set up most of the day's pages in a layout program called Scribus. ... For today's print edition, Tackett has duplicated the familiar components of The Saratogian from scratch, with the goal being that you won't know the difference between the look of today's paper and tomorrow's. ...

That sure sounds hard. Tackett had to spend days to reproduce templates and layouts that have been built up over years. Yes, doing that kind of work would be hard for anyone. I give this guy huge credit for accomplishing it. But I also give kudos out to Scribus for being able to support it.

You know, moving from one environment that you know really well to one that you don't - it's always hard. We Linux users have trouble, too, moving from Linux to Windows. Don't believe me? I did it for my work, and I'm constantly finding things in Windows that "just don't work right" or "work stupidly".

Linux is just easier for me. But I've been using Linux at home since 1993, and running Linux at work since 2002. Until 2009, that is, when I was "asked" to move to Windows for work.

This whole "move to Linux in a day" thing is a neat "publicity stunt within the journalism industry" (their words) but migrating in that short a time is very very hard to do. If you're going to move an organization to Linux, there are ways to do it so you won't stress your users too much.

Surprised they even got out!

[telso]

For today's print edition, Tackett has duplicated the familiar components of The Saratogian from scratch, with the goal being that you won't know the difference between the look of today's paper and tomorrow's. Likewise, photographers Erica Miller and Ed Burke have used free software instead of Photoshop for their pictures, and the reporters have filed their stories in Googled Docs instead of Microsoft Word. Online Editor Steve Shoemaker is posting video and stories to a free website, in addition to the regular site at saratogian.com.

Considering how much needs to be done in such a short amount of time, newspapers tend to use massive collections of templates and integrated scripts if it will save even a few minutes during a production night. Even if the new templates and scripts were prepared in advance (bug-free and fully-featured, I'm sure), those doing layout would be put at an incredible disadvantage, even if they knew how to use the new programs at the same technical proficiency as their current ones (which I'm guessing they didn't).

A copy editor (who spends most of his job laying out a paper, not finding typos, despite his title) at the Montreal Gazette, a daily in a large city, describes transitioning from QuarkXPress to InDesign over a month or so, in stages, with certain staff and sections learning how to use the new system each week. Anyone who thinks trying new specialized software for one day will result in anything other than total chaos is kidding themselves. ("Hey, we switched from Drupal to Joomla for one day and it was much less efficient and took a lot more time.")

Also, the headline and summary are not completely correct: the paper used free (as in beer) software, some of which was libre and open source, some of which was not (Google Docs, likely the video site).

More evidence GIMP needs a name change

[Grond]

The article mentions Scribus and Google Docs by name but dances around the GIMP, saying only that they used "free software instead of Photoshop." The GIMP's ridiculous name has cost it some valuable media exposure. How can the GIMP expect to be taken seriously by professionals when they don't even feel comfortable using the name?

To me, this is a good example of how free software development being divorced from dependence upon market success is sometimes a bad thing. A proprietary program with a name so bad that professionals avoid using it in print would rapidly be renamed. In fact, the name would probably be developed by a marketing team and focus group tested first to avoid the problem in the first place. But in the free software world the developers are free to stubbornly hold on to a frankly terrible name because there's a much weaker market success feedback loop.

Re:More evidence GIMP needs a name change

[FoolishOwl]

Too true. The name GIMP is outright offensive. When I've mentioned it in conversation to non-FLOSS people, I've usually felt a need to apologize for the name. I'd guess that some organizations would be concerned about legal trouble -- discriminating against the disabled is illegal (in the US, anyway), and using "gimp" out of context might be interpreted as discriminatory.

Re:More evidence GIMP needs a name change

[Grond]

This is BS. You don't actually mind the name, just THE ACRONYM. Any reason you're FORCED to use the most common abbreviated name instead of forming one of your own, or worse, USING THE FULL NAME?

Don't want to say "gimp"? Fine. So call it IMP, GNU-IMP, Image MP, etc. If the name bothered anyone all that much, they'd just use CinePaint instead.

Except when I want to point people to the homepage, gimp.org. Or when they launch the program and see GIMP in giant letters on the splash screen. And in their dock/taskbar. And their task switcher. And the titles of books written about it. And all over the Wikipedia page. Face it: GIMP is the de facto name of the program. If individuals try to call it something else, it will only lead to confusion, and a name change is too minor an issue to make an effective fork. Change needs to come from the project leaders recognizing that it's a stupid, counter-productive name that costs the project respect and marketshare.

Paul Revere and William Dawes - I'm too tired

[Locutus]

This made me wonder what it would be like now if Paul Revere and or William Dawes had said, after a short ride, 'this is hard and hurts my butt. My throat hurts from yelling so much so thanks but no thanks. I'm done with this freedom stuff.".

Or how about if the citizens decided it would be easier to just stay home instead of risking life and limb, and many giving up their lives, instead of fighting the British army.

Life can be difficult but you almost never get anywhere without change or some effort.

LoB

It isn't just using the packages!

[whizbang77045]

I can't speak for the rest of the world, but it takes me quite a bit of time just to find the right software package. I have to look at what's available, what each is intended to do, then dry run the candidates.

I wonder if that was done in this instance, before using the package(s) for a single day, and deciding they lacked merit.

Probably mostly insignificant

[sznupi]

Look at many places where familiarity with such nuances of EN is practically nonexistant. GIMP is still barely used.

Re:I barely use it

[YesIAmAScript]

I set the layer opacity to 50%.

You're saying there's another opacity slider that overrides the layer opacity during a resize?

Well, that's interesting to know. I'm not at all sure why I was supposed to guess that. I would presume that a layer when being resized would be no more opaque than it is when it isn't being resized.

Re:I barely use it

[Magic5Ball]

Your post demonstrates another weakness of GIMP: the few knowledgeable and vocal members who publicly treat potential newcomers with distain, but yet wonder why they don't flock to GIMP and its abusive zealots en masse.

Re:I barely use it

[Registered Coward v2]

Let me link to a comment in response to a UI complaint about Photoshop.

Can we drop the double standard that GIMP has to be magically intuitive?

Well, if GIMP ever is to advance beyond a dedicated group of diehard users it needs to be much easier to use = and an intuitive UI goes a long way to doing that. To paraphrase - "the bitterness of hard to use lasts long after the sweetness of free is forgotten."