2,051 karma · joined December 17, 2010
I think that Bezos quote is actually very Apple-like, what with "people are going to love these" and so on.
It is also a practical test of the thought experiment that wonders whether an infinite number of monkeys pounding on an infinite number of typewriters would be able to produce Shakespeare's works by accident.
is rather idiotic. Nobody "wonders" whether this'll work. Of course it'll work. It's a mathematical certainty. It just... takes a while.
And that was in the 70s, imagine what stuff they've got up there right now!
All those terms sometimes get used differently in different contexts sometimes, but I think that's what's usually meant by them.
What a waste...
edit: Seriously, wouldn't this be so much cooler if it gave us a new way to explore mathematical and scientific data?
If we could draw any curve and it would present us with matching constants, physical laws, mathematical proofs & theorems that have some correlation with the input data, chemical and biological data points, information from sociological studies, historical statistics...
That's a pretty bullshit excuse. Wasn't the insurance file on PirateBay? How exactly should they have removed that once it was out there?
They put a computer in every home.
But of course, you don't really need closures for that. For example, Cocoa does it this way:
- (void)deleteLineAtRow:(NSUInteger)row {
NSString *deletedLine = [self lineAtRow:row];
[[self.undoManager prepareWithInvocationTarget:self] insertLine:deletedLine atRow:row];
// do actual deletion
}
- (void)insertLine:(NSString *)line atRow:(NSUInteger)row {
[[self.undoManager prepareWithInvocationTarget:self] deleteLineAtRow:row];
// do actual insertion
}
That -prepareWithInvocation: stuff tells the undoManager to store the next message sent to it, along with it's parameters, on an internal stack. This is of course depends on Objective-C's dynamic nature and there's a whole lot of complexity hidden inside the undo manager object.But mixing this undo manager concept with closures should be pretty straightforward, resulting in something like this (note that this is a hypothetical example; Cocoa does not currently implement this functionality):
- (void)deleteLineAtRow:(NSUInteger)row {
NSString *deletedLine = [self lineAtRow:row];
[self.undoManager registerUndoWithBlock:^{
[self insertLine:deletedLine atRow:row];
}];
// do actual deletion
}
- (void)insertLine:(NSString *)line atRow:(NSUInteger)row {
[self.undoManager registerUndoWithBlock:^{
[self deleteLineAtRow:row];
}];
// do actual insertion
}On other platforms different screen sizes aren't a problem since that's been the norm from the very beginning. But why shouldn't we be able to make assumptions on iOS? It's an entirely different environment, one where, among other things, screen size and aspect ratio are fixed.
And yes, I don't think you should hardcode every last pixel in your iOS app either, but it's perfectly acceptable for your graphics to rely on the documented sizes. How should e.g. GarageBand account for a suddenly different aspect ratio?
While you shouldn't ever make assumptions about CPU or memory specifics (which is why apple doesn't release that information, even to developers) you absolutely can make assumptions about screen size and aspect ratio. Sure, Apple changing the system font shouldn't cripple your app. But having to code for every possible hardware configuration? What is this, Android?
And at the bottom: Last Modified on April 27 2007 08:01:26 UTC
This right here disqualifies any legitimate point you might have made in your post.
http://stream.hpi.uni-potsdam.de:8080/download/podcast/HPIK_...
http://stream.hpi.uni-potsdam.de:8080/download/podcast/HPIK_...
http://stream.hpi.uni-potsdam.de:8080/download/podcast/HPIK_...
http://stream.hpi.uni-potsdam.de:8080/download/podcast/HPIK_...