Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Link to Original Source
Seriously stop calling it OO.o, it makes 90% of military acronyms
actually make sense, and that is messed up.
Its proper name is OpenOffice.org. Thereby we derive the acronym OO.o. I'm
generally an advocate of calling products and people by their actual proper
nouns rather than a shorter or insulting name.
What's the cost of data insecurity[...]
Use a text file and never save to the hard drives. Bring a flash drive with portable apps on it so you don't have to use insecure apps.
[...]of giving up freedoms[...]
You have the freedom not to go to the school, and thus not use the operating system if you like.
[...]and of supporting a criminal corporation?
I'm all for due process of the law. Will they violate the laws? Probably yes. But I as a consumer won't support them. I'll use Windows if it's given to me as a service, but I won't support them directly.
The bottom line is that freedom will probably cost something. If you have exotic values such as to never use proprietary standards, then you are going to have to make some sacrifices. Most people just don't give a shit. I use Windows at my college and Linux at home because I don't have enough money to grab Windows, nor is Windows actually a priority for me to own.
If I compiled my Xorg to be tiny, then I might have less usage. But compiling with -O3 and -ggdb (among other options), I have a larger footprint. But, again, I don't care because of the system I have. If I had only 64 MiB of RAM, then I would be more wary about my memory.
OTOH the modal interface of vi gives an additional error source because you always have to remember if you are in insert of command mode.
That's not the correct way to use vi. Command mode is normal mode. Never leave it in any other mode, including insert mode. Ever. Only use insert mode when you're actually inserting something.
There's also usually a status area which tells you which mode it's in as well.
But there is no justification to make a program with a steep learning curve.
Says you. vi and emacs have steep learning curves, but it pays off with high efficiency in editing text in the long run. Using something like AutoCAD has a high learning curve in order to efficiently use it. For a physical example, we have fork lifts, caterpillars, and heavy machinery in general.
uzbl may have a steep learning curve, but it's worth it to the power users that want the type of functionality it can offer.
Not to mention possibly troublesome for multi-user systems on a guest account where flash is grabbed from a global directory. But, I suppose if a sysadmin were to update firefox, they should also probably update flash. If they don't value security, that is.
However, flash can be installed to ~/.mozilla/plugins/ for precedency over the global directory. I'd hate to be support on that:
Support: "What file manager are you using?"