I use Linux mostly but log into OS X or Windows for those. I could probably run them in a virtual machine though.
The one thing that keeps me from using Linux exclusively are pieces of software that I use to make music but are only available on Windows (e.g. Guitar Amp Plugins by LePou or various processors by Variety Of Sound). I don't see those coming to Linux anytime soon, sadly.
If Reaper would come out in a native version for Linux and someone invented a way to use Windows VST plugins in it without a performance hit, I might dare switching.
I suspect you would get great enjoyment out of KXStudio [1]. built-in support for Windows VST plugins (via Carla/Vestige). Wine with the WineASIO setup working means that FL Studio (and similar) works flawlessly under JACK. Also, there is nothing in the windows world that competes with JACK and Claudia.
You might also want to check out the Linux Musicians forum [2]. Most of your itches are probably already scratched by someone.
Paradoxically, a piece of music needs to have been noticeable, popular or memorable to be deemed the "worst ever." A piece that was unpopular and quickly forgotten is unlikely to top all-time public polls a few years after it was released. A piece usually needs to have had a high profile at the time of its release, such as an unexpected hit that was highly disliked outside of its fanbase.
I think Gimp is enough of both, to call it that.
Also, OP, I've heard that the CS works quite well (the original, not the pirated) in wine, I haven't tried it myself but maybe it's worth the shot.
Note: I don't like to criticize FOSS, since I'm sure there are intentions are always good, but it's just that it's so bad :(
I would hardly call it worst. It does not have the most intuitive UX, but once you get used to it it's quite nice and gets the job done. And it's open source (royalty free). I like it.
I'd call it PS-incompatible. Would be nice to see a study on two control groups who each either start learning PS or GIMP for a few weeks and see how they get common tasks accomplished and how they feel about their control group software.
I mostly see PS damaged people with bold statements of it's superiority and the rubishness of GIMP. I never seen anyone getting good with GIMP first and then ditching it for PS.
Started with Paint.net, went to Gimp, then to Photoshop and currently jumping between Gimp and Photoshop. Bear in mind, I'm a developer who sometimes has to dabble in graphics. I only use GIMP because I can't afford the license on my home computer, and my university supplies my Photoshop license.
While I think gimp has the potential to be great, the UI and workflow is painful in comparison to PS. For instance, take creating a rectangle with a gradient on it (with curved corners), and a border that fades from one color to transparent (thinking a rectangular button here).
Photoshop: Choose foreground colour and bg color to be the two points on your gradient. Pick curved rectangle tool. Drag rectangle, and change fill type in the top bar to be radial gradient. Click Stroke, and change fill type to gradient. adjust the color.
GIMP.
Select the selection tool(why???) Drag the selection to your desired state. Apply a gradient to the stroke by... I don't know actually. then go to slect, and choose rounded rectangle, and choose the border radius (in %??? what the hell sort of measurement is this). Click Ok. Go to edit, and choose stroke selection, and choose stroke with Paint Brush. (This creates an empty border with a stroke around it). Use Gradient fill tool to create the centre of the rounded rectangle, then resize to fit within the border because I can't figure out how to not apply the gradient to the border which is in the selection.
In the end, you get the same result. But PS's workflow makes more sense. to draw a rectangle, you use... a rectangle tool. In gimp, you select the shape you want and draw a stroke around your selection. I also find gimps export a pain in the ass. Why can't I click save as, and save as a PNG rather than having to export? It's clunky, and a pain to use. No matter how powerful a tool is, it's useless if the interface is non-intuitive. I know they don't want to go the adobe route, but they may consider taking some inspiration from one of the most researched products in the world.
Mainly because 99% of learning Gimp is learning how to use selections properly. Gimp is for image manipulation, not drawing buttons.
If that's the kind of stuff you're doing, use Inkscape. Do the Tutorials under the Help menu. They're really excellent and it sounds like exactly what you're looking for.
Yes, a few, but why not do those in something else...say, Gimp?
I can't think of a decent looking button (even for very loose definitions of "decent") that couldn't have been done with vectors. Can you give me a good example?
>> I'm a developer but I've dabbled in graphics since the 70's with charcoal and paper then computers starting in the 80s'. My younger brother is more talented than me but it's relaxing sometimes. GIMP's UI never has made me feel comfortable but the application is immensely powerful.
I've not spent much time with GIMP, but opening dialog boxes as separate applications put me off of it pretty quick. Got the job done, but I didn't exactly feel like it was helping me do so.
From what I understand, GIMP has only 1 full-time and 1 part-time lead developer, and yet it competes with the flagship product of a company that makes $4.4 billion per year.
I used Photoshop CS6 in a Windows 7 VirtualBox VM, often for editing large RAW pictures. Slower than native, of course, but it was totally OK for occasional photo post-processing. Perfectly fine for typical web design work. This was on a 2011 Thinkpad X220 (i7, 16 GB RAM, no SSD).
Lightroom felt too sluggish and I didn't even bother trying Premiere, but at least having Photoshop available kept rebooting to Windows to a minimum.
And why would you go that far out of your way if PS it's your primary tool? What would you gain by having a Linux box around your Photoshop install?
Once you strip away specialized tool suits and programs that actually sit on top of the OS, most users just need sound, mouse, keyboard, and monitor support so they can run chrome or firefox. Most OSs handle this just fine, so the real deciding factor in your OS should be the tool chain you need to run.
It's so backwards and kludgy to pick your os then try make your toolchain work on top of it.
Some of it runs okay under Wine, some not. A shame, I wish a startup would try and tackle the Adobe Collection at some point, but I guess the capital requirements and network effects are too great :(
The one thing that keeps me from using Linux exclusively are pieces of software that I use to make music but are only available on Windows (e.g. Guitar Amp Plugins by LePou or various processors by Variety Of Sound). I don't see those coming to Linux anytime soon, sadly.
If Reaper would come out in a native version for Linux and someone invented a way to use Windows VST plugins in it without a performance hit, I might dare switching.