Ways to measure time: 1) execution time 2) development time
1 is usually less important than 2. Really. If it saves me one round trip to the compiler, I'll take it. The merits of the boxes themselves aside, this is a very reasonable and useful thing to do, from the perspective of both ease of coding and of code clarity.
Also for what it's worth, those numbers probably don't mean much. If it's what you get out of windows task manager, then they indicate the size of the program's virtual address space, which includes pages from libraries they use that have been mapped in. Which means two things: 1) the memory may be shared with other apps, and 2) the memory may not even be in physical memory, but on disc and never actually loaded.
And those numbers do make sense - winamp probably uses its own libraries for mpeg decoding and so on, whereas I'm sure wmp uses directx stuff.
you can always fake precision if you want to badly enough, but it's really slow. One arithmetic operation vs. many, not to mention the various memory accesses that may need to happen, depending on how it's implemented.
That's a really good idea. It would be interesting to see out it worked out - there'd probably be set times when people would all log in to play together, it'd be like a two-hour day in the game world, effectively.
It could also be used as a lower price point for the service.
mLan is a superset of normal firewire audio (IEC 6something), which is starting to get some attention in JACK via the firewire generic driver. I'd do it myself with my fa-101, but the standard is kind of expensive.
And what about sites with boobies on their front pages? Verisign is now a porn site! (albiet one with very small pictures) Will all the censoreware block them?
Good point, that is a valid interpretation. However, my guess is that their sample size (300) is too small to make any really significant conclusion. Maybe if they surveyed the same group of people over a period of time it would work better.
OTOH, you might want to take a look at my other post in this article--among professionals, a signifigant number have stuck with OS9 because osx gui etc and overhead is so much heavier than in os9 that programs like photoshop, illustrator, quark, etc run a lot slower.
Part of it is GUI overhead, but a lot of it is probably having a proper scheduler, memory protection, and all the other trappings that go with a modern OS. Plus all the apps are made with higher-level libraries that incur more overhead themselves, but lead to better software in the end. I'll bet Win95 would be pretty snappy on my Athlon too.
1. Put a cd in your drive upside down. 2. Double click on "My Computer" 3. Watch the window try to appear 4. Wait as your drive tries to read the label of your cd in vain. 5. After the timeout, see all the icons pop up in explorer.
For what it's worth, those numbers can be misleading. They measure the size of the process address space, but that includes mmap'ed libraries. (i.e. stuff that's not necessarily loaded yet or may never be) A somewhat more accurate measure is to turn on the "VM Size" column, but I'm not sure exactly what that measures.
Hear hear! There was something bugging me about this article and you've articulated it exactly. Coding for maintainability, clarity, and correctness is far more important than optimization. Increase in computer speed and size allows not only the luxury of additional features but more importantly the ability to work at a higher level and get more done.
Re:They should stick with C
on
The GNOME Roadmap
·
· Score: 2, Informative
Depends what you use it for. If you're folding up method definitions, sure it's the same thing effectively. But there are other places where it helps a WHOLE lot - like when you're using a GUI builder that puts gobs of generated code in different places. Just set it up to fold over the auto-generation delimiters it puts in the file and you can read your code much more easily. I've used it for that in VS.NET, with the gui builder. Eclipse's VE works in very much the same way, so it should be very useful there.
It also works well with any other application where you have a horde of boilerplate code that you want to ignore but don't want to or can't factor out.
Rogue Wave Software always used to ship source. I assume they still do.
Ways to measure time:
1) execution time
2) development time
1 is usually less important than 2. Really. If it saves me one round trip to the compiler, I'll take it. The merits of the boxes themselves aside, this is a very reasonable and useful thing to do, from the perspective of both ease of coding and of code clarity.
Also for what it's worth, those numbers probably don't mean much. If it's what you get out of windows task manager, then they indicate the size of the program's virtual address space, which includes pages from libraries they use that have been mapped in. Which means two things: 1) the memory may be shared with other apps, and 2) the memory may not even be in physical memory, but on disc and never actually loaded.
And those numbers do make sense - winamp probably uses its own libraries for mpeg decoding and so on, whereas I'm sure wmp uses directx stuff.
you can always fake precision if you want to badly enough, but it's really slow. One arithmetic operation vs. many, not to mention the various memory accesses that may need to happen, depending on how it's implemented.
:)
Also talking out of my ass.
That's a really good idea. It would be interesting to see out it worked out - there'd probably be set times when people would all log in to play together, it'd be like a two-hour day in the game world, effectively.
It could also be used as a lower price point for the service.
What a great idea!
No.
Can you sychronise the transport now? I tried that a few months ago, to no avail.
mLan is a superset of normal firewire audio (IEC 6something), which is starting to get some attention in JACK via the firewire generic driver. I'd do it myself with my fa-101, but the standard is kind of expensive.
And what about sites with boobies on their front pages? Verisign is now a porn site! (albiet one with very small pictures) Will all the censoreware block them?
Good point, that is a valid interpretation. However, my guess is that their sample size (300) is too small to make any really significant conclusion. Maybe if they surveyed the same group of people over a period of time it would work better.
They say that the number of people who have never played online games has *risen*. How exactly does that work?
I very much disliked that book. Seemed so depressing to me.
OTOH, you might want to take a look at my other post in this article--among professionals, a signifigant number have stuck with OS9 because osx gui etc and overhead is so much heavier than in os9 that programs like photoshop, illustrator, quark, etc run a lot slower.
Part of it is GUI overhead, but a lot of it is probably having a proper scheduler, memory protection, and all the other trappings that go with a modern OS. Plus all the apps are made with higher-level libraries that incur more overhead themselves, but lead to better software in the end. I'll bet Win95 would be pretty snappy on my Athlon too.
1. Put a cd in your drive upside down.
2. Double click on "My Computer"
3. Watch the window try to appear
4. Wait as your drive tries to read the label of your cd in vain.
5. After the timeout, see all the icons pop up in explorer.
http://lwn.net/Articles/84583/
Not Invented Here
And me - several times now. Other searches seem to work though...
For what it's worth, those numbers can be misleading. They measure the size of the process address space, but that includes mmap'ed libraries. (i.e. stuff that's not necessarily loaded yet or may never be) A somewhat more accurate measure is to turn on the "VM Size" column, but I'm not sure exactly what that measures.
99.84 percent spam? Must be asdf.com.
Hear hear! There was something bugging me about this article and you've articulated it exactly. Coding for maintainability, clarity, and correctness is far more important than optimization. Increase in computer speed and size allows not only the luxury of additional features but more importantly the ability to work at a higher level and get more done.
extern "C" {
.
.
.
}
I've always thought The Little Schemer would be good for this kind of thing.
So, just where DO you buy your crack?
Depends what you use it for. If you're folding up method definitions, sure it's the same thing effectively. But there are other places where it helps a WHOLE lot - like when you're using a GUI builder that puts gobs of generated code in different places. Just set it up to fold over the auto-generation delimiters it puts in the file and you can read your code much more easily. I've used it for that in VS.NET, with the gui builder. Eclipse's VE works in very much the same way, so it should be very useful there.
It also works well with any other application where you have a horde of boilerplate code that you want to ignore but don't want to or can't factor out.
Both, until you look.
What's the superposition of YOUR OS?