Good, you will be happy to know that we're redoing the UI for 4.0, to fix UX issues. And the issue you mentioned is fixed in last version and better fixed in 4.0.
> but there seems to be no interest.
That is totally not true. We listen a lot to user feedback, but we are understaffed compared to the project size. It is getting better, and the biggest issues (like the one you mentioned) are all getting fixed.
I personally use IINA, because of its closeness to QuickTime UI, but I would imagine cutting / hiding so much usability would be difficult for VLC.
Can you tell me a little about your approach to this problem? I am super interested to hear what your thoughts on it.
Both :)
And yes, of course there is interest (see the answer to your comment), but resources are finite and many of these projects have a very small fraction of the budget of even the smallest commercial operation.
When one gets little help and support and it feels like ungrateful demands are the only thing anyone ever contributes, it's not hard to see why one might just take the money and ghost.
A moment of respect for what jbk personally passed up to keep VLC free for us.
Comments like these never fail to bring a smile to my face. Someone who doesn't understand the project / issue decides it is easy and people should care about their personal grievances for a program they have not paid a single cent for
Just because it's an OSS project does not mean it's beyond reproach. I contribute free software myself and never once felt that I was above my users. I don't think the VLC guys are this way one bit, but your suggestion that I should not be talking about any of my minor gripes is ridiculous.
Just an analogy... Suppose on a nice summer sunday afternoon, you are walking or cycling on the country side. You come past a farm, and they have free apples on the side of the road that you can take with you. You pick one, but find that there is a bad spot on that apple. First thing you do is throw it against the front wall of the farm. The farmer comes outside and you tell him he should be more carefull in picking apples, it is easy to do that and won't take much time. Next week you are there again, and there are no free apples anymore.
I’d say there seems to be far less interest in improving, in particular, the UX (not even UI, but UX specifically) of usability disasters like Gimp or Blender.
I’m hardly ready to give Gimp another shot - I doubt, at this point, either of these releases will phase me or my use - I’ve simply been too disappointed with them both for more than 15 years of trying every new version, that they would probably literally need a new name to get me to use them.
I get a bad taste in my mouth when I think about Gimp or Blender - I unfortunately only have terrible memories of frustratingly trying to do basic tasks like make a selection or move an object around, to the point where I hear the word ‘Blender’ like I’d hear the word ‘Wasp’ - a little cringe of bad memories and something to be avoided.
I think it’s been almost 18 years of trying Gimp on a yearly basis on multiple platforms only to be baffled how rudimentary user-level functions are so fundamentally broken.
It must sound like I’m really bashing this software, and I’m not - I am appreciative of everyone who puts an effort into the important and often thankless work of FOSS - but part of the point of the FOSS movement is to demonstrate its feasibility to replace the equivalent paid software. This is also critical to its growth, evolution, and support. Firefox, VLC, and, to an extent, OpenOffice, have achieved this tremendously.
Due to the overwhelming complexity of the tasks it sets to achieve, Blender’s usability atrocities can be pushed aside. Not so with Gimp.
OpenOffice, for example, is somewhere in the middle, but both ways - the functionality and the UI/UX are both ‘good enough’, and I can hand it to my Grandma instead of Word and she will hardly notice.
I think the major point for me here, is that this is why there’s an age old saying that FOSS is made by geeks, for geeks, and we will never have ‘the year of Linux’.
That’s because usability these days is basically on par with functionality, because with so many frameworks and software options available, even if something half-works - people will still prefer the half working, usable thing, to something that works great and literally seems to change its mind on what function does what depending on some extremely random-seeming context.
Photoshop’s UI/UX is shit to start. I’ve often stated it’s a piece of software you must have someone basically show you the first time how to use - then it’s okay. That we have only this to really compare Gimp’s state of awfulness to, indicates, unfortunately, the depth of the shithole Gimp’s UX is really in.
I’m a UI/UX dev, and I find these pieces of software unusable, and, perhaps especially due to my education on the subject, actively frustrating to try to use - I pray to think what would happen if I gave, let’s say, my girlfriend, who does Photography and Graphic design, a copy of Gimp to replace Photoshop. She’d probably leave me for even putting her through the experience. /s
Again, though, OpenOffice vs. Word? No problem.
tl;dr: Usability has to go hand in hand with functionality in development, or there is a risk in the brand simply becoming a ‘bad name.’
If Gimp 3 might actually be usable, I’d personally go for a name change. I see people in IT visibly cringe when I mention it.
Very few UI/UX people do, yet they love to complain.
This has been fixed in 3.0.7 (now, it increases a delay between successive failures).
VLC 4 has a new "player", but the behavior to fix this issue is exactly the same.
Tguillem implemented it in the player: https://code.videolan.org/videolan/vlc/blob/8fc06287a82f3f23...
And I implemented it in VLC 3: https://git.videolan.org/?p=vlc/vlc-3.0.git;a=commitdiff;h=d... https://git.videolan.org/?p=vlc/vlc-3.0.git;a=commitdiff;h=1...
This is implemented that way because retrying indefinitely may be the expected behavior (so we may not stop), we just avoid busy loops.
Btw, you should upgrade: http://www.jbkempf.com/blog/post/2019/VLC-3.0.7-and-security
That said, VLC is still pretty good. It handles the various webm, mkv, mp3, mp4, plus whatever else I've got floating around in /home without losing a beat.
I’ve never opened media files from a command line, personally.
The ‘Swiss army knife’ approach is why I love VLC - the knowledge I can throw literally any file at it and it will just open is very satisfying. iTunes/QuickTime just don’t make that cut, even with Perian. (is that still a thing?)
Then how do you open media files? /s
100,000 hours spent on programming the underlying features, 0 hours on actually making it usable.
That which is asserted without evidence may be dismissed wihlthout evidence - or, in terms which may be more paletable to some: lol, no u.
I use it every day for professional work, so, yeah no.
> 100,000 hours spent on programming the underlying features, 0 hours on actually making it usable.
Clearly you meant to say "0 hours spent learning it" there, right?
Bizarre keyboard shortcuts, awful ‘stay-on-top’ window behaviour when tabbing between applications. ‘Copy’ copies the inversion of the selection by default. Dragging a selection drags the rest of the image. The default behaviour of most tools is inverse to any previously established behaviour.
I’ve used Gimp thousands of times over 15-some years, in some cases for professional projects, and under the hood it is very good, but for many years it’s UI/UX made it literally the most bottom rung tool I would possibly choose to use for graphics manipulation - only when I absolutely had to. (I remember using Gimp in between the PowerPC -> Intel transition, where CS2’s performance on my Intel Mac Pro was worse than my iBook, and Gimp had a Universal Binary before Adobe did...)
I learned GIMP, through tooth and nail, and, knowing it well, I can still say through and through, especially historically, Gimp has been nothing short of a mess to use. I’m still not used to the idea that selecting and dragging something moves the rest of the image, not the selection itself.
I don’t want to learn to make an exception for Gimp as opposed to every other graphics application on the planet I’ve used since MS Paint, and I am certainly not the only individual criticizing particularly the glaring UX issues within Gimp.
Now, Blender, I’ve tried to take a dozen or so YouTube tutorials, and read dozens of articles on, and it just makes me want to hurl my MacBook Pro across the room every time. I was never able to accomplish anything serious in Blender the way I did with Gimp, which is why I put Gimp as the second worst UI/UX I’ve ever tolerated.
Unless there is an actual use bug, like things do not work, for high value software, it pays to just work the thing the way it works.
All improvements welcome, of course. And the interesting there is I hope they are good, not just a pretty pass, or rearrange. That takes time to remap. It is nice when it is time well spent.
I tend to give a wide berth to high value tools I get to use gratis.
Perhaps a better UX can be funded somehow.
‘Selecting selects the opposite’, is, to me, a use bug, among with many other designers and developers (a quick Google search confirms this).
I wish I had the time myself to go in and look at it, I really do. I’m sure it’s the same for a few folks. I love and support FOSS and I wish I could get behind GIMP like I can VLC.
But VLC managed to make itself a daily driver, even from this interview’s description, by being usable.
Gimp isn’t usable unless I’m going to dedicate myself to it. Functionally, there’s no reason I can’t use it and Photoshop interchangeably for the same task.
But when that same task takes me two or three times longer because I’m fighting with the UX, and design time is money, Adobe can unfortunately take my money for now.
Most of us have seen it all done a bazillion ways. I go all the way back to floppies, TV for a monitor and separate application and data disks.
Even a lame UI is presenting me with fast, potent tools!
If there is value there, the learning follows, then stuff gets done, next. It is hard the first few times. Easier after that. Almost no worry now. "How does this one do it?" K, next, done.
Hard to complain about pretty great tools I can use, modify, etc. for a song and small investment in how the tool works.
Or don't, right?
Adobe is happy for your money, and parting with it is worth more than some time sorting GIMP out.
No worries.
It is easy to create a tool that is specifically tailored to your workflow, because for parts that may tough to code, you manually take care of it. It becomes harder to generalize that tool for public use. It is harder still to add good UX that lets novices pick it up and begin working.
It seems easy, because the ubiquitous tools, libraries and frameworks have years of planning and experience to learn from.
In fact I've found that a lot of the professionals that refuse to go near the OS version are a hell of a lot less skilled than those that enjoy the benefits of the GPL'd versions.
Open Source apps are very popular in enterprise and professional circles.