The real discussion is much more nuanced and scientific than "peer review is bullshit," but that blunt approach is appropriate for Slashdot.
I totally agree. The problem is even worse in free software than in real science. It is enough for a "reputable" developer to state that a given free software project is "superior" to another for most everybody accepting it on his word alone, even if the evidence shows that the opposite is true.
And that's your answer. A filesystem like FAT32 or ISOFS that's likely to still be implemented in future OSes and a recovery files which let you rebuild anything that suffers from bit rot.
Lzip and lziprecover can help you keep your data safe in the long term. (For the kind of data where it makes sense to use a lossless compressor, that is).
That does NOT eliminate the need for good code design, actually, having a good design phase is absolutely crucial to this approach, since else your juniors have to design. That would be... let's say sub-optimal.
Even more important than good code design is good data format design. No amount of good code can compensate for the defects in a bad format.
Subject: Re: [Bug-ddrescue] ddrescue. NTFS-3g eating 100%. Solved by switching to ext3
I had a ddrescue imaging to a file on an ntfs partition (mounted with ntfs-3g) on a USB drive on Ubuntu 9.04 LiveCD. It was going slower and
slower, although number of errors was not increasing. I tried all the ddrescue options I could find, but nothing helped - it was working for 5 days already and was slowing down so much so it would never end. By the time I stopped it it copied 112Gb out of 223Gb.
Then I noticed that ntfs-3g was eating 100% cpu. So, I created an ext3 partition on the same USB drive, copied my image file and log there and
restarted ddrescue.
Boy! it finished in a couple of hours!
getopt() is in the header <unistd.h>, which is in POSIX, not ANSI. POSIX facilities are not guaranteed to be present on W*nd?ws systems. It also handles only short options, not long options. For those, you have to use getopt_long() of <getopt.h>, which isn't even in POSIX. You can also use Arg_parser and avoid all the portability problems of getopt_long.
1. You did not specify. You asked simply "what Vim can do that Moe can't".
Yes, Sorry. I tend to be too concise because it costs me a lot to write in English.
2. For a text editor, being capable of editing multi-language files is an absolute imperative nowadays. Did you know.desktop files contain all the translations (English, Deutsch, Korean, Japanese etc) of the label of an application? Many people need to use an utf8-capable editor.
But many other people does not need UTF-8 most of the time, or even never. I am one of them. Also a smaller editor tends to have less bugs and fits better in rescue discs.
3. "Simply use another editor"? Come on, I tought you were asking for information and help (which I tried to provide here) but you seem to be only interested in advertising Moe.
This was a honest response. If my editor does not suit your needs because it is designed for other use, what do you expect my answer to be? "I'll work all the night to offer you the editor of your dreams in the morning"?
Moe's source is about 37 times smaller than Vim. I intend to make Moe a small, simple and reasonably complete editor, not a clone of Emacs.
4. I found your answer deeply disrespectful, and I was only trying to help.
I didn't intended to be disrespectful, and I appreciate your help. But I think we are speaking about two completely different types of editors.
Why is UTF-8 out? I speak Portuguese natively, and my preferred encoding is not latin1 anymore (because with UTF8 a lot of stuff in Japonese can be cleanly in the same page as my Portuguese text, for instance). I also happen to like vim's modal interface.
UTF-8 is out by design. If you need UTF-8, simply use another editor. The same can be said about modal interface.
When I asked "what Vim can do that Moe can't", I was refering to editor tasks, not charset encodings.
Re:Why are we hiding from the police, daddy?
on
Vim 6.4 Released
·
· Score: 1
Similarly, Vim is the Hole Hawg of text editors
Please, could you explain me what Vim can do that Emacs or Moe (the new GNU editor) can't.
I am not trolling. I would like to improve GNU Moe as much as possible.
From time to time, I have tried to learn emacs (seeing the benefits) but the learning curve seems so steep
GNU has now a new option, GNU Moe, a text editor very easy to use, and two orders of magnitude smaller than Emacs, yet powerful enough for most editing tasks.
The war in Iraq was legal. Although not properly informed of the situation, and not the best Idea. But it was legal as Iraq was breaking a lot of UN Violations.
AFAIK Israel has violated more UN resolutions than Iraq. Why haven't the USA invaded Israel already?
Wait a minute, I thought you said there should be no laws? That's what I was calling an assinine idea. Now it seems that you do want at least one, so apparently you do agree that laws are necessary in human society?
Lets see if I can help you to get out of this circular reasoning.
A society without laws and in which no one has the right to make laws and impose them to others is exactly the same that a society with one only law forbiding "to make laws and impose them to others". This is, so to speak, an "implicit law".
The only way to make someone do something in such an advanced society (say sponsor a mars mission), is to convince them with arguments.
Slashdot Mirror
I totally agree. The problem is even worse in free software than in real science. It is enough for a "reputable" developer to state that a given free software project is "superior" to another for most everybody accepting it on his word alone, even if the evidence shows that the opposite is true.
if there's one lesson on how to do your part in an age of distributed truth, it's to speak the truth and to support those who do.
Xz format inadequate for long-term archiving
I'll believe they are serious about bug squashing when they drop xz from the deb package format.
It is not a better link; it requires javascript to even see it.
Lzip and lziprecover can help you keep your data safe in the long term. (For the kind of data where it makes sense to use a lossless compressor, that is).
Data formats are designed without taking bit flips into account even today.
Even more important than good code design is good data format design. No amount of good code can compensate for the defects in a bad format.
Global warming?
In the manual of any argument parser.
Then outlaw trade secrets by requiring that the schematic diagram, source code, recipe, etc, of anything sold to the public must be made public.
For example performance with very large files.
Subject: Re: [Bug-ddrescue] ddrescue. NTFS-3g eating 100%. Solved by switching to ext3
I had a ddrescue imaging to a file on an ntfs partition (mounted with ntfs-3g) on a USB drive on Ubuntu 9.04 LiveCD. It was going slower and slower, although number of errors was not increasing. I tried all the ddrescue options I could find, but nothing helped - it was working for 5 days already and was slowing down so much so it would never end. By the time I stopped it it copied 112Gb out of 223Gb.
Then I noticed that ntfs-3g was eating 100% cpu. So, I created an ext3 partition on the same USB drive, copied my image file and log there and restarted ddrescue.
Boy! it finished in a couple of hours!
Moe's source is about 37 times smaller than Vim. I intend to make Moe a small, simple and reasonably complete editor, not a clone of Emacs.
I didn't intended to be disrespectful, and I appreciate your help. But I think we are speaking about two completely different types of editors.When I asked "what Vim can do that Moe can't", I was refering to editor tasks, not charset encodings.
I am not trolling. I would like to improve GNU Moe as much as possible.
Try the latest version (0.4) of Moe here.
For those not in "The land of the metric free", 250 MPG is about 1L/100km.
A society without laws and in which no one has the right to make laws and impose them to others is exactly the same that a society with one only law forbiding "to make laws and impose them to others". This is, so to speak, an "implicit law".
The only way to make someone do something in such an advanced society (say sponsor a mars mission), is to convince them with arguments.
If you prefer it another way, we would need one only law, "Live and let live". And execute anyone who can't accept that.
--
How may a "trillion" be a "million million"?