Originally posted by Kano
View Post
Announcement
Collapse
No announcement yet.
How to help / support Linux ? - your idea's
Collapse
X
-
Originally posted by ?John? View PostI completely agree. The real question is "What's the route cause of the problem (if the relatively small market share even is a problem)?"
I would like to get one thing straight though - we obviously disagree about this, but there's definitely no reason to insult each other. I was simply presenting my opinion on the matter and tried to support it with arguments based on the view from my own perspective. If you believe I have insulted you in any way in the process, then I'm really sorry, because I definitely didn't mean to. My opinions are never final before it's proven beyond any doubt that they're right and I'm more than happy to correct them accordingly when I'm presented with relevant evidence before that happens. I honestly believe you should start treating your opinions the same way instead of calling the thoughts of the others "diatribes of drivel" because it defeats the whole point of any discussion if you don't.
I believe there's no point in continuing this dialog unless you realize what I'm talking about and start treating other members of this forum with appropriate respect.
Most people don't know how to get to work if you ask them for directions, what makes you think we are going to fix the other bad habits they have. That is the key and fundemental difference between MS and Apple and most of the OS community.
Comment
-
Originally posted by Kano View PostI do not fully get the coincidence between stable drivers and open source drivers. I had several ati cards which had several problems with open source drivers. Even with open specs it does not mean that everything works.
Originally posted by Kano View PostIt is more a psychological aspect that somebody prefers open source.
Ask yourself if the hardware manufacturers can really be trusted to keep providing their customers with stable and secure drivers, able to make the most of their hardware (both efficiency and feature-wise), as long as they need and all things considered, the obvious answer seems to be "most likely not."
Take GPUs as a classic example:
Is AMD making sure that those who need it can keep using the last fglrx version working with R5?? and older GPUs? No.
Never mind - not every GPU manufacturer out there is doing the same. For example nVidia's blob for legacy hardware still works with latest kernels and X servers. But do they keep actually maintaining it (actively optimizing it, adding new features relevant to supported hardware and scanning the code for security)? If they say so, what makes you believe them (at least for stuff that isn't trivially visible to end users)? And even if they really do, how much longer are they gonna keep it up?
Remember the saying "If you want something done right, you have to do it yourself"? I believe it's based on a bunch of very good reasons, at least as far as my experience can tell.
Needless to say this problem is nothing specific just for GPUs, because various degrees of closed code breakage seems to be virtually ubiquitous throughout the ICT industry as firmware, blobs, operating systems and applications all tend to go completely haywire from time to time (definitely much more often than I consider acceptable).
Originally posted by deanjo View PostYup, that is pure truth especially as devices get more complex.
Originally posted by Thatguy View PostKeep in mind that the developers job is to make the computer accesable to the users, not the other way around.
Most people don't know how to get to work if you ask them for directions, what makes you think we are going to fix the other bad habits they have. That is the key and fundemental difference between MS and Apple and most of the OS community.
Comment
-
Originally posted by ?John? View Post
I tend to be rather pessimistic when it comes to trying to estimate the chances of correcting any flaws of human nature. The problem is obviously on both sides and all I'm trying to say is that I'd hate to see us screwing up technically superior solution to any problem just to make up for the incompetence of it's potential users.
In most ways concerning the users Mac OSX and Ms Windows are vastly technically superior to linux.
The question becomes, how do you want to define your argument. If the system has incapable users by and in large due to intellegence or lack of apptitude, it must adapt or it become inferior to other systems.
Regardless of performance or liscensing arrangments.
Comment
-
Originally posted by Thatguy View PostTechnical superiority is a matter of perspective and is relatively case based.
In most ways concerning the users Mac OSX and Ms Windows are vastly technically superior to linux.
As an engineer I tend to emphasize what's hidden under the hood and the resulting real-world experience when evaluating technical superiority.
I don't want to go into much detail here as that would probably become grounds for further misunderstanding, but believe me that both me and those following suit can see a big difference (mostly for the better, otherwise they would be back in no time) after moving to Ubuntu.
Let me just say that GNU/Linux could use a complete overhaul of GUI subsystem (already being worked on and I'm really curious how Wayland pans out as KMS and Gallium3D already rock), much more standardization (for example userspace environment and unified package management - both in terms of package format and dependency structure) and Winblow$ should really get rid of registry, the tendency to have almost everything hardwired (including vital stuff) instead of being able to dynamically adapt to changing environment and most importantly trying to keep backwards compatibility at all cost, resulting in all sorts of dirty mess.
Originally posted by Thatguy View PostThe question becomes, how do you want to define your argument. If the system has incapable users by and in large due to intellegence or lack of apptitude, it must adapt or it become inferior to other systems.
Whatever happens to GNU/Linux in the future, I really hope bringing more people aboard won't make it become just a free (as in price) replacement for MAC OS or Winblow$. That said, I'm always happy to see someone bringing over anything good and maybe even taking it a few steps further - for example I just love how Winblow$' GUI subsystem is able to switch GPUs or even fail and recover without the user even noticing and I can't wait to see that coming.
Comment
-
Originally posted by ?John? View PostDefinitely. I keep saying that it's always a matter of respective user's perspective.
As an engineer I tend to emphasize what's hidden under the hood and the resulting real-world experience when evaluating technical superiority.
I don't want to go into much detail here as that would probably become grounds for further misunderstanding, but believe me that both me and those following suit can see a big difference (mostly for the better, otherwise they would be back in no time) after moving to Ubuntu.
Ubuntu hopes to reduce the fracturing in the API and the ABI that is just plain retarded. One of the giggest problems is that release quality is not prioritized over release quantity. Ubuntu is likely one of the best versions of linux out, yet it has problems with abi and api. To many tool chains kit etc. Instead of making 500 half assed versions of damn near the same thing, make 1 or 2 really good versions instead.
Originally posted by ?John? View PostLet me just say that GNU/Linux could use a complete overhaul of GUI subsystem (already being worked on and I'm really curious how Wayland pans out as KMS and Gallium3D already rock), much more standardization (for example userspace environment and unified package management - both in terms of package format and dependency structure) and Winblow$ should really get rid of registry, the tendency to have almost everything hardwired (including vital stuff) instead of being able to dynamically adapt to changing environment and most importantly trying to keep backwards compatibility at all cost, resulting in all sorts of dirty mess.
Originally posted by ?John? View PostIf I didn't make myself clear by now, adapting for the needs of incapable users more than what is healthy and reasonable (which is a very thin line to cross) is exactly what I'm so afraid of, because the system going down that road is bound to become a total disaster.
Whatever happens to GNU/Linux in the future, I really hope bringing more people aboard won't make it become just a free (as in price) replacement for MAC OS or Winblow$. That said, I'm always happy to see someone bringing over anything good and maybe even taking it a few steps further - for example I just love how Winblow$' GUI subsystem is able to switch GPUs or even fail and recover without the user even noticing and I can't wait to see that coming.
Let me rant back here for a minute. As a example of a WTF is wrong with linux developers.
Application names.
Why is a photo editing and image art creation tool called gimp. WTF. Why not call it Free Art and Image editor. Or something else. One of my big annoyances is WTF is that program and is it any good, will it break the rest of the OS by overwriting various libs.
the list of annoying crap like that is pretty long. Obscure or obfuscated naming shcemes. Why does VLC have a traffic cone for a icon, wouldn't a dvd or video tap make alot more sense.
Not only does the application name give no information about function but the damn icon makes no sense either.
thens there bash with its bizzare function name.
shit like SUDO etc.
not to mentions settings etc that are the same damn way. So not only can things be hard to configure but the naming schemes make it worse.
Its not always about dumbing it down, but providing a logical application and configuration naming scheme.
for instance Grub.
WTF
how about
Bootmanager or something similar. GRUB WTF does that mean anyway ?
its bigger then a few gui tricks its a gui and useability problem from naming on up.
Comment
-
Some more examples can be made too, like a window with four colors representing an OS, or a guy with two faces and a big nose representing the MacOS.. Also Chrome and Safari has to do with the internet?
I also can't believe that "Starbucks" is a place you go to get coffee, and that their logo is a mermaid with a ring around it
..
Okay, I just did a quick google search which revealed that:
GIMP stands for GNU Image Manipulation Program
sudo can be interpreted as "Substitute User DO [command]"
GRUB means GRand Unified Bootloader
What can I say? OSS community likes acronyms. It's culture. And it's nice
Comment
-
Originally posted by renkin View PostSome more examples can be made too, like a window with four colors representing an OS, or a guy with two faces and a big nose representing the MacOS.. Also Chrome and Safari has to do with the internet?
I also can't believe that "Starbucks" is a place you go to get coffee, and that their logo is a mermaid with a ring around it
..
Okay, I just did a quick google search which revealed that:
GIMP stands for GNU Image Manipulation Program
sudo can be interpreted as "Substitute User DO [command]"
GRUB means GRand Unified Bootloader
What can I say? OSS community likes acronyms. It's culture. And it's nice
When you look at a icon it should embu the viewer with the purpose of the program it is attached, a box of crayon, a video dvd, a pair of scissor, a typewriter.
Icons are visual identifiers and without them being properly assigned most people mentally revolt.
Comment
-
Originally posted by Thatguy View PostApplication names.
Why is a photo editing and image art creation tool called gimp. WTF. Why not call it Free Art and Image editor. Or something else. One of my big annoyances is WTF is that program and is it any good, will it break the rest of the OS by overwriting various libs.
the list of annoying crap like that is pretty long. Obscure or obfuscated naming shcemes. Why does VLC have a traffic cone for a icon, wouldn't a dvd or video tap make alot more sense.
Not only does the application name give no information about function but the damn icon makes no sense either.
thens there bash with its bizzare function name.
shit like SUDO etc.
not to mentions settings etc that are the same damn way. So not only can things be hard to configure but the naming schemes make it worse.
Its not always about dumbing it down, but providing a logical application and configuration naming scheme.
for instance Grub.
WTF
how about
Bootmanager or something similar. GRUB WTF does that mean anyway ?
its bigger then a few gui tricks its a gui and useability problem from naming on up.
GIMP = GNU Image Manipulation ProgramGRUB = GRand Unified Bootloader
SUDO = SuperUser Do
Here are a few more you to grasp
CPU = Central Processing Unit or do you think that should be called "The Thinker"
RAM = Random Access Memory or do you think that should be "Stuff that I was told"
VLC's icon is a bit of an Easter Egg. The cone icon used in VLC is a reference to the traffic cones collected by Ecole Centrale's Networking Students' Association.
As far as worrying if installing something will overwrite various system libs that is not really a concern. Package managers do a very good job of managing that.
Part of the joys of programming and developing is to add a bit of personality to your project and often that involves application naming often poking fun at themselves. A good example of those would be like WINE, YaST, YASM. Years ago I co-developed an application that used to restore frequency information taken from sub harmonics in music that were lost in the recording. We,with tongue in cheek. called the the algorithm S.H.I.T. (Sub Harmonic Interpolation Technology). We had a great time telling people that S.H.I.T. made their music sound better.
In short, your rant sounds like an excuse to just bitch.
Comment
-
Originally posted by deanjo View PostLMFAO, so I suppose your pets are named Cat, Dog, and Fish. What do they call you? Human?
Now on a more serious note, that user has a point when in regards to certains aspects of the operating system. Some generic functions should have a meaningful name and icon, like "control panel", "system settings", etc (1)... but when it comes to applications it doesn't make much sense, or else we would have Text Editor, Another Text Editor, Yet Another Text Editor, That's Right This Is One More Text Editor, The Greatest Text Editor Of Them All.
Back to the OP, I found out that contributing to open-source is more difficult than it seems. A while back I made an init script for transmission-daemon in openSUSE 11.3 since the package didn't include one, nor was there one available on the transmission website. I contacted the transmission authors who told me that, if I wanted to contribute that init script I should talk to the distribution's package maintainer and not them (2). I talked to someone (can't really recall who it was) on the openSUSE's package maintenance side that told me I should talk to upstream and not them... Basically I got kicked around and no one cared about my init script. I guess I'm probably the only person using transmission-daemon with openSUSE. Anyway, if anyone knows the correct way to contribute to an open-source project I'm all ears (eyes?).
(1) This is already taken care of in most modern DEs.
(2) Note that they have init scripts for some distros on their site.
Comment
Comment