Apple has already put capslock protection into their keyboards. It works really well in practice, I haven't accidentally engaged the capslock since I got this on a keyboard in 2008.
That's the point. He doesn't "have to." Every techie (possibly except him, though I doubt it) understood this years ago. By saying this now, though, he gets attention.
Apple allows external Mac applications to sync iTunes music to devices other than the iPod. It's the integrated-into-iTunes thing that's a little sketchy. I'm not sure Apple will bother blocking it, though they may rather than going to the effort of properly labeling the Pre in the UI. Leaving iTunes as is, with the device labeled as an iPod, probably isn't going to happen.
I found (and measured) 10.3 faster than 10.2 on my then-computer, and 10.4 faster than 10.3 (once indexing was complete). Numbers long since lost, though, sorry.
Aside from technology being a bit more advanced, it's faithful. It's a parallel universe story and things do diverge fairly quickly, but that's explained by the end of the movie.
Imagine Yesterday's Enterprise with fewer big-picture changes (at least at the start of the movie), and more personal ones for the main characters. And they figure out what's going on, but have no way to fix things.
Because it couldn't possibly be that Apple users like the products, is that the thinking?
Anyone looking to hire Apple shills: I'm available! Mind you, I'll say good things about products I like for free, and that *usually* includes Apple products. So I'm probably not a great place to spend $$$.
Err, I don't see how you could read it that way. Every good point in the article towards Apple is "other manufacturers do this, too." The prices are compared to the most common vendors that come in higher, but doesn't say that Apple's prices are in any way exceptionally low. It seems pretty balanced to me.
But regardless of how balanced it is, it's very informative: Mere mortals do not get this kind of information out of Apple. You certainly won't find it in any brochure.
The term has a specific meaning. You're not using it correctly. You can argue whatever you like about whether it was a good ending or not, I don't really care: you're using the term wrong.
SQLite locks the entire database (a single file) using the file system. This is fast and simple, but breaks down when you have a lot of tasks trying to update the database at once. Fixing it would introduce a lot more complexity, so they're just not going to do it.
If you need a lot of concurrent updates, SQLite is clearly not your engine.
The best description I ever read was that SQLite was a replacement for fopen, not a RDBMS.
But I've always been curious where else (if anywhere) it really fails as a database.
I've run into some poorly-performing queries, but I'm not convinced a "real" database would handle any of them any better.
The query optimizer is weak (that it exists at all is something of a surprise), but that's just a matter of tuning queries better. The query optimizer rarely causes trouble, and in that case you just disable it using CROSS JOIN instead of JOIN.
Lack of foreign key constraints is troubling, but not critical.
"Manifest typing," (store anything in any column) combined with "column affinity," (convent if possible to the column's type, but store anyway if you can't) is as often an advantage as a disadvantage.
So I'd say SQLite is a good pick for non-server applications, and possibly small-scale server applications where a "real" database isn't available. Certainly, I wouldn't hesitate to use it in a desktop (or embedded) application, but I'd probably use something else on a server. Particularly since that "something else" would probably already be installed and running.
The only one of those examples that came close was her vanishing at the end of the finale. But it resolved no loose ends, instead adding one of its own. There's a long standing tradition of allowing just this kind of twist to an ending in modern story telling, and if anything it seems to becoming more acceptable.
The first one that springs to mind is Phone Booth, where the caller inexplicably escapes and gets close to the main character, but I'm sure you can think of a thousand more.
When I posted that original reply, I'd misread what you wrote and thought you said SQLite had a huge speed advantage over MySQL. They're usually comparable, with some operations being faster for one or the other. I don't think speed is a good reason to pick one or the other, given how different they are in other ways, and from the way I'd misunderstood your question I was really wondering what you'd come up with.
But now that I actually understand what you wrote (heh): what areas does a real database system have a huge speed advantage? Concurrency, certainly, is a big weakness of SQLite (though it isn't bad in the small scale).
Do you have any benchmarks that back up MySQL being faster than SQLite? Ever set I've seen has SQLite being slightly faster on most operations, which makes a lot more sense considering how much less work it does.
I was saying a year only because some of the elements were only thrown in at the very end of season 3: Kara having the coordinates to a new world. But you're right that other elements have existed a lot longer than a single year.
That's not exactly what we're saying. What we're saying is dues ex machina requires the miracle (for lack of a better term) to be just hacked on to the end. If you establish before the end, it's by definition not dues ex machina.
That doesn't mean it's a good ending. You're absolutely welcome to hate it. I can totally respect someone not liking that ending. But claiming it's dues ex machina makes you look like an ignorant fool to anyone who knows what the term actually means.
Establishing that such things are not just possible but commonplace in the universe, foreshadowing to the audience and visions to the characters, and having characters tell you all along what's going to happen does.
Slashdot Mirror
Apple has already put capslock protection into their keyboards. It works really well in practice, I haven't accidentally engaged the capslock since I got this on a keyboard in 2008.
That's the point. He doesn't "have to." Every techie (possibly except him, though I doubt it) understood this years ago. By saying this now, though, he gets attention.
Stallman feeds from attention.
Yes, my thought too. It's much easier to see a trend over time when you ignore the last three data points, isn't it? :)
Apple allows external Mac applications to sync iTunes music to devices other than the iPod. It's the integrated-into-iTunes thing that's a little sketchy. I'm not sure Apple will bother blocking it, though they may rather than going to the effort of properly labeling the Pre in the UI. Leaving iTunes as is, with the device labeled as an iPod, probably isn't going to happen.
I found (and measured) 10.3 faster than 10.2 on my then-computer, and 10.4 faster than 10.3 (once indexing was complete). Numbers long since lost, though, sorry.
Aside from technology being a bit more advanced, it's faithful. It's a parallel universe story and things do diverge fairly quickly, but that's explained by the end of the movie.
Imagine Yesterday's Enterprise with fewer big-picture changes (at least at the start of the movie), and more personal ones for the main characters. And they figure out what's going on, but have no way to fix things.
I think your professor absolute nailed it.
It's mostly about GCC. To build a universal application, you need to use GCC 4. But GCC 4 needs runtime libraries that aren't present on Jaguar.
You can build using GCC 3.3 for PowerPC and GCC 4 for Intel, but who wants to be stuck using GCC 3.3?
So it isn't an API change as much as a RTL change.
You deserve an Insightful or funny upmod for that. I wish I was sure which. :)
Because it couldn't possibly be that Apple users like the products, is that the thinking?
Anyone looking to hire Apple shills: I'm available! Mind you, I'll say good things about products I like for free, and that *usually* includes Apple products. So I'm probably not a great place to spend $$$.
The first hundred times, I'm sure it's better. But the second hundred? And the third?
You need to supply your own pony feed, though.
Err, I don't see how you could read it that way. Every good point in the article towards Apple is "other manufacturers do this, too." The prices are compared to the most common vendors that come in higher, but doesn't say that Apple's prices are in any way exceptionally low. It seems pretty balanced to me.
But regardless of how balanced it is, it's very informative: Mere mortals do not get this kind of information out of Apple. You certainly won't find it in any brochure.
The term has a specific meaning. You're not using it correctly. You can argue whatever you like about whether it was a good ending or not, I don't really care: you're using the term wrong.
SQLite locks the entire database (a single file) using the file system. This is fast and simple, but breaks down when you have a lot of tasks trying to update the database at once. Fixing it would introduce a lot more complexity, so they're just not going to do it.
If you need a lot of concurrent updates, SQLite is clearly not your engine.
The best description I ever read was that SQLite was a replacement for fopen, not a RDBMS.
But I've always been curious where else (if anywhere) it really fails as a database.
So I'd say SQLite is a good pick for non-server applications, and possibly small-scale server applications where a "real" database isn't available. Certainly, I wouldn't hesitate to use it in a desktop (or embedded) application, but I'd probably use something else on a server. Particularly since that "something else" would probably already be installed and running.
No, you're still misusing that term. It's used for resolution, not additional complication.
The only one of those examples that came close was her vanishing at the end of the finale. But it resolved no loose ends, instead adding one of its own. There's a long standing tradition of allowing just this kind of twist to an ending in modern story telling, and if anything it seems to becoming more acceptable.
The first one that springs to mind is Phone Booth, where the caller inexplicably escapes and gets close to the main character, but I'm sure you can think of a thousand more.
When I posted that original reply, I'd misread what you wrote and thought you said SQLite had a huge speed advantage over MySQL. They're usually comparable, with some operations being faster for one or the other. I don't think speed is a good reason to pick one or the other, given how different they are in other ways, and from the way I'd misunderstood your question I was really wondering what you'd come up with.
But now that I actually understand what you wrote (heh): what areas does a real database system have a huge speed advantage? Concurrency, certainly, is a big weakness of SQLite (though it isn't bad in the small scale).
Do you have any benchmarks that back up MySQL being faster than SQLite? Ever set I've seen has SQLite being slightly faster on most operations, which makes a lot more sense considering how much less work it does.
I was saying a year only because some of the elements were only thrown in at the very end of season 3: Kara having the coordinates to a new world. But you're right that other elements have existed a lot longer than a single year.
You're using the fallacy of necessity. I'm not buying.
I require it to meet the actual definition of deus ex machina, which has a specific meaning.
That's not exactly what we're saying. What we're saying is dues ex machina requires the miracle (for lack of a better term) to be just hacked on to the end. If you establish before the end, it's by definition not dues ex machina.
That doesn't mean it's a good ending. You're absolutely welcome to hate it. I can totally respect someone not liking that ending. But claiming it's dues ex machina makes you look like an ignorant fool to anyone who knows what the term actually means.
Establishing that such things are not just possible but commonplace in the universe, foreshadowing to the audience and visions to the characters, and having characters tell you all along what's going to happen does.
Yes, I think you're right. I would have been happier about this had she been shown at the end in New York, though.