13 ms·
- GNOME forced on people, the things that come to mind was pushing of tech like Wayland that makes it hard for little DEs. As for the default I remember clearly
by simion314 5y ago
- GNOME forced on people, the things that come to mind was pushing of tech like Wayland that makes it hard for little DEs. As for the default I remember clearly a giant anti_unity mob , there were some big Youtube channels giving Ubuntu and Linux a chance and the GNOME fanboys popped up in chat and convinced the dudes to purge Unity and install GNOME, this was idiotic because it was not a correct procedure so they created a broken Ubuntu and gave Linux a bad image.
About the "vision" comment, at my work there is always a support team, they get feedback from users and we never give a response "it is our designer vision or our dev leader vision that things are like this". The differences are that
1 we care for each and even one of our users so we never say "go use our competitors because we don't care about your problem"
2 we do not have a big birocracy or a tyrant with a big vision, so we can think for ourselves, propose solutions and implement them. Sure it happen that later the designers demand we simplify the GUI but we know that each complex feature is still used by some power users and w propose ways to keep it in, but more hidden so designers don't complain.
Maybe GNOME does not have enough money for their big ambitions but they have a lot more then other DEs.
My summary would be, vision is fine in your hobby toy project, GNOME, Chrome, Apple's OSX are not toys, if you do a radical change only based on a dudes vision IMO you are doing it wrong, you forgot about the users and are only thinking at your ego/CV.
- md8z 5y agoI don't understand what GNOME using Wayland would have to do with any other DEs, those DEs don't really have to use Wayland if they don't want. Although they probably should for technical reasons. Also I don't think any youtube videos were a particularly big factor in the decision, Mark Shuttleworth said it was because of money: https://www.omgubuntu.co.uk/2017/10/why-did-ubuntu-drop-unity-mark-shuttleworth-explains https://www.omgubuntu.co.uk/2017/10/why-did-ubuntu-drop-unit... "About the 'vision' comment, at my work there is always a support team, they get feedback from users and we never give a response 'it is our designer vision or our dev leader vision that things are like this'." Yeah you may not actually say those words exactly but I've many times heard support staff essentially state the same thing. They might say "sorry the product is not designed to do that" or "we don't sell that here", e.g. if you go to a car dealership and what you really want to buy is a helicopter, they will say sorry we don't sell flying cars, these cars were not designed to fly. Maybe they don't use the word "vision" but it's all the same, if you decide you are going to build a car a certain way then you have to stick to that, once you decide to add helicopter blades then it's a different product for a different market. So you could just exchange the word "vision" with "plan" if that helps to understand it. For a big project, yeah, they can obviously afford to do more and to put more features in a product but they still have to draw the line somewhere.
- simion314 5y agoYour example with cars is flawed when you are talking about 1 having the thing but hiding it for Windows or Linux users because "vision" 2 having the thing, everyone else having same thing but you remove it because of vision. So is not about just 1 dude demanding Gnome or Chrome to add say something weird like "vim" keyboard support , but many users asking something basic present in similar products and in previous version of same product or for the Chrome issue I mentioned the feature is visible but only on Mac. Btw I appreciate our conversation, is refreshing to disagree with someone that puts effort int he comments and is maintaining respect, thanks EDIT: about wayland, we will have to disagree, in my opinion Wayland could have been implemented much better like 1 have a protocol 2 implement this protocol and share the implementation with all DEs, like Xorg , so only say Rust guys could have a go and create their own version in their cool language 3 define the extensions and implement them, not do "X11 did this but it is stupid, it is not our job, go figure it out yourselves"
- md8z 5y agoI don't really know the details of this but for some things it is non-trivial to ship even small changes on other platforms, even those will have to go through full dev-test cycles which takes time and money. About removing things, I don't know, I had a car once that had some really nice cupholders. Really deep and exactly the right size, exactly at the right height for the arm. My current car doesn't have them and I can't find any cars that have that were quite as good as that. They just stopped making them. If that's not "vision" then what is it? I mean somebody has to make the decision of how to make the new cars. There is also the question of, do I value cupholders over everything else in the car? Would I buy a car with terrible steering if it meant the good cupholders? If I could get the good cupholders in any car would I pay an extra $3000 or however much the dealership charges? I think probably not but it really depends. So there's many factors at play here. Edit: Or say maybe I am a startup founder and I design and build my own car exactly how I want and turn it into a company. It's perfect for me but then someday I get bored of driving my car and I retire. Then I hire someone else to design the cars and pass responsibility on to them and they change some stuff. Well, now the cars are different and everyone pretty much has to accept it because the original designer is gone, and as much as people liked the old one, nobody else can really copy them exactly because it was really their personal vision that made it what it was. For Wayland, I think all of that is happening already? There is somebody making an implementation in Rust. They did try to make a shared implementation (Weston) but it turned out that people didn't actually want that, they preferred to write their own implementations.
- smoldesu 5y agoWell-put.