(is he gone yet?)
1,278 karma · joined October 16, 2009
(is he gone yet?)
My only other concern is how they're delivering the videos. Is it just flash? Or is it some crazy Silverlight+DRM thing like netflix? If it's the former they could attract some Linux users who can't use netflix.
Awesome is both really minimal and really extensible. By default you don't have anything, and you build it up to how you like it with lua and a couple of libraries that expose bindings to things like desktops and tags.
I'm not really sure why, but Spaces just feels inferior to basically every multiple desktop implementation I've used on Linux. There's just not enough of a UI for it, and it's clunky to use. On Linux using multiple desktops is smooth and natural. On OS X, it just feels weird.
I was participating in an obfuscated code contest a while back (making a simple command line multi-function calculator), and since I knew I couldn't compete on line noise I decided to try obfuscation through architecture. Somewhere around writing a RightSideOperandInterface (so I could catch division by 0), it managed to get into my head that it was actually more robust and extensible than doing it any other way. I came to my senses slightly after submitting it.
If you map them to something else (say... modifier keys), you can do all sorts of useful things. Like hold down one of the buttons and click on files to select more than one. Or activate Spaces if you click the middle button, but activate Expose if you click the middle button while holding the back button down.
If back/forward buttons had to stay back/forward buttons I'd agree that they are pointless. They don't though; they can be super useful.
Assembly line style processes are just like shell pipes. I get data, process it, another step.
The same project I also got to act as an accumulation buffer. As things were produced I collected sets of 10 at a time of them and gave those to someone else who counted and stored them. He didn't have to walk as much and they were easier to count.
To the people who use gigantic numbers of tabs, what does your browsing workflow look like where you end up with that many?
I think that seems like a pretty good methodology in a lot of cases actually.
If it was left up to the OS's package manager the writer would have to maintain 10 to 15 different packages, or get other people to. Would you rather deal with one gem, or bento package or one each of whatever rpm/apt/yum/pacman/brew/macports/pkgsrc/... use?
If different OSs all converge to one package manager in the near future, then, great! we can use that. Until then though, I think language specific ones are just fine.
I think that's rather counter-intuitive, but I doubt it'd be much of an issue in practice.
autocmd BufWriteCmd *.html,*.css,*.haml :call Refresh_browser()
function()! Refresh_browser()
if &modified
write
silent !xdotool search --class google-chrome key ctrl+r
endif
endfunction