06.08
It’s funny how something as utterly basic as the position of the window decorations can cause such massive arguments. What I really learned is that having such discussions is entirely pointless. The advocates are going to get upset, confusing criticising parts of Linux with criticising all of Linux and realistically the people who already agreed with me agree with me and the people who don’t skim read it and then call me an idiot. Simply put, it’s not exactly productive.
But I am sure everyone can agree that Linux usability could do with a bit of work. Obviously so does Windows and OSX too – the idea of ‘perfection’ in a UI is ludicrous considering the constant changes in use-cases and hardware. I can’t help but feel that Linux is getting left behind though and the people making a lot of these UI choices are perhaps not the best people to be making such decisions, but in all truthfulness I don’t really have the right to tell them what to do. Who approved my credentials after all?
So here is my idea. Make a non-existent Linux distro. That is appeal to people that are interested in usability, UI design and graphic design. Through a process of debate and discussion create a virtual ‘dream OS’ concept. Reconsider everything. Do not start out with Gnome/KDE and go from there. Re-examine every assumption about the current desktop situation and then create a series of mockups with HID guidelines, behaviour guides and working prototypes (do it in Flash even). Maybe create a few ‘best of breed’ applications also, such as a media centre, a basic word processor, that sort of thing.
My thinking is that in traditional FOSS projects there is two main motivations, the ‘fun’ of creating something new and the satisfaction at creating something good. Since UI designers do not often make good programmers and programmers working (often for free) would not be willing to take directions from someone else, reducing them to a cog in the machine, usability often suffers. By providing a template though the second reason ‘creating something good’ would still be valid. After all many FOSS projects are just reimplementations of closed source software – most FOSS games are this way – but people still make them.
It would also be a good way to entirely sidestep historical inertia associated with most decisions. Large swathes of UI decisions and placements are only there because they have always been there, and the only reason they were there in the first place is because it seemed a good idea at the time. Projects such as Gnome are like a supertanker with years invested in the particular direction and the people working on it are so close to it, so familiar with it, that usability criticisms with it are often simply not seen. I remember when I first got my Android phone I spotted so many usability issues with it, but now I am so used to it that I cannot see them any more. By bringing in people that understand the subject but are not ‘tainted’ with deep knowledge a fresh perspective can be gained.
This isn’t a new idea – I’ve been thinking about this for quite a while and have the overarching structure and methods to doing it fairly well thought through and I honestly do think it is feasible.
So if you are honestly interested in getting involved in something like this please let me know at kerberos at piestar dot net.
I don’t think this would work because like anything else, usability needs to be tested. You can’t give your granny a fictional distro and then learn from watching her use it. The existing distros are the usability tests and their creators already won’t listen.
Of course there are things like Vi which are a completely different UI and it’s attempt to make you rarely leave the homerow really does work; once you’ve learnt it. But the learning curve is so high is it really a good UI? There’s a lot to be said for actually keeping things the same even if they’re not optimal. I mean, I’m so used to ecommerce sites with the search box top centre that I sometimes miss the small search boxes on the right of many WordPress blogs.
I’m pretty sure Microsoft and Apple are already doing your basic idea, but with actual working OSs and real user testing and more money than any of us could hope for. If they find something good I’m sure they’ll implement it and Ubuntu will rip it off quickly enough anyway, so why bother?
One thing I’ve learnt from my years as a Linux user is that even the most honest, well-intended projects will falter simply because of the ideological baggage Linux carries. What you suggest is a grand idea, Kerberos, but lots of others (including myself) have suggested similar improvements and have promptly either been shot down or given up in frustration.
I’ve reached the inescapable conclusion that: 1) Linux is unchangable unless the inherent ideology is ditched and 2) the inherent ideology cannot be ditched.
Wiping the slate clean will be seen as unnecessary, because Linux is already perfect. Any attempt to build on an idea from Microsoft will be seen as heresy, because anything MS does is a bad idea and automatically corrupt by association. Any improvement put forth will be seen as a personal affront and rejected. Even if a new project moves past the above obstacles, it will stagnate as developers lose interest and get frustrated with the attitude of the Linux crowd. They’ll divide into camps of pro- and anti- users and call your product bloated, a black eye, etc.
It’s hopeless.
@Kyle:
While I do agree usability needs to be tested, it should be the last step rather than the first. I’ve seen the FOSS crowd plan (and even do) all sorts of usability testing but they don’t need to as the current issues are so glaringly obvious but they don’t seem to appreciate the issue and are seeking a technical solution to a non-technical problem. I think you can get 95% of the way there without user testing and then working mockups should expose any serious issues.
@Delano:
The idea is to ignore the Linux baggage entirely, to ignore the current system and start the project as new. Actually getting it coded is not a concern and actual programmers will have no real place – that will all come later (if at all). There is no room to get ‘shot down’ as there will be nobody above dictating anything. Anyone acting like a zealot or troublesome can be dealt with. It’s an entirely independent effort who’s results are free to be implemented by anyone who wants to, and a place to discuss usability issues without the zealots. Even just gathering people together with an interest in Open Source and usability would be nice.
Isn’t this kind of what Ubuntu Brainstorm is for?
I hate to be the nay-sayer every time when the subject of Linux is brought up, but I guess that’s just dirty work that someone will have to take up doing anyway.
To me, your idea of a Linux UI mock-ups community is just nothing more than a UI equivalent of a TED conference. Yes, there will probably be nice ideas here and there, but who is going to take up materializing them at the end of the day? Commercial OS developers? Their lawyers will certainly not be too comfortable about that. Hobbyists? Forget it. And I am only saying this basing on the assumption that your infinite monkey community – if you get my drift – will actually produce something useful rather than the usual sweet nothing that we get from similar settings. People aren’t perfectly impartial creatures. They lie, they spin, and they are collectively prone to herd mentalities. This is why the majority of the Linux communities that we see today are more the epitomes of all the TMs in the Repository than the gateways to technological achievements that they want see themselves as, and this is why the pragmatists among us have long lost interest in making a difference in the so-called “open source” world and just leave problems like software design and development to those having both the incentives and resources to look after.
The problem, in summary, is not about whether the glass is half empty or half full, but whether there is anything worthwhile doing with a 99% empty glass holding 1% of undrinkable sewerage. I am sorry, Kerkie, but I think you have really lost the plot this time.
So, not a lot of traction on this idea!
“So, not a lot of traction on this idea!”
I am afraid not, Kerbie.
Helping PC-BSD or Haiku would be a far better use of your time man, even if you managed to make this awesome GUI, it would still have Linux below, and all the problems associated with it, the community being the worse.
Note: I know that since it would just be a prototype, the dependency on Linux is irrelevant, whoever I certainly wouldn’t participate in this if Linux was the target.
“It” doesn’t want to be helped.
The problem is I have found going to these projects and saying ‘your UI/usability sucks’ never ends well and you always get bogged down (as stated above) by the zealots who want to defend everything. The aim would be to sidestep the whole mess and do what is needs to be done rather than fight from a bottom-up position for radical change.
“The problem is I have found going to these projects and saying ‘your UI/usability sucks’ never ends well and you always get bogged down (as stated above) by the zealots who want to defend everything”
Of course.
“The aim would be to sidestep the whole mess and do what is needs to be done rather than fight from a bottom-up position for radical change.”
I think everyone understood the idea.
Even the so called pragmatic hatetards want nothing to do with improving linux. Instead they just attack it. Again the M$ shills show their true aphiliation.
I’d be down, even though I’m something of a noob and not a developer or anything, but maybe that could be an asset. I assume the goal would be to design a GUI that’s accessible to somebody like myself.
At the very least, it could be a fun, interesting exercise, and maybe yield some unexpected and cool results. What’s the harm?
Then why don’t you join the project Adam? Make something useful for once, oh wait… Linux is perfect right? Then this project must be some kind of paradox to you or something, better not.
‘Make a non-existent Linux distro. That is appeal to people that are interested in usability, UI design and graphic design. Through a process of debate and discussion create a virtual ‘dream OS’ concept. Reconsider everything. Do not start out with Gnome/KDE and go from there. Re-examine every assumption about the current desktop situation and then create a series of mockups with HID guidelines, behaviour guides and working prototypes (do it in Flash even).‘
Canonical are already doing this, see: the last paragraph on Michael Forrest’s blog post:
‘So here I am. I’m back doing Flash (after a frantic couple of weeks trying desparately to find a better way to produce prototypes than with Flash). I’m making a fake version of Ubuntu in which we prototype user interaction designs [...]‘
and Flash-Ubuntu. The one big difference is that Canonical’s designs are hidden, not open for discussion.
It also seems most of the Ubuntu team use Macs, so I applauding their lack of Freetardery. However, it’s easy to see from whence the Mac influence on Ubuntu comes.
‘What I really learned is that having such discussions is entirely pointless. The advocates are going to get upset, confusing criticising parts of Linux with criticising all of Linux and realistically the people who already agreed with me agree with me and the people who don’t skim read it and then call me an idiot. Simply put, it’s not exactly productive.‘
It’s anecdotal but the evidence changed my mind and my wife’s (personally I liked the button positioning, before reading your post). What you have to remember is: out of all the people who read the article, how many commented one way or the other? Perhaps the majority read the post, thought, ‘Good point!’ and moved on.
Also could someone explain to me why every linux interface related project that seems remotely interesting DOES NOT HAVE SCREENSHOTS in it’s homepage? Why?
Enlightenment and ElementaryOS are good examples, if you want to revolutionize linux user interfaces, might want to start with something smaller like… making a proper freaking website.
I’m starting to quite like this Michael Forrest, he’s a bit of a fucking ponce, but he’s right about Linux:
‘My experiences with the Ubuntu codebase so far have been that far too much emphasis is being placed on how the machine works, with little emphasis on modelling the real world or coming up with APIs and toolkits that work nicely from a human perspective.
We have driver code with giant switch statements to detect pin configurations of different chipsets on different motherboards, with new lines being hacked in whenever a new laptop comes out or some manufacturer decides to cut corners by wiring some connector to pin 3 instead of pin 2.
At the other end of the spectrum, we have inflexibly hacked UI code where any change to a view requires changes in two other files, often involving adding in mappings that could be implicitly determined or even removed entirely with a better approach to templating.
The phenotypical results of the underlying architectural problems are rife. My file-system suddenly became read-only yesterday. I hadn’t done anything – I’d just walked across the room to talk to someone for two minutes. Sure, it’s alpha, but seriously… how could this happen? Another time, during a UDS session while listening to something in my headphones, not realising until somebody told me that, embarrassingly, the sound was also coming from my laptop speakers.‘
Sorry for the long copy-pasta, but he’s right-fucking-on about these problems IMO. Freetard developers spend far too long on ‘new’ and ‘cool’ (differentiation) than satisfying user’s basic expectations.
I completely agree with this post. Linux is completely unusable. I use it every day (Debian with OpenBox) because it’s light and fast, and my laptop doesn’t have a lot of power to it. But all I can manage to use it for is web browsing and word processing. Anything else, I end up breaking something, and the only solution is to copy and paste lines of code from a forum and hope it, at the very least, doesn’t break anything else. I use OpenBox because if there’s no interface, there’s no interface to worry about changing or breaking.
I shouldn’t have to do this! Next semester I’m going to be taking my Linux+ certification test! I know how to use Linux, I’ve been doing it for 5 years, but I still have no idea how Linux works. The constantly changing, constantly forking, bickering, 50 apps to do one thing, but zero apps to do 50 things. It’s the epitome of an anarchist-capitalist system: everyone does exactly what they want to do, with no rules and no one to think about but themselves, and if someone doesn’t like it… “develop it yourself (aka the market will take care of it)”. It’s not the open-source communist paradise the developers make it out to be. No one is thinking of anyone else. Take the GNU/Linux naming scheme. If Stallman REALLY cared about just making a decent piece of software that fulfilled his philosophy, he wouldn’t care about the name. Think about that.
Linux is dead, and it was killed by Linux developers. I’m with you to help create a new project, but like Kommentor mentioned, Linux isn’t the right place to start. Look at how Ubuntu’s being blasted, not for the UI changes, but just for the mainstream appeal of it.
I think ultimately the talk of linux is pointless. What you really want is a thought experiment in UI design. By billing it as Linux you lose the mindshare of all those people who think that Linux needs some tweaking to compete when this is not at all the case.
I can understand the underlining point of this post, Kerberos. I too was a Linux user once. I too acknowledge that there is good ideas in it and I too would very much like to salvage it. It too breaks my heart that the Freedomites took a good-intentioned idea and raped it with their ideology of exclusivism, lying and censorship.
But I’ve buried it. Linux is the house that is so infested with termites that nothing can be salvaged without bringing the termites back. It’s sad, but I’ve accepted it.
Maybe one day there will be a free operating system which, while not perfect, will be excellent for a large scope of people. Maybe this operating system will be not only developer-friendly but user-friendly too, allowing progression, taking constructive criticism and allowing a culture of solid interaction between users and coders.
But Linux is not this system, nor will it ever be.
I can understand why people might be reluctant, if not downright defeatist, but there seems to be a community of like-minded people here who don’t have any pretenses about Linux, who don’t dump disproportionate amounts of their identity and self-worth into an OS and who won’t mindlessly defend it against any and all criticism. That Linux community you always wanted? Well, guess what? We’re IT. And my guess is there’s even more of us out there who’ve been waiting for an opportunity like this.
If something were to actually come of this, then as long as the right people appreciate it, who cares what the freetard majority thinks? Why should we let their lack of perspective, their counter-productive screeching, their knee-jerk zealotry dictate what we do?
We all enjoy this blog for one reason or another; I’ve gained quite a few insights from it myself. Don’t we at least owe Kerberosa a brainstorming session? No long term commitment, just a brainstorming session.
A lot of bloggers dole out criticism, but how many actually invite you to participate in something other than commenting on it?
C’mon, just ONE brainstorming session.
What say you all?
I think the reason I proposed it as the ‘Non-Existent Linux Project’ was that Linux has the greatest marketshare and base so it would be more likely to get looked at. Also as people use ‘Linux’ as this all encompassing term (not just the kernel). In truth the actual OS is irrelevant – there is no reason it could not be Haiku. I like Haiku. Also any distro which used it would be tainted with the ideals of the project – a definite win. I suppose the correct approach would be to name it the ‘Dream Desktop Project’ or something. As far as Linux is concerned there is nothing I’d want to keep from it anyway, which probably makes it incompatible with the “Those that don’t understand UNIX are doomed to reinvent it” crowd. Either way the aim would be to demonstrate ‘this is how it should be done’ and if a Linux distro wanted to use it they would have to do it on our terms. Plus Linux is so entrenched in it’s own way most of the stuff is probably not even possible except after a partial rewrite.
“The one big difference is that Canonical’s designs are hidden, not open for discussion.”
Yeah, I even think they are paying that guy, yet creating a development process that is closed to anyone who would contribute their time for free. The mind boggles. He’s also starting from a broken system (Linux and Ubuntu) and saying ‘what do we need to change to fix this’. The fact they are ultimately beholden to upstream anyway makes any efforts on their behalf pointless – if they actually gave a crap they’d fork Gnome. As it stands all they can do is change the theme and move some buttons around – the important stuff is simply out of reach. The LHS button debacle also proves they have no clue what they are doing. Plus windicators are a stupid idea. It’s ironic that the focus on ‘choice’ prevents them from doing anything major as they will break all the other identical distros.
“It’s anecdotal but the evidence changed my mind and my wife’s (personally I liked the button positioning, before reading your post).”
My job is done then. I find after pointing out a few things like this people manage to break out of the mental model that things are the way they are because it’s the best way and instead start to see usability failings all around them – even in things such as washing machines, toasters and door handles. Is this the best it can be, and is there a better way to implement it?
So I am slightly more hopeful about this now. As was said above this community is built on criticism, rather than silence and praise, so hopefully a stupid situation can’t arise like in FOSS where it’s all about praise and sucking up with nobody daring to tell it like it is (as when they do the community and mods get them). Anyway I may develop them idea further – I’ll keep you posted!
@Kommenter:
Elementary OS looks good until you dig into it and realise it’s just Gnome with a OSX styled theme and a dock. ‘Cargo Cult Usability’ anyone?
I fear that you underestimate two problems:
1.) Who would care ?
As John Gruber put it years ago: “Unix nerds who care about usability are switching to Mac OS X in droves.” So the remaining Linux users are those who don’t care about usability (because they are technical enough to still use it, they use it out of ideology and / or they are cheapskates). And developers are by definition the worst: If you are technical enough to use vi or emacs, then usability is not an itch you feel any need to scratch.
2.) How hard would it be ?
No, good ideas are not enough, you need good data, too. Please read this post first:
http://blogs.technet.com/b/office2010/archive/2009/10/29/ux-research-tools-and-techniques.aspx
This should give you an idea of what is involved in UI research these days. Do you have a test place with an eye-tracking camera etc. ? How do you attract non-technical people as testers for a basically non-existing OS ? (Anybody caring to read your blog is surely not non-technical.)
Sorry, it really would be nice, but I can’t see how it could be done.
Greetings from the land of good beer,
Carsten
I don’t join the project because I already believe linux is perfect. You winbred hatetards bash linux claiming you only want to improve it but when the most intelligent hatetard on this blog tries to improve it you all say no. Obviously you have other motives, perhaps dealing with Ballmer’s cock.
Thanks, Adam, that was most enlightening.
And now back to the topic. Stung as I was by the suggestion that I didn’t read your previous post and just commented “me too,” I’m going to do something different this time.
Well, actually, I’m still going to say “me too,” but it’ll be different, because I disagree with most of the posters above. I think this is an interesting (if difficult) idea. Me too!
It doesn’t have to fit Carsten’s model of a complex usability lab, since it’s neither commercial nor part of academia. It doesn’t have to aim for 1% of the desktop market, or even 0.0000000001% of the desktop market. It doesn’t have to aim for any market at all. And best of all, there’s absolutely no point in using Linux as a base.
In fact, it wouldn’t be necessary to pick an OS as a base at all. What you’re looking at is a FOSS-esque collaborative project to “build a desktop from scratch,” except that it’s not really from scratch because you’d be using an underlying GUI framework. (You could reinvent that as well, but why bother?) Just pick a framework that works across OSes, and you’re there.
I’d be tempted by wxWidgets, but actually any one of the Web GUI frameworks (is Flash a framework? Can’t think of a better word) would do.
The problem comes when you have to deal with the management side, because frankly the open source model is a steaming pile of shit. Move the metaphor. It’s not a bazaar, it’s not a cathedral, it’s … the Knights Templar! Just make sure somebody is really in charge (vote them off if necessary), and that there’s an actual road-map — not a wish-list — with an identifiable individual responsible for each milestone. It’s a lot of work for everybody, mind. I’d seriously consider only allowing *retired* software engineers to apply, because at least they have the time.
And the great thing about the Knights Templar model is that you can sell the idea as the basis for Dan Brown’s next book, and bingo! You’re a made man!
Then again, I may be misinterpreting this idea.
(And by “software engineers,” I really meant designers and GUI experts and the like. The odd software engineer would come in handy for stitching things together and doing the drudge work like maintaining repositories, producing releases, and so on. This would be an utter inversion of the FOSS model, and not before time.)
“I’d be tempted by wxWidgets, but actually any one of the Web GUI frameworks (is Flash a framework? Can’t think of a better word) would do.”
wxWidgets wouldn’t be a very good idea, to really do this you’d have to drop lower and program it from the ground up, flash would work very well though, even if I hate flash.
Liked when it was made by macromedia, now it’s just awful (talking about the IDE, not the plugin).
Also as far a usability testing goes, they really exaggerate nowadays, I had an interface design class this semester and we had to do usability testing.
We had to measure the time it took for users to find stuff, compare the times it took for different paths to the same goal, calculate GOMS and KLM crap, make questionnaires stuff like that.
Of all that you know what was the most useful? Just talking to the person, listening to what they though, what could be improved, what they liked, what they disliked, what made sense, what didn’t.
Also, you don’t really need a camera, just log the users actions, could be easily made from a web interface.
Not as good, but still very useful.
Now that I think of it, this project does interest me, “Dream Desktop Project”, hehe, has a nice ring to it
.
@Kerberos
, guess that’s to be expected from anything Linux related.
Found more info about elementary os… It’s a total mac ripoff (including hiding the filesystem) with a stolen logo from enlightenment (I actually thought they used enlightenment at first since I can only find minuscule screenshots of that).
Just another useless “fork”… Disappointed
Knights Templar model – I like it!
I imagine one of the key ideas would be to have two groups of discussions, one anyone can join and one that is read only with applicants having to put forward a good argument as to why they should be allowed in. Plus a decision committee consisting of a small number of people who’ll ultimately get to decide on various issues if they get too contentious. I’d want it to be all about who can argue their case best rather than shout the loudest. Not that the read-only group would be too hard to get in to, only act as an idiot filter to stop newbies and trolls.
I also think (shoot me now) that the idea of a timed release (say every 6 months) isn’t so bad where by getting everything together and ready (in whatever way it is done) it would create real, tangible milestones and also provide renewed interest and give the impression of movement on a semi regular basis. You’re right, a roadmap is a definite necessity – I’ve been involved in enough projects to know that if you do not have a finish date you will never finish.
@Carsten Hardt:
I agree with the first point, the core problem will be getting people interested and involved. I do think this is unique enough to create some interest though.
As far as user testing is concerned, this should be the absolute last step rather than the first step. As Henry Ford said, ‘If I asked my customers what they wanted, they would have asked for a faster horse’, yet FOSS focuses on making dumb decisions poorly thought through and hoping that user testing will be some sort of panacea. Only when you are happy with everything yourself is it time to try it on users yet large swathes of FOSS UI’s don’t even pass a basic smoke test – see the LHS button issues. Most UI decisions can be argued through rationally but there is this belief that graphic design == usability and thus usability is subjective and as a result there is no ‘wrong’ implementation. Once you approach it from the perspective of there is such a thing as a plain bad implementation/decision then it all gets a lot clearer. But I firmly believe a well reasoned UI not user tested is going to be superior to a poorly planned but user tested UI, and on implementation (if it ever happens) then user testing can be considered. Plus the Flash/Whatever prototypes will allow basic testing anyway.
The ultimate problem with the FOSS approach is the ‘code first, plan later’ mentality. Early decisions will be made poorly and the effort required to change them gets greater the more you write until you are locked into a path that may not be ideal but the pain to change it may be too great. By planning absolutely everything first the whole mess can hopefully be avoided.
All we need is a name and logo competition and we’ll be 90% of the way done!
What’s the logo competition TM, is there even one?
You want a name for the project/team or for the end result?
Kerberos, I’d be interesting in helping out.
Kerberos, your idea is now doomed.
I’d suggest not going any further than mockups until you were sure everything was right. Something like Balsamiq Mockups is a good tool for that; Even Shuttleworth uses it. However, it too makes a lot of assumptions for its widgets, so I’d say one initial rule might be to only use basic boxes, lines and icons if possible.
A name should be easy to pronounce, have as few syllables as possible, be familiar and have some relevance to the system. Common pitfalls to avoid include using “OS” as a prefix/suffix, the use of acronyms and the use of “Linux” anywhere in the title. (Most people mispronounce Linux anyway, and the average joe doesn’t consider OS to be relevant. Acronyms have more geek appeal, unless it forms an already-existing word).
As far as logos go, similar principles apply; eye-catching and simple. Logos with Tux in them are severely overused, but any other animal will be fine… and an animal with some relevance to the OS will be even better.
A topic rarely covered in the Linux crowd is: who is your target audience? Throwing in OpenOffice, VLC, Firefox, Banshee and a couple of lame games doesn’t suddenly make Linux a “general purpose” OS. Nor does a couple of GUI configuration tools suddenly make it “suitable for the desktop”. From the very start, the user’s needs have to be taken into account and things need to be streamlined to make sure the user is spending their time using their OS instead of configuring and tweaking it.
If for no other reason, that link to Balsamiq mockups makes the thread worthwhile. Can I has it free for teh Linux render stationz?
Dunno about “target audience” as a block, but I agree it would be worth doing the Joel thing and “inventing” users, complete with pseudo-biogs. It’s a good approach if you want to be able to say “works for someone who can program Hello World, but not for Queefer.” (That, of course, is the rock-bottom know-nothing end of the spectrum, but you get my drift.)
The whole concept needs, er, a manifesto, however. I’d assume that everybody here has a different mental model of what’s intended. My mental model doesn’t actually involve real applications _at all_, although it would be nice to have a scripting language (hell, make it Javascript) to make pretty moving pictures when an “application” pops up. Assuming applications are supposed to “pop up.”
(FWIW, my mental model also involves dual monitors — one for the GUI itself and one to list running commentaries, etc. In other words, the second monitor “pretends” to be an OS.)
The thing to avoid is a RAD-style development where whole swathes of stuff get thrown away every month whilst people bicker about the exact shade of puce used for the windicators. Well, my experience leads me to run away from RAD for that reason; YMMV. Sadly I think Balsamiq is likely to lead in this direction, not least because of the round-trip between sketches and “implementation” and back again.
Note that a computer OS is the only thing that Richard Branson hasn’t sunk his clammy little paws into yet. Taking a leaf from Ubuntu’s tendency to rip off the Mac (badly), perhaps we could call the project “O’Virgin?” Our man’s already been to space…
@Kerberos: I agree that in the first phase of designing a GUI ideas + debate should be enough, but when it comes to refining (and we wouldn’t want something half-assed, that’s what others allready do
you need something more to find out which of the good ideas is the right one. I found the blogs of the Office teams quite interesting:
http://blogs.msdn.com/b/jensenh/archive/tags/why+the+new+ui_3f00_/default.aspx
http://blogs.technet.com/b/office2010/archive/tags/research/
Of course they pertain more to application UIs than desktops, but still they contain some interesting stuff. Yes, asking actual users must be an important part of the process,
no disagreement there.
Another observation: As someone who uses Windows almost exclusively today (after having tried most of the rest before) I was always a bit surprised about the way the *x-folks were raving about their virtual desktops. I could have used VDs on Windows almost 20 years ago, but I never bothered – the task bar suits me just fine. So what is the difference ? After a bit of reflection I got it: In Windows I use allmost all my apps in fullscreen – because they are designed to be used that way and because they are powerful enough to do the stuff I#m doing in one window. E.g. if I write something in Word and want to insert a complex diagram I just insert a Visio object and create the diagram in the Word window. Could I do that with OOo write and Dia ? (Rhetorical question)
I think this has consequences for the desktop design: If you usually work with “many little windows” (the Linux way, it seems) than VDs, window management and the desktop in general become more important. If you usually go with fullscreen apps (the Windows way, I am tempted to call it) then most of the time you just see your app and the taskbar (and you probably don’t want to see anything more from the DE) so VDs and WMs are a non-issue and the desktop is just one more place to start your apps in the first place. So maybe the first design question to settle would be: Do you want to design for “full screen” or “little windows” ?
Slightly OT: Here’s my personal pie-in-the-sky dream, feel free to pick any useful ideas you might find.
Assumption: I had the kind of money that Mark S. has.
Mission: Create a usable Desktop OS – just to show the Linux fanboys what they should have done. Avoid GPL software wherever possible. Make it marketable.
Name: Something simple, my personal favorite would be “Eagle”. (Probably allready trademarked)
As a base we need a kernel etc. – one of the BSDs should do. (Include OSS for audio.) We need an application framework, which should be .NET because it exists, isn’t bad (AFAIK it’s even pretty good) and there are existing applications. X11 doesn’t cut it, so create a graphic “layer” to sit on the kernel and provide the necessary services for the .NET framework. If QT provides any help with this, license it and use it.
Marketing, target audience etc.:
Once it runs Paint.NET, call it Eagle 1.0 and give it away to interested tinkerers / nerds. Once it gets actually useful and some ISVs have been persuaded / “bribed” to porting useful stuff, call it 2.0 and use it as the base for customized “appliances”, eg:
If we can get Cubase and some other stuff, create a HW/SW bundle and sell it to recording studios as the “Recording Eagle”. “Movie Eagle” for rendering, “Photo Eagle”
might be other applications of the same principle. Once games are written in .NET, maybe even a “Games Monster”.
OK, I told you it’s pie-in-the sky.
I’m all for the name. Here’s our revered founder: http://images1.wikia.nocookie.net/__cb20080726160048/muppet/images/thumb/4/41/Sam_myspace.jpg/300px-Sam_myspace.jpg
I don’t think you need a kernel. I don’t think you need an application framework. Those things can be integrated later. This isn’t a distro, it’s a desktop model.
On the other hand, you do need some sort of a graphic layer, and it clearly isn’t going to be X. Picking a suitable GAL (Graphics Abstraction Layer) might be a good start.
You also need a management structure, which is where we come back to the Knights Templar. And it’s going to be a full-time job for some, which means you either need Shuttleworth’s money without Shuttleworth, or, more practically, a small number of interested parties with the time to waste: probably retirees.
I’ve just realised that my mental model of all this is horribly reminiscent of Xerox Parc.
Who’s going to supply all the bean-bags?
I’ll be honest, I’m a bit skeptical. Not of the idea – I think it’s great – but in the sheer amount of work this’d probably take. Snow Leopard and Windows 7 have about 15 years’ worth of tech and experience in them. That’s how high the bar has been set.
I’m not trying to discourage – I just think the best approach to take here is what Apple did with the first iPhone. Decide on a core set of features, and do them well – *then* add the more interesting stuff.
I think you chaps are falling into the same trap Freetards do: worrying about the technical details when you don’t even know what your target market is and who your users are.
As for asking users what they want, Henry Ford understood what his users’ goals are, they want to travel from A to B, faster. Do you know what your users’ goals are? That is, the mythical users, not people who will use this UI research to build operating systems.
User testing wireframes and functional prototypes is good for getting users to concentrate on how stuff works, instead of how it looks; introducing user testing for this is one reason not to do it last. However, if by ‘user testing’ you mean ‘Freetards raising bugs’ then yes, I agree.
As for a name and LogoCompetition™, I’d hold off until you know exactly what you’re doing, although a couple of possibilities spring to mind:
Usable
Work (as in, get’s the fuck out of your way and let’s you work)
Spritely
Slight (as in, small and slender, but also a slight against UNIXtards and their stuck-in-the-1970′s era philosophy)
A simple description of what the project is for: Writing code is easy, creating a user experience is hard.
‘Eagle’ is a little generic, in my opinion, it doesn’t convey anything about the project. Good name for a release though.
Seems the WordPress spam filter ate my last comment. Kerbie, would you mind dredging through your spam to see if it’s there? Thanks old chap.
I’m not trying to discourage – I just think the best approach to take here is what Apple did with the first iPhone. Decide on a core set of features, and do them well – *then* add the more interesting stuff.
Agreed. It’s less about how the UI will look and more about how it will work and the principles it will employ. For example, iPhone guidelines dictate that switching between pages should always have some sort of transition effect; a slide, fade, flip, etc. This wasn’t done just to look neat, the principle behind it was so that people wouldn’t get lost.
For example, one one screen slides left to reveal another, when the screen slides right again, you know you’re back at the previous screen. No jumping, no jarring, no disorientation. These are the sorts of UX considerations that have to be taken into account, anticipated, tested and measured.
@Dr Loser: My weird dream was about creating a complete Desktop OS, so a kernel would be necessary. And of course money would be important – I’m not that much of a developer myself, and one guy would be too less anyway, so I would have to hire scores of them. Therefore the assumption I stated upfront: “Shuttleworth’s money without Shuttleworth”, indeed.
@Ken Ham: Completely agree with your point re. target market. Please allow me to repeat myself: If our hypothetical “targets” mostly use full screen apps, then the desktop itself is of little real interest. Look at Windows: All attempts by MS to do something with the actual desktop have essentially failed, nobody seems to care much about “Active Desktop” and widgets etc., most of us put a wallpaper of our choice and some program icons on the desktop and that’s it. All the “action” is in the taskbar and the start menu, and do we really want to put that much effort into improving just those ? However, a slightly more realistic target might be: “Linux users looking for a desktop that doesn’t suck”.
Two things that I would like to see in OSes, usability-wise:
1) During setup, a dialog where I can set the following (with sliders):
- Size of UI elements (fonts, icons, buttons etc.), from “I’m blind as a mole” to “20/20″. (Unfortunately, just changing screen resolution as we did in CRT days doesn’t work well with LCDs, and some of us are severely short-sighted.)
- Security and privacy, from “Just let me do everything, I’ve nothing to hide” to “Paranoid”. Default setting should be 3/4 to paranoid, with dire warnings if the users sets it lower.
- Assistance level, from “I know what I’m doing, spare me those explanations” to “Help !”
- Overall look, from “I want my Win95 look back” to “Gimme all that fancy bling !”
Of course, these settings should be respected by all apps, and they should be easily accessible after setup.
2.) An assistant within the file manager that would help you to do that kind of stuff the CLI fans allways blabber on about: “For all files that meet the following criteria (long list of file attributes), rename to …/ copy to …/ move to …/ delete / apply comand …”
“Two things that I would like to see in OSes, usability-wise:
1) During setup, a dialog where I can set the following (with sliders):
- Size of UI elements (fonts, icons, buttons etc.), from “I’m blind as a mole” to “20/20″. (Unfortunately, just changing screen resolution as we did in CRT days doesn’t work well with LCDs, and some of us are severely short-sighted.)”
Don’t really agree much with this one, i think the best way is for the font size that applications should use to be specified in the interface guidelines (and made dificult to change in the API), while changing the font size should be easy for the user (internet explorer style zoom button) and also possible per application (provided by default, the programmer should not have to code it in).
“Security and privacy, from “Just let me do everything, I’ve nothing to hide” to “Paranoid”. Default setting should be 3/4 to paranoid, with dire warnings if the users sets it lower.”
Not enough, use capabilities like: What can this program do?
And a bunch of default settings like:
Device Driver: Graphics Card
Web Browser
Instant Messenger
etc.
And what folders they want access to (like the downloads folder)
Programs can specify in the “setup” what they are. Users can modify the permissions themselves.
(microkernel fan)
If a program says it’s a device driver, it should be signed, if not, lots of warnings on screen and i mean lots, flashing red, and even then all it could hurt would be the specific device it targets.
No need to think monolithic here folks
“- Assistance level, from “I know what I’m doing, spare me those explanations” to “Help !””
Yeah this is a must, I hate when i’m being spammed with stuff, and I hate when i don’t get help at all, let me choose.
“- Overall look, from “I want my Win95 look back” to “Gimme all that fancy bling !”
Of course, these settings should be respected by all apps, and they should be easily accessible after setup.”
Also a must, one of them should be lightning fast (only 90º gradients, square shapes), the other should have everything but wobbly windows.
On thing that pisses me off in WPF is that a lot of controls don’t follow the windows standard look. Give me the freedom to make my program work the way I want, but don’t make me think about how it looks, it should look like all the other programs on the system. Consistency is good.
2.) An assistant within the file manager that would help you to do that kind of stuff the CLI fans allways blabber on about: “For all files that meet the following criteria (long list of file attributes), rename to …/ copy to …/ move to …/ delete / apply comand …”
Maybe something like Automator on Mac OSX?
@Kommenter:
(font size) “Don’t really agree much with this one, i think the best way is for the font size that applications should use to be specified in the interface guidelines (and made dificult to change in the API),”
That would be a prerequisite to make it possible to change that globally, yes.
“while changing the font size should be easy for the user (internet explorer style zoom button)”
The button would go where ? Systray maybe ? (I guess I could live with a button as well as with “my” slider, as long as the function is there.)
“and also possible per application ”
I’ve once had to change font sizes in Outlook
I would love to have one central place to change the size of stuff on-screen globally – and with a vector-based GUI that should be really easy. Per-app settings might be a nice addition, but not a substitute.
(security) “Not enough”
Once again, this should be an easy way to adjust stuff globally – of course there should be more “screws to turn” for experienced users / domain admins, but as a first rough setting during setup this would be nice IMHO.
Signed drivers ? Definitely.
“Consistency is good.”
Absofuckinglutely. (And I like buttons that look like buttons – something that seems to be out in Redmond.)
“Maybe something like Automator on Mac OSX?”
Why am I not surprised someone has allready come up with this idea, and that the someone would be Apple ?
“Why am I not surprised someone has already come up with this idea, and that the someone would be Apple ?”
.
They really do know how to make great interfaces. I’m getting one of the new 13′ macbook pro’s next week
I do need to laugh a little at the “Mac’s are overpriced” comments some people make.
I’ve actually tried to look for equivalente PC’s (and I do mean equivalent, battery life, build quality and size/weight are important as well), There were very few, and the ones i found were more expensive, or had shit battery life, or were a lot weaker.
Interesting isn’t it?
@Kommenter, when it comes to desktops they tend to be a bit pricier since desktops have more space and the parts are more commoditized. However, when you compare all the higher end laptops like the Vaio line, Dell XPS line, etc. They all wind up being about the same price and usually lack something the macbook has; Either it’s heavier, less battery, too thick, etc.
This was my experience as well when I did my due diligence prior to getting my MBP. I’ve been extremely happy with it with the one exception is they nickel and dime you for mini-DP output adapters. The one thing I would say is that my previous laptops all had a tendency to crack. The aluminum doesn’t crack but can get dirt ground in. This is better for me, but something to take into consideration.
Most laptops get dirty/worn eventually, so I guess that’s one trait Apple overcharges on; They’re one of the more expensive brands to get dirty
They sure do use the DisplayPort to rip you off.
Standard DVI (HDMI really if you use the adapter) 1GB 4870 = £122.99
1GB 4870 Mac Pro “upgrade kit” with a mini-DP = £286.00
Their whole desktop line costs 2-3x more than you’d expect. When it comes to laptops it really is a whole different game since build quality matters so much, and quite frankly the specs don’t matter to me on a laptop so I’ll buy the cheapest/toughest/lightest/longest lasting etc.
Geez, I just went to the Apple site to see what the prices actually are now. Ever tried to customise a Mac Pro? Forget 2-3x, more like 10x.
Also, the theory about why most people use apps in Windows fullscreen is interesting, and probably true. Though personally I find it’s less true for me these days than it used to be.
Once you get to 24″+ monitors everything but IDEs start to look a bit sparse when run fullscreen. Plus with so much space you can have your browser on one side of the screen and Skype or a video on the other. Something quite common for me is two documents on each side of the screen, and if it wasn’t for the media keys on my keyboard I’d probably have even more open at a time.
“Ever tried to customise a Mac Pro? Forget 2-3x, more like 10x.”
Apple’s profit margins on the Mac Pro are outrageous once you go beyond the base spec – especially on RAM. It’s far, far cheaper to buy a model with base RAM and just buy the additional RAM.
A fully-specced out Mac Pro costs near double what a Dell Precision does, and the Dell will have more and faster storage, faster CPUs, a graphics card suitable for heavy-duty 3D or CAD (instead of a mid-range gaming card) and more RAM.
@Kyle
“Their whole desktop line costs 2-3x more than you’d expect”
It’s due to the size of the thing, but yeah… what a joke! why would you want a thin desktop that’s also a giant monitor? They really need to make a normal desktop, the iMac is just crap.
@Ted
“Apple’s profit margins on the Mac Pro are outrageous once you go beyond the base spec – especially on RAM”
Yeah that’s definitely true, I was talking about the base specs, i’m guessing that since those are mass produced they still make a lot of profit despite having a more competitive price.
Learn the truth! About Islam! The so called religion of piece! That psychologically programs it’s followers to hate freedom! That turns women into sex slaves for men! That declares war upon Jesus! That declares war upon America! That declares war on the white race! Learn the truth!
There’s nothing quite like a religion of piece, is there?
Gotta love the actual links
Customising the Mac Pro was something like £1100 for an extra 400MHz, £80 for an extra 240GB, and so on. The case, while mostly the same outside for like 8 years, is pretty awesome inside. Not worth more than maybe £150-200, but at least they didn’t pocket all the money. Saying that though, functionally it is basically like an old full AT case my dad had 15+ years ago. PC cases have only recently gotten back to being even half good.
Apple have always seemed pretty dumb about the eMac and iMac. They were meant to be for schools but there’s always something drastically wrong with them. From not having a floppy drive at the end of the 90s (how was I meant to bring in my work?) to the huge monitor of the current ones. Before Jobs came back it was still reasonably common to see banks of Macs in schools like you do with PCs now, but since the eMac they’ve been relegated to sitting in the corner of a few select classes like an old Acorn or BBC.
Of course, Apple don’t even target that market any more but they did try and Jobs isn’t flawless.
I think Mac still markets to higher education. Xgrid has shown some success out and about. I’m sure this is not still the case but a few years ago the fastest grid was a set of like 2k iMacs at the University of Virginia. At the same time, my University went the iMac route for their computer science and biology labs and windows pc’s everywhere else. I had never realized it but there are a lot of chemistry programs that are Mac and the CS department was actually pretty small so they elected for Unix without the constant need of babysitting like a Linux distro would require.
Regardless of cost, if you were given a mac to work on, there’s a good chance you’ll be able to do everything you could do in Windows. The same cannot be said for a Linux desktop, no matter how they try to dress it up.
Want to make Flash content? Windows can, OSX can, Linux…can’t.
Want to sync your iPhone? Windows can, OSX surely can, Linux…can’t (file access does not a sync make, freetards)
Want to write some music? Windows can, OSX can, Linux…can’t (they can’t even get their audio stack working properly, let alone release any competent music software).
Want to play some games? Windows can for sure, OSX can with a growing handful of popular titles, Linux…can’t (Loki went under, all the ports were more expensive, open sourcers won’t pay for games and scared off the big 3rd party companies like Epic and ID)
The list goes on…
To be fair there are plenty of ways to make Flash content without actually buying Flash. Pretty much everything but the charting library and the more recent video library are freely available in the Flex SDK.
If you want to make fancy animations you’re screwed (fancy doing it programmatically?), but for little web apps there’s like five different ways to do it.
Kyle, I work at an animation studio that does 90% of its 2D animation in Flash, no application development whatsoever. Flex is good for application development, but not game development. Once you have to delve outside their UI controls framework and into game timers, you’re equally screwed.
Quoting: “The thing to avoid is a RAD-style development where whole swathes of stuff get thrown away every month whilst people bicker about the exact shade of puce used for the windicators. Well, my experience leads me to run away from RAD for that reason; YMMV. Sadly I think Balsamiq is likely to lead in this direction, not least because of the round-trip between sketches and “implementation” and back again.”
RAD is only as good as the tools used. The issue is that it became a huge FAD and lots of developers didn’t learn how to develop software well, efficiently, and with good design decisions.
There are large systems written in Windows Forms, Delphi, and WPF that perform more than acceptably and have great look and feels.
The problem with RAD in F/OSS is that most of those developers look for results, as opposed to good designs and implementations. That’s why the closed or quasi-closed source model is more successful at delivering great software, IMO.
If you’re developing a new desktop environment, you probably won’t evne have the tooling available to facilitate this type of RAD development, anyways, unless you’re forking some other desktop environment.
This sounds very interesting until I think of the possibility of working on a GNOME or KDE fork, personally…
And I’d use OpenSolaris or a BSD as a base before I’d mess with Linux, for obvious reasons.
What Kerberos was proposing was Research instead of development. There would be no fork, no base, and no code to speak of. It’s simply a matter of designs, mockups and possible usability testing with the mockups (Flash was proposed, for example).
That brings up a good point; What criteria do we use to evaluate an interface? A few I can think of:
Discoverability – How easy is it to figure out where to start and how to finish? Ideally this should be rated on how many cues were needed? How obvious were the cues, did they require excessive reading? etc.
Ease of Use – How many actions, or more importantly, decisions, did the user have to make to get from start to finish?
Aesthetics – How pleasing to the eye is it for the majority of people? If bad, do they impact productivity (poor contrast, for example)?
Responsiveness – Does the interface respond in a timely manner? Are there cases where the user will think the UI has become unresponsive (greater than 100ms is when users start noticing)? Are animations taking too long and hampering the user’s progress?
Well, I wouldn’t say making music in Linux is *impossible*, but it’s severely crippled, even in the unlikely event that your audio stack is behaving. There’s Linux audio software and “media-creation” distros like Ubuntu Studio. All of these, however, fall into the same trap as most FOSS offerings; they’re buggy, incomplete and feature-lacking compared to proprietary software. Audacity doesn’t compare to Goldwave or Audition, LMMS doesn’t compare to Fruityloops or Reason and Mixxx doesn’t compare to VirtualDJ or Traktor. Add that to the fact that almost all of these FOSS programs have Windows builds and your “need” to switch to Linux goes from “not essential” to “totally unnecessary”.
@TMR: “Want to write some music? Windows can, OSX can, Linux…can’t ”
and @Delano: “Well, I wouldn’t say making music in Linux is *impossible*, …”
I have been an amateur musician for quite a while, and so I had Steinberg Cubase. In discussions with freetards I sometimes mentioned the point that there is no equivalent to Cubase in OSS land. The program names thrown at me as an alternative have varied over the years, but a real alternative was never among them. Last time The Alternative was “Ardour and Rosegarden”. This tiny detail that you have to JACK together two different programs to get something remotely resembling Cubase of course didn’t deter the freetard (and neither the fact that he doesn’t know a thing about music SW in the first place), but the real coup de grace was the following page on the Ardour homepage:
http://ardour.org/support_expectations
Well, at least they are rather realistic (except for the occasional pat on the back), and I wish them all the luck – but if I were still making music, I’d just stick with Cubase, thank you. (And of course Cubase is just one of the many _good_ music stuff you can use on Windows and MacOS but not on Linux.)
@TMR: “What criteria do we use to evaluate an interface?”
Good question, and I mostly agree with your criteria (I’m not so sure about aesthetics as such, but contrast is definitely an issue.) Do I dare suggest as another criteria “Controlling Your Environment Makes You Happy” ?
http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html
That thing about RAD, btw; I did qualify it with “YMMV.” Like “agile,” it often falls into the category of a Silver Bullet. Where possible, I try to avoid jobs that are based around a silver bullet. It’s increasingly impossible.
@Carsten: Pretty much everything Joel has written about UI development would apply, although I have a sneaking suspicion that Kerberos was there before him and has thought more carefully about it afterwards. It’s a useful resource for ignoramuses like me, however.
*Obviously* you’d have to include aesthetics, however difficult that criterion might be to judge. Where would anything marketed by Jobs be without aesthetics? There’s at least one basic issue to resolve asap, which is to choose between pixel-based font-rendering and aesthetics-based font-rendering (Joel again).
I’m a programmer, not a designer, so a couple of other things spring to mind.
You also have to consider Unity. (I can’t think of a better word to describe what I mean.) An obvious counter-example to Unity is the long-standing X issue with cut & paste. Who knows when it will work and when it won’t? It’s not unreasonable to start with the Linux Desktop as a series of inaccurately linked design decisions and then consciously strive to avoid all of them. (From an Apple point of view, Unity seems to be embedded by virtue of Cocoa, so I’d still want a mandatory scripting framework for absolutely everything.)
One more thing which is *not* part of any current desktop, so far as I can see. There’s enough computing power out there, these days, to allow for an UberPaperclip to offer sensible AI-style help. Maybe current HMI work is going in this direction, although I have no information on the subject. It’d be really nice if one could utilise anti-spam techniques in reverse and actually “guess” what the user is thinking — related files or apps, maybe relevant personal contacts or music/visuals, whatever.
It’s not strictly part of the remit, but it would be a fabulous addition. No idea how you’d make it unobtrusive, though…
I’d propose some sort of sliding rule interface that brings your most-used applications (assuming we even go the standard application route), tasks and documents to the forefront. This gives a logical way of finding lesser used functions; start near the back of the stack/timeline/ruler/etc. Bear in mind, this is a concept, not a fleshed out model.
Secondly, project-oriented storage. It’s a real pain having to try and force a folder hierarchy to mimic a project. I propose the idea of project-oriented storage with projects and assets rather than folders and files. The benefits to this become clearer when you take into account the ability to reference one asset into other assets elsewhere within a project. Likewise, all tasks/applications that contribute to a project become linked to it so that there is a complete history of changes made and those changes can be baked, altered, or rolled back.
Think of it this way, you don’t have a Word document, you have a text asset that needs to be combined with a logo asset made of vector art that can then be consumed by a printing task. This way, tasks can consume and remodel a project as it deems fit to complete its task.
The sliding rule interface is a simple version of what I was muddle-headedly aiming at: I’m trying to get away from the browser paradigm, which essentially does this with absolutely no intelligence attached. I think what I’m suggesting is a sort of “event network,” whereby the UI captures what it can — launching apps, task switching, button-pressing, etc — and tries to make sense of it for a given session or workflow. This is more akin to what the better automated test tools do.
Project-oriented (asset-oriented) storage in some form would be great. There’s a reason IDEs exist … in fact, representing the entire file system in an IDE (with pluggable extensions, yet) would be a heck of a better paradigm that this stupid folder thing.
Of course, third-party installers (ie the whole of the rest of the world) would still insist on the old paradigm, so you’d still need a mirror filesystem that looks like, sigh, the Unix one. Well, Linux still needs a CLI. I guess you need a certain degree of backward compatibility.
”
freehunter said: 2010.06.09 03:14
I completely agree with this post. Linux is completely unusable. I use it every day ”
Yeah, zealotry is a problem. Quite a few on this blog. Wow. Talk about cognitive dissonance.
“Mission: Create a usable Desktop OS – just to show the Linux fanboys what they should have done. Avoid GPL software wherever possible. Make it marketable.”
So we’ll use…what?
“As a base we need a kernel etc. – one of the BSDs should do.”
Because those kernels are more….something than Linux. Or less something else. Less compatible, and popular for sure. But hey, if the BSD license is so rad-tastic it will liberate us from the evils of the Linux Kernel with all its…Linuxy stuff, then ok.
“(Include OSS for audio.)”
Because it’s old and sucks, and will really showcase the audio capabilities of our hypothetical non-Linux Eagle-BSD…the ultimate desktop…WATCH OUT APPLE! I can’t wait to see who starts mixing records on Logic 8 for Eagle-BSD featuring the OSS audio architecture: A quantum Leap forward in sound sub-systems. Take that, Linux! We’ll have OSS!
” We need an application framework, which should be .NET because it…”
…Blows, has memory leaks, couldn’t even be used as a core language for Windows, is only implemented properly *on* Windows, requires a VM, reflects the biases of the posters here, and may infringe on Microsoft Intellectual Property rights if you implement it in Mono– oh yes, and will result in slow-as-fuck apps like all the ones on Linux you hate. Not even “Linux Zealots” like Mono much, but you’ll show them!
“exists, isn’t bad (AFAIK it’s even pretty good) and there are existing applications.”
For Windows. Or did you mean the GPL apps like F-Spot (ghey) and Banshee?
“X11 doesn’t cut it, so create a graphic “layer” to sit on the kernel and provide the necessary services for the .NET framework. ”
Yeah, only a Linux nerd would use X11. Let’s conjure up a “layer” thingie and provide…WinForms? Or DirectX controls? Good luck licensing that.
“If QT provides any help with this, license it and use it.”
Ummm….with yer thingie layer-dealie? Or?? Is that tied right into the Warp Engines?
Fucking amazing. I think the blog owner cited the Dunning-Kruger effect in another post. I hope his readers Googled that. I just thank the Usability Gods that you guys are here to save the Heathens from the fatally-flawed Linux. Whew.
[...] Door Pin Insert Kit By Omix Posted on July 6, 2010 by merledua239 The Non-Existent Linux Project | Piestar [...]
[...] Door Pin Insert Kit By Omix Posted on July 7, 2010 by careybautista246 The Non-Existent Linux Project | Piestar [...]
[...] Door Pin Insert Kit By Omix Posted on July 9, 2010 by efrainfortis289 The Non-Existent Linux Project | Piestar [...]
[...] Door Pin Insert Kit By Omix Posted on July 9, 2010 by dorianclifton124 The Non-Existent Linux Project | Piestar [...]