Meanwhile, my C program to read and sort lines of bible.txt runs in less than a millisecond. And it's bloody simple, any C programmer who knows what he's doing can get there with just the basic techniques and no libraries besides stdlib and POSIX <sys/time.h> for measuring.
Name:
Anonymous2008-05-14 6:11
>>1,16
the right way to do it would be to use the time utility instead of timing only part of the program's execution. oh wait, javafags would really lose then because the VM takes 100 FUCKING MINUTES to start.
Name:
Anonymous2008-05-14 6:24
I'm beginning to suspect that by default on Windows file I/O is unbuffered. Which is bloody stupid really, given >>16.
>>17 because the VM takes 100 FUCKING MINUTES to start.
this is simply false, and you're the type of stupid faggot that thinks that java is bad for this reason. go suck a cock you moron. fuck. if any of you had any brains you'd realize how much C sucks.
Name:
Anonymous2008-05-14 23:25
Meanwhile, my C program to read and sort lines of bible.txt runs in less than a millisecond
LOL
3/10
Name:
Anonymous2008-05-14 23:28
>> 21
Well, the VM start time is significant, but if you're programming anything more complicated than a small console app, it shouldn't be too noticeable.
Choose the right tool for the job, etc.
Name:
Anonymous2008-05-14 23:59
>>23
the program in the OP's link is a small console app.
If you have a long-running program, the startup time is dwarfed.
If you have a short-running program that is run once, it simply doesn't matter.
If you have a short-running program that is run multiple times, you just stream data through it, instead of starting/stopping processes, just like you do in C++ etc (also why makefile and such building SUCKS ASS compared to uber fast Java compiling of giant code trees in seconds)
Name:
Anonymous2008-05-16 7:40
That is what I was saying
Name:
Anonymous2008-05-16 7:47
>>30
imagine what it would be like if cat or grep took about 20 seconds (that's about how long the java VM startup time is on my computer) to start up every time you ran it.
Name:
Anonymous2008-05-16 9:13
>>32
Then it'd be a service. I do hate the notion of process boundaries and applications, though. Like I said in >>30 , I fucking HATE compiling C++ because it always takes so goddamn long, spawning shitloads of processes for every single file, only to close and restart for the next one ad nauseum.
And I seriously doubt it takes 20 seconds to start, even on an older box. MAYBE the very first time you invoke it, but the shit caches all over the place now.
Name:
Anonymous2008-05-16 9:26
>>32
That's not a problem if you already have cat running. Just add an option to take filenames line-by-line on stdin, then keep it open in another window.
>>33-35
I'm sorry to inform you that 1TB RAM is not yet generally available, so running all programs on my computer in a JVM at the same time is not an option.
If you have a long-running system, the development time is dwarfed.
If you have a short-running system that is used once, it simply doesn't matter.
If you have a short-running system that is used multiple times, you just stream machines out of the factory instead of designing/trashing blueprints, just like you do in architecture etc (also why skyscraper and such building SUCKS ASS compared to uber fast server compiling of giant hardware trees in seconds)
Name:
Anonymous2008-05-16 14:22
stream machines out of the factory Go back to Design Patterns, please.
Name:
Anonymous2009-03-06 6:23
The bigger question is What kind of annoying Anyone know how I would like to learn Lisp and read them until my ass is a good way to promote our favored.
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy