WinZip is good; heck, it's one of the very few shareware programs I paid for. I wish it could extract bzip2 archives, though. And I wish it could perform the equivalent of a tar -> bzip2 process, since I get significantly better compression rates than with the normal pkzip compress-each-file-individually method.
Still, it's great being able to right click on a folder and select "Add to xxx.zip". Damn convenient.
Reminds me of a MacOS X utility I downloaded to help set up some NFS exports. The author wanted me to pay $15 to use it, even though I was going to use it once. Needless to say, I set up the exports the old-fashioned way. Once. More than two years ago. Glad I saved that $15; it bought me a copy of MEPIS Linux a few months ago.
I don't even think there's the need to enumerate any of them.
Please do. Aside from bicycling, I can't think of any. And bicycling is only enjoyable when the weather is nice, which is maybe 40 or 50 days out of the year here in Iowa. What can I do the rest of the year?
But what kind of $6000 machine can you toast with software? I know that you could destroy older hardware like video cards, monitors, and hard drives with software, but what can you do to modern hardware?
Not that I want to fry anyone's $6000 system out of seething jealousy, mind you. Oh, gosh, no.
they'll just ignore the warning or throw in lip service methods
Ranum admits that there isn't much the runtime can do if developers deliberately bypass built-in safety checks. His idea is that the runtime should handle more of the gruntwork so that it's less work to use the safety checks than it is to bypass them. Right now it's the other way around, and that's why so many programmers take the insecure route.
One thing the author suggests is that warnings should prevent the code from compiling, so it would be difficult to ignore them. IOW, there are no more warnings, just a broader range of compilation errors.
Which is exactly what Raymond says. "If there is actually anyone still left on the planet who thinks the term free software was a good idea, I hope they're paying attention. Because what Microsoft is doing here is exploiting the old familiar gratis/libre ambiguity of the word free in yet another way. They're setting up for a claim that free software advocates are lying or deluded because Linux has a nonzero TCO."
A pragmatism that has allowed free software to expand and flourish in mainstream computing circles, instead of being limited to a few thousand hackers debating the finer points of "free speech" and "free beer" from their parents' basements.
And I'm sure you hand-convert all of your logic into wiring diagrams before putting it together on a breadboard. I mean, real programmers don't want compilers, libraries, and prefabricated hardware. Just like you don't build houses from lego bricks, you don't build software from lego bricks.
I'm willing to sacrifice a little speed for the convenience and features of an integrated desktop environment. I don't care if my computer "screams" if it's going to be a pain in the ass to use.
I don't know what environment you're using, but in KDE, Apply always makes the changes permanent without closing the dialog. I'm not aware of any changes you can make that only last for the session.
(I've seen apps on Windows that only apply the changes temporarily if you click on "Apply" or "OK". They also have a "Save" button to make the changes permanent. I think that's terribly clunky. And don't get me started on apps that make your changes permanent as soon as you make them, regardless if you click on a button or not.)
Umm, how are you going to get that ISO? With your dial-up connection? Oy. And I thought getting my three-month-old MEPIS installation up to date was a pain in the ass at 48.8Kbps.
Some people prefer using a unified environment. If you're happy with what you're using, then fine; you're not in the target audience.
I tried the Rox + Windowmaker combination myself before I got more RAM. To quote you, "I see 0 advantage". DnD saving required me to open file-manager windows, so it was no faster than a Save dialog. Also, since I ended up using mostly KDE apps after awhile, I didn't really save any memory. Plus I lost advantages like having my session restored when I logged back in. So, just because something works for you doesn't mean it works for everyone.
BTW, I'm curious how Gnome and KDE managed to render you nonproductive for a whole week. Did they switch your keyboard layouts at random or something?
Until recently, I could run Windowmaker and a few apps just fine on my (now-dead) 64MB laptop. It clipped along pretty well unless I launched Netbeans.
I'm running the latest KDE on a six-year-old PC and it's performing just fine. It would probably run even better if I'd compile it myself, but I'm too lazy.
I don't know what the people complaining about abominable performance on machines at least twice as fast as mine are talking about.
Slashdot Mirror
After seeing Gimp and BitchX in my package list all these years, Kunt would barely faze me.
That tells us more about you than it does about the name.
WinZip is good; heck, it's one of the very few shareware programs I paid for. I wish it could extract bzip2 archives, though. And I wish it could perform the equivalent of a tar -> bzip2 process, since I get significantly better compression rates than with the normal pkzip compress-each-file-individually method.
Still, it's great being able to right click on a folder and select "Add to xxx.zip". Damn convenient.
Hey, I liked the IP-Openly variation.
Reminds me of a MacOS X utility I downloaded to help set up some NFS exports. The author wanted me to pay $15 to use it, even though I was going to use it once. Needless to say, I set up the exports the old-fashioned way. Once. More than two years ago. Glad I saved that $15; it bought me a copy of MEPIS Linux a few months ago.
Just to nitpick: I think you mean Qt, not KDE.
Not a furry, eh? ;-)
Ooo, I'll have to remember that one next time rent is due.
Please do. Aside from bicycling, I can't think of any. And bicycling is only enjoyable when the weather is nice, which is maybe 40 or 50 days out of the year here in Iowa. What can I do the rest of the year?
But what kind of $6000 machine can you toast with software? I know that you could destroy older hardware like video cards, monitors, and hard drives with software, but what can you do to modern hardware?
Not that I want to fry anyone's $6000 system out of seething jealousy, mind you. Oh, gosh, no.
Hell, I just wrote a buffer overflow earlier this morning. In effin' COBOL, no less. Spent three hours debugging it.
Of course. But that takes longer to develop, which is a Bad Thing in the commercial world.
Ranum admits that there isn't much the runtime can do if developers deliberately bypass built-in safety checks. His idea is that the runtime should handle more of the gruntwork so that it's less work to use the safety checks than it is to bypass them. Right now it's the other way around, and that's why so many programmers take the insecure route.
One thing the author suggests is that warnings should prevent the code from compiling, so it would be difficult to ignore them. IOW, there are no more warnings, just a broader range of compilation errors.
Which is exactly what Raymond says. "If there is actually anyone still left on the planet who thinks the term free software was a good idea, I hope they're paying attention. Because what Microsoft is doing here is exploiting the old familiar gratis/libre ambiguity of the word free in yet another way. They're setting up for a claim that free software advocates are lying or deluded because Linux has a nonzero TCO."
A pragmatism that has allowed free software to expand and flourish in mainstream computing circles, instead of being limited to a few thousand hackers debating the finer points of "free speech" and "free beer" from their parents' basements.
And I'm sure you hand-convert all of your logic into wiring diagrams before putting it together on a breadboard. I mean, real programmers don't want compilers, libraries, and prefabricated hardware. Just like you don't build houses from lego bricks, you don't build software from lego bricks.
I'm willing to sacrifice a little speed for the convenience and features of an integrated desktop environment. I don't care if my computer "screams" if it's going to be a pain in the ass to use.
I don't know what environment you're using, but in KDE, Apply always makes the changes permanent without closing the dialog. I'm not aware of any changes you can make that only last for the session.
(I've seen apps on Windows that only apply the changes temporarily if you click on "Apply" or "OK". They also have a "Save" button to make the changes permanent. I think that's terribly clunky. And don't get me started on apps that make your changes permanent as soon as you make them, regardless if you click on a button or not.)
Umm, how are you going to get that ISO? With your dial-up connection? Oy. And I thought getting my three-month-old MEPIS installation up to date was a pain in the ass at 48.8Kbps.
Simplicity is beautiful.
Unless that simplicity prevents you from doing something. People have different ideas about what's "simple" or "elegant".
I tried the Rox + Windowmaker combination myself before I got more RAM. To quote you, "I see 0 advantage". DnD saving required me to open file-manager windows, so it was no faster than a Save dialog. Also, since I ended up using mostly KDE apps after awhile, I didn't really save any memory. Plus I lost advantages like having my session restored when I logged back in. So, just because something works for you doesn't mean it works for everyone.
BTW, I'm curious how Gnome and KDE managed to render you nonproductive for a whole week. Did they switch your keyboard layouts at random or something?
Until recently, I could run Windowmaker and a few apps just fine on my (now-dead) 64MB laptop. It clipped along pretty well unless I launched Netbeans.
The horror. The horror....
Why would you be running kdeinit if you're not running any KDE apps?
I don't know what the people complaining about abominable performance on machines at least twice as fast as mine are talking about.