11–19 of 19 posts
For several months I have a 500MB tmpfs ramdisk (which I will probably turn into a ramfs one after reading that article). I put my browser cache, several logging files and other volatile things there. Whenever I download something just to dispose it later, it goes in there. If I try something stupid with a lot files or some big ones, it goes in there. It feels much nicer than to fragment the harddisk for such things;…
This article exemplifies one problem with the Linux/tech crowd. All that text and command line output - and not a single damn graph on the page! One graph showing speed differences would eliminate the need for tons of text on that page.
Hard disk: _ 100 MB/s
Ram disk : ____________________ 2000 MB/s
For several months I have a 500MB tmpfs ramdisk (which I will probably turn into a ramfs one after reading that article). I put my browser cache, several logging files and other volatile things there. Whenever I download something just to dispose it later, it goes in there. If I try something stupid with a lot files or some big ones, it goes in there. It feels much nicer than to fragment the harddisk for such things;…
can this be done using osx?
For several months I have a 500MB tmpfs ramdisk (which I will probably turn into a ramfs one after reading that article). I put my browser cache, several logging files and other volatile things there. Whenever I download something just to dispose it later, it goes in there. If I try something stupid with a lot files or some big ones, it goes in there. It feels much nicer than to fragment the harddisk for such things;…
I call it /tmp-ram and I give it the same drwxrwxrwt permissions as /tmp.
I use it as the default place for all downloads.
Another example, I listen to streaming radio, and I rip it to disk (so I don't have to deal with buffering, and so I can skip songs). I put it in /tmp-ram, it rips from one end, and I play and then delete from the other.
This article exemplifies one problem with the Linux/tech crowd. All that text and command line output - and not a single damn graph on the page! One graph showing speed differences would eliminate the need for tons of text on that page.
Hard disk: _ 100 MB/s Ram disk : ____________________ 2000 MB/s 'K?
Earlier quoted context omitted.
Hard disk: _ 100 MB/s Ram disk : ____________________ 2000 MB/s 'K?
No, but that's not the point: anyone can be cajoled into making a graph (and I love ASCII art as much as anyone), but the fact that there wasn't the culture of putting a pretty ribbon on nice results, that's the problem.
Earlier quoted context omitted.
Hard disk: _ 100 MB/s Ram disk : ____________________ 2000 MB/s 'K?
No, but that's not the point: anyone can be cajoled into making a graph (and I love ASCII art as much as anyone), but the fact that there wasn't the culture of putting a pretty ribbon on nice results, that's the problem.
I wrote an article some months back about competing with OSS, which included some very basic advice like "If you offer software for download, you should have a prominent button which lets people download your software". I did not anticipate this recommendation would be controversial. I got some absolutely priceless comments about it. My two favorites: users who can't find the software without a big ugly button don't deserve to have it, and technically disinclined users who are attempting to install software from the Internet are already doing something wrong, they should be getting it from their distro's repo instead.
This article exemplifies one problem with the Linux/tech crowd. All that text and command line output - and not a single damn graph on the page! One graph showing speed differences would eliminate the need for tons of text on that page.
Graphs without much content, which is the leading combination these days - especially around "tech", business, economics sites/"content", is pretty damn annoying and it makes it feel a lot more cheap.
I do agree that a graph would be a nice complement. Even if the "problem with Linux/tech crowd" was pretty unnecessary.