Then apparently you haven't studied it enough. We're not talking about cooperative multi-threading. A true, honest to God thread gets spawned to handled these requests. "Cooperative multithreading" is the practice of scheduling processing and voluntarily using a limited amount of time for each turn. That's feasible without Gears or HTML5, but it's not what the XMLHttpRequest object does.
I think you guys are both missing the point. Asynchronous means asynchronous. That's it. It doesn't imply preemptive threading, and it doesn't imply cooperative threading. It just means asynchronous. Asynrchonousity can be implemented many ways. You could have one thread per asynrchonous call, or one thread for all asynchronous calls, or kernel support, it's really depends on the design and implementation of the library/API. They all have trade offs. You're both right, and you're both wrong. "Multi-threaded" isn't a feature. "Responsive" is a feature and there are many ways to get there, and that they're stable, and perform well is what really matters.
I don't mean to troll, but "Imagine how good life would be if only money wasn't an issue..." You can replace 'life' and 'money' with whatever you feel provides the best example. The point is that problems and solutions are really only interesting when they have constraints.
Categories are *the* best feature of Objective-C. They let you keep problems object orrient when subclassing isn't avaiable. Simple example. Say you're working with a class library that exports a string class, and that string class doesn't have a 'spit/explode' function. In languages without categories you would write a static method some place, or a method on some unrelated 'toolbox' class that takes a string and splits it. In objective-c, you can just put a category on string that is a split method. This way the string is doing the split. If you later hve some subclass of string that can do a more efficent split, well override split, dont' swtich on the class type in your static method. YAY OO.
I hinted on a much more important feature above. When you have to work with many objects that you know little about, categories are awesome. Take GORM for example. GORM should integrate with many flavores of objects but it really only knows a lot about a couple of base-classes. Classes like view, object, and window. GORM might need to know if a view acts as a container. To do this, it might put a category method on view called 'isContainer'. It could return NO by default and be overrided in all containers to return YES. Now when working with a view, GORM just has to say [view isContainer] to find out if the view is a container. This is much better than looking asside in some table, or manually coding up the reflection hack that would be nessecary to ask such a question in other statically bound/typed languages.
I think you missed the point. It can make computers start up faster because the cache can be consistent across power-down power-up cycles. Flash memory is persistent. If disk sectors that represent files like system32.dll are always hot, they can be in the flash cache when the system is powered up before it has read a byte from disk.
An obvious fault that seems to go with out notice about garbage collectors, particularly stop-and-copy collectors is that when ever they do the full blow stop and copy, they have to touch all of those memory pages, and fault all of your virtual memory back into ram.
My experience is that C# is pretty good, on par with java. and C++ is C++, MS bastardizes it a little but it isn't that bad. But the major selling point of VS.NET isn't the.NET part, its the VS part.
The IDE kicks ass. it's just that simple. I know you may be able to code like a pro with emacs if you know all of the key combos, but the combo boxes that pop up when you type giving you on the fly documentation and revealing the classes/functions available to you is a god send.
VS is just an awesome IDE that makes up for any short coming of.NET, which i haven't found many.
There is a sendmail binary that isn't send mail, its a simlink(?) to another email client.
I can't remember if it is a sim link, or an actual binary that just converts the command line args to what is expected by the other email server... i'm not on my mac now.
But either way, there is something there called sendmail, that isn't sendmail for compatibility reasons.
If your in a public location using a hotspot the only transfers your most likely going to be doing are to/from the internet, not to/from your 1337 mp3 s3v3r box. Chances are the hot spots inet connection is ~1mbps anyway.
I think he's saying that the 'features' come from the Apps, not the DB, and the end user doensn't really care if it's DB2, Orical, PostgresSQL, or MySQL, just as long as it runs the apps.
Course not;) I'm glad to see you recognized me. You're right making money is a side affect. I really enjoy writing the software. I've been enjoying it quite a lot lately. Hopefully you'll be able to try out my next release and enjoy using it as much as I enjoyed writing it.
Clearly the GPL has benefitted many people and businesses. The fact that Microsoft isn't collectively smart enough to figure out a business model that will allow them to benefit from it isn't anyone's problem than theirs, and certainly doesn't make the GPL a bad thing.
Slashdot Mirror
Instapaper is great for this type of thing: http://instapaper.com./
I think you guys are both missing the point. Asynchronous means asynchronous. That's it. It doesn't imply preemptive threading, and it doesn't imply cooperative threading. It just means asynchronous. Asynrchonousity can be implemented many ways. You could have one thread per asynrchonous call, or one thread for all asynchronous calls, or kernel support, it's really depends on the design and implementation of the library/API. They all have trade offs. You're both right, and you're both wrong. "Multi-threaded" isn't a feature. "Responsive" is a feature and there are many ways to get there, and that they're stable, and perform well is what really matters.
I don't mean to troll, but "Imagine how good life would be if only money wasn't an issue..." You can replace 'life' and 'money' with whatever you feel provides the best example. The point is that problems and solutions are really only interesting when they have constraints.
If you have $300.00 to drop on an iPod, chances are, you don't mind spending 99c on music.
Even though many are cheaper now, I bet a substantial number of iPods sold have been at price points near $300.00.
Categories are *the* best feature of Objective-C. They let you keep problems object orrient when subclassing isn't avaiable. Simple example. Say you're working with a class library that exports a string class, and that string class doesn't have a 'spit/explode' function. In languages without categories you would write a static method some place, or a method on some unrelated 'toolbox' class that takes a string and splits it. In objective-c, you can just put a category on string that is a split method. This way the string is doing the split. If you later hve some subclass of string that can do a more efficent split, well override split, dont' swtich on the class type in your static method. YAY OO.
I hinted on a much more important feature above. When you have to work with many objects that you know little about, categories are awesome. Take GORM for example. GORM should integrate with many flavores of objects but it really only knows a lot about a couple of base-classes. Classes like view, object, and window. GORM might need to know if a view acts as a container. To do this, it might put a category method on view called 'isContainer'. It could return NO by default and be overrided in all containers to return YES. Now when working with a view, GORM just has to say [view isContainer] to find out if the view is a container. This is much better than looking asside in some table, or manually coding up the reflection hack that would be nessecary to ask such a question in other statically bound/typed languages.
I think you missed the point. It can make computers start up faster because the cache can be consistent across power-down power-up cycles. Flash memory is persistent. If disk sectors that represent files like system32.dll are always hot, they can be in the flash cache when the system is powered up before it has read a byte from disk.
I'm sure the police thought he was the theif.
That is called ex post facto and the constitution explicitly forbids it.
o .h tm
http://www.law.cornell.edu/lexicon/ex_post_fact
An obvious fault that seems to go with out notice about garbage collectors, particularly stop-and-copy collectors is that when ever they do the full blow stop and copy, they have to touch all of those memory pages, and fault all of your virtual memory back into ram.
I bet you'd also flip out if they didn't test it with FB 0.7 on Linux and then it ate your data.
Um, what about the first time you plug it into your computer and it syncs 20gigs?
I use mine in this fashion regulary.
I for one welcome the new-small-boxes-that-fit-on-our-bookselfs overlords.
inconceivable
My experience is that C# is pretty good, on par with java. and C++ is C++, MS bastardizes it a little but it isn't that bad. But the major selling point of VS.NET isn't the .NET part, its the VS part.
.NET, which i haven't found many.
The IDE kicks ass. it's just that simple. I know you may be able to code like a pro with emacs if you know all of the key combos, but the combo boxes that pop up when you type giving you on the fly documentation and revealing the classes/functions available to you is a god send.
VS is just an awesome IDE that makes up for any short coming of
There is a sendmail binary that isn't send mail, its a simlink(?) to another email client.
I can't remember if it is a sim link, or an actual binary that just converts the command line args to what is expected by the other email server... i'm not on my mac now.
But either way, there is something there called sendmail, that isn't sendmail for compatibility reasons.
If your in a public location using a hotspot the only transfers your most likely going to be doing are to/from the internet, not to/from your 1337 mp3 s3v3r box. Chances are the hot spots inet connection is ~1mbps anyway.
I agree with both you guys, but he said "Computer Scientist" were normally an engineer/implementer would care about the 10, a scientist would not.
And you are a computer scientist? I mean, not to troll, but scientists care about the Big O, not the C.
The factor of ten is irrelevant, solving the problem asymptotic faster would be much more impressive - like lg n vs n^2.
Try out OS X, not classic :( some time.
And that a bunch of other OS's use it's code, that's what's meant by the children part.
I think he's saying that the 'features' come from the Apps, not the DB, and the end user doensn't really care if it's DB2, Orical, PostgresSQL, or MySQL, just as long as it runs the apps.
Glad you like it. My AIM screen name's Vandel405 if you want to IM me sometime.
Course not ;) I'm glad to see you recognized me. You're right making money is a side affect. I really enjoy writing the software. I've been enjoying it quite a lot lately. Hopefully you'll be able to try out my next release and enjoy using it as much as I enjoyed writing it.
Have fun -
Jon
pff, Well if downloading mp3s off napster is legal, then I don't see what's wrong with sampling!