but the source or the java libraries IS available. i've been able to look at the source for the standard libraries for years (it's available with the Sun SDK). so am i missing something or are you complaining about the license the source is available under? if it's the second, why? why would java need to be under a more GPL like license? what are the real benefits?
you probably got modded up because you lied about your relation to the story, essentially claiming that you heard the story directly from the source ('I heard an American sniper tell a story...'), when it appears that you absolutely did not. but good job pointing out how distasteful disney's disney based-on-a-true-stories are being 99% fiction, 1% facts.
maybe these super top secret features can be hacked together and made available for linux or microsoft within a few 'hours' but in both cases they'd generally take much longer (less for linux, more for ms) to make it into an official distribution.
if apple announced and demoed all of their super top secret features for leopard now, there would certainly be plenty of time for ms to get them in to vista if they're useful/flashy enough and thus apple would lose a little lead on microsoft. apple wants to be able to say "we're ahead of microsoft" and if a feature doesn't make it into the initial release of vista, it will usually be quite a while before it makes it in and this is exactly how apple needs to act if it wants to eat into microsoft's space.
The separation of support and development will probably not reassure 'corporate types.' In general, it is better from their perspective, that these two entities are relatively tightly coupled as when an actual product defect is found that prevents some business function in their enterprise from working, they'd really like to know that the people they have the support contract with have a tight and integrated relationship with the development team such that they can more easily get a production level fix created for their problem. The clear separation between support and development makes this much more difficult both in perception and actual practice.
with the appropriate implementation, a case aware but case insensitive file system is essentially equivalent to a filesystem allowing only lowercase characters (but allowing for a display name including mixed case). this makes most of your issues go away (most operations just need to canonicalize the input filenames to the lowercase equivalent and then perform the operation as if the filesystem were case sensitive) completely as well as fixing a normal user searching for "foo*" as they may or may not remember exactly if the document is really "Foo*" or "fOo*" or some other variant. the only issue left is if the user really does want a case sensitive search for "foo*" as they know they have a lot of documents that are "Foo*" or "foo*" but only want the latter. this really isn't nearly as common as the first instance and should not be the case the system is optimized for.
when designing for a user, very very rarely (never) should you make something harder for the user but easier for the programmer. as many have already pointed out, most users really want case aware case insensitive filesystems.
i'll grant you the fish and prawns though a freezer can fix that problem (they were generally frozen before they got to the store, so it's not like they'll be much less 'fresh').
as for the bread, i presume you're talking a loaf of fresh bakery bread (with no preservatives) which is definitely not the normally consumed bread in the US. we'll take our prepackaged loaf with preservatives and the bread will easily last a week or so. but bakery bread can be kept fresher a bit longer using an appropriate bread box or by placing it in a fridge. some people freeze the bread so that it lasts as long as they need it, others don't like the hassle.
none of these things is an issue such that it would force someone to go to the market every day. if it is, that's a problem with the store.
where the hell do you get your fresh food that it goes bad within a day of purchasing it? because you've got to start shopping somewhere else.
additionally, if you're buying a weeks worth of fruit, it's a good idea to buy at varying levels of ripeness. that way you can eat them when they're properly ripe.
additionally, using the alt key is the standard (maybe not adhered to so well) on windows when accessing a mnemonic in a dialog. so forcing the alt-t from the ctl-alt-del screen is actually just fixing an accessibility/consistency issue.
there is no sensible reason for netflix to want to reward high volume. higher priority for higher volume is not only a bad business decision (since netflix is just a flat fee), but it would also reward those people who receive their movies, copy them illegally, and then return the movies immediately.
from a business point of view, netflix wants to reward those users who watch only a couple a month. low volume users will usually not have huge queues and so they'll want to be able to receive the movies that are in their queue - precisely those movies which are harder to get anyway - in a timely fashion. otherwise there's a good chance they'll stop the service. medium volume users will generally watch enough enough/have enough in their queue that they'll always having something and not really notice/care about any throttling. high volume users that are illegally copying the movies will often resign themselves to the fact that they can't get the theoretical maximum number of movies as they're stealing the movies anyway, getting a large collection for a fraction of the normal cost. high volume users that are legally watching all their movies are relatively few and far between and, currently, lacking a better option (they're still getting a fantastic rental deal) that they'll stay -- they're also less likely to care significantly about the latest release.
rewarding high volume users breaks this entirely. not only will it increase illegal copying it will make it much harder (and not easier) for medium and lower volume viewers to get what they want to watch as movies returned immediately by high volume users more likely go to other high volume viewers. doing this would put netflix out of business.
presumably the data that would be written to local by the cell isn't data that typically should be read back by the cell. so writing it to local actually keeps that traffic completely off the main memory bus (it doesn't get written there so it can't be read from there) and so it actually LESSENS the contention on the main memory bus.
someone else might be. with multi core, multi processor architectures where i need to write may not ever be a place i need to read from. so why make that fast?
There are multiple DRM schemas and while none of them 'command the market', ALL are playable on an Origami device while NONE are playable on Pepper Pad. If you want to argue that that is not a problem for the Pepper Pad's target customers (i.e. Linux and open source diehards) that's fine. But it's not a feature (as claimed in your review video) and it severely limits the Pepper Pad's usefulness outside of that narrow market. All in all, not a great idea.
For those of us who don't like DRM, and do like open source, I wanted to talk about the Pepper Pad in comparison to Origami.
Ignoring it's other drawbacks, the fact that the Pepper Pad can't play DRMed music and the Origami can is a serious one. Whatever your feelings on DRMed music neither the Pepper Pad or the Origami would ever be creating that DRMed music, only play it. And if someone's got DRMed music the Pepper Pad is useless. You can try to argue that if no players played DRMed music then all music producers would put out music that contains no DRM, but I think then you've probably been riding the open source bandwagon a little too long. Instead they'd just not distribute it at all. Claiming, in the video in the review, that this (not playing DRM) is a feature is ridiculous.
You can use the ClearType Tuning wizard to make the ClearType look much better on your display (LCD or CRT) if you don't want to turn it off completely. Using this should rid you of the 'bolding' look which I think just happens because ClearType tends to make text look much thicker, but with tuning this should be easy to take care of. Personally, I find that with it tuned properly text does look much better and is easier to look at for long durations than with ClearType off, but obviously that's a personal preference.
While ClearType is intended mainly for LCDs it can make text on CRTs look much better as well (of course it will come down to personal preference, but I find the text on my CRT much more readable over long periods of time with ClearType enabled). In either case, it's a very good idea to use the ClearType tuning wizard that MS provides to try to optimize the output of ClearType for your specific display.
your analogy is ridiculous. what you're saying is that if the component that your car runs on (gas) becomes product specific (Ford) you could be screwed. let's move this to computers. the component that your car runs on (electricity) becomes product specific (Windows only) you could be screwed. ok. but what's that have to do with microsoft. oh. what you want to say is that a specific brand of car (Ford) comes with a sunroof that isn't very good. and you want to replace it with a better sunroof, but Ford won't let you. valid complaint. but MY POINT is that most people will say "it's got a sunroof. that works for me. so who cares if i could have a better sunroof, the one that's there does what i want it to."
P.S. the real reason that Lotus wouldn't run is that it just plain sucks.
Slashdot Mirror
but the source or the java libraries IS available. i've been able to look at the source for the standard libraries for years (it's available with the Sun SDK). so am i missing something or are you complaining about the license the source is available under? if it's the second, why? why would java need to be under a more GPL like license? what are the real benefits?
you probably got modded up because you lied about your relation to the story, essentially claiming that you heard the story directly from the source ('I heard an American sniper tell a story...'), when it appears that you absolutely did not. but good job pointing out how distasteful disney's disney based-on-a-true-stories are being 99% fiction, 1% facts.
maybe these super top secret features can be hacked together and made available for linux or microsoft within a few 'hours' but in both cases they'd generally take much longer (less for linux, more for ms) to make it into an official distribution.
if apple announced and demoed all of their super top secret features for leopard now, there would certainly be plenty of time for ms to get them in to vista if they're useful/flashy enough and thus apple would lose a little lead on microsoft. apple wants to be able to say "we're ahead of microsoft" and if a feature doesn't make it into the initial release of vista, it will usually be quite a while before it makes it in and this is exactly how apple needs to act if it wants to eat into microsoft's space.
and that's entirely due to the fact that it is not
The separation of support and development will probably not reassure 'corporate types.' In general, it is better from their perspective, that these two entities are relatively tightly coupled as when an actual product defect is found that prevents some business function in their enterprise from working, they'd really like to know that the people they have the support contract with have a tight and integrated relationship with the development team such that they can more easily get a production level fix created for their problem. The clear separation between support and development makes this much more difficult both in perception and actual practice.
long enough for china to produce a device that will make their turning the flag on moot as well.
with the appropriate implementation, a case aware but case insensitive file system is essentially equivalent to a filesystem allowing only lowercase characters (but allowing for a display name including mixed case). this makes most of your issues go away (most operations just need to canonicalize the input filenames to the lowercase equivalent and then perform the operation as if the filesystem were case sensitive) completely as well as fixing a normal user searching for "foo*" as they may or may not remember exactly if the document is really "Foo*" or "fOo*" or some other variant. the only issue left is if the user really does want a case sensitive search for "foo*" as they know they have a lot of documents that are "Foo*" or "foo*" but only want the latter. this really isn't nearly as common as the first instance and should not be the case the system is optimized for.
when designing for a user, very very rarely (never) should you make something harder for the user but easier for the programmer. as many have already pointed out, most users really want case aware case insensitive filesystems.
i'll grant you the fish and prawns though a freezer can fix that problem (they were generally frozen before they got to the store, so it's not like they'll be much less 'fresh').
as for the bread, i presume you're talking a loaf of fresh bakery bread (with no preservatives) which is definitely not the normally consumed bread in the US. we'll take our prepackaged loaf with preservatives and the bread will easily last a week or so. but bakery bread can be kept fresher a bit longer using an appropriate bread box or by placing it in a fridge. some people freeze the bread so that it lasts as long as they need it, others don't like the hassle.
none of these things is an issue such that it would force someone to go to the market every day. if it is, that's a problem with the store.
where the hell do you get your fresh food that it goes bad within a day of purchasing it? because you've got to start shopping somewhere else.
additionally, if you're buying a weeks worth of fruit, it's a good idea to buy at varying levels of ripeness. that way you can eat them when they're properly ripe.
additionally, using the alt key is the standard (maybe not adhered to so well) on windows when accessing a mnemonic in a dialog. so forcing the alt-t from the ctl-alt-del screen is actually just fixing an accessibility/consistency issue.
there is no sensible reason for netflix to want to reward high volume. higher priority for higher volume is not only a bad business decision (since netflix is just a flat fee), but it would also reward those people who receive their movies, copy them illegally, and then return the movies immediately.
from a business point of view, netflix wants to reward those users who watch only a couple a month. low volume users will usually not have huge queues and so they'll want to be able to receive the movies that are in their queue - precisely those movies which are harder to get anyway - in a timely fashion. otherwise there's a good chance they'll stop the service. medium volume users will generally watch enough enough/have enough in their queue that they'll always having something and not really notice/care about any throttling. high volume users that are illegally copying the movies will often resign themselves to the fact that they can't get the theoretical maximum number of movies as they're stealing the movies anyway, getting a large collection for a fraction of the normal cost. high volume users that are legally watching all their movies are relatively few and far between and, currently, lacking a better option (they're still getting a fantastic rental deal) that they'll stay -- they're also less likely to care significantly about the latest release.
rewarding high volume users breaks this entirely. not only will it increase illegal copying it will make it much harder (and not easier) for medium and lower volume viewers to get what they want to watch as movies returned immediately by high volume users more likely go to other high volume viewers. doing this would put netflix out of business.
presumably the data that would be written to local by the cell isn't data that typically should be read back by the cell. so writing it to local actually keeps that traffic completely off the main memory bus (it doesn't get written there so it can't be read from there) and so it actually LESSENS the contention on the main memory bus.
or that's my guess.
someone else might be. with multi core, multi processor architectures where i need to write may not ever be a place i need to read from. so why make that fast?
i think you're probably stretching the concept of negligence.
Actually, Origami runs Win XP Tablet edition. Meaning that it clearly runs iTunes and so Apple's DRM is playable on Origami.
There are multiple DRM schemas and while none of them 'command the market', ALL are playable on an Origami device while NONE are playable on Pepper Pad. If you want to argue that that is not a problem for the Pepper Pad's target customers (i.e. Linux and open source diehards) that's fine. But it's not a feature (as claimed in your review video) and it severely limits the Pepper Pad's usefulness outside of that narrow market. All in all, not a great idea.
Ignoring it's other drawbacks, the fact that the Pepper Pad can't play DRMed music and the Origami can is a serious one. Whatever your feelings on DRMed music neither the Pepper Pad or the Origami would ever be creating that DRMed music, only play it. And if someone's got DRMed music the Pepper Pad is useless. You can try to argue that if no players played DRMed music then all music producers would put out music that contains no DRM, but I think then you've probably been riding the open source bandwagon a little too long. Instead they'd just not distribute it at all. Claiming, in the video in the review, that this (not playing DRM) is a feature is ridiculous.
You can use the ClearType Tuning wizard to make the ClearType look much better on your display (LCD or CRT) if you don't want to turn it off completely. Using this should rid you of the 'bolding' look which I think just happens because ClearType tends to make text look much thicker, but with tuning this should be easy to take care of. Personally, I find that with it tuned properly text does look much better and is easier to look at for long durations than with ClearType off, but obviously that's a personal preference.
While ClearType is intended mainly for LCDs it can make text on CRTs look much better as well (of course it will come down to personal preference, but I find the text on my CRT much more readable over long periods of time with ClearType enabled). In either case, it's a very good idea to use the ClearType tuning wizard that MS provides to try to optimize the output of ClearType for your specific display.
have you considered a mobile amp?
i smell class action lawsuit
fyi, when you search in firefox's search bar, pressing alt-enter will open the result in a new tab.
and that is why blu-ray will win.
your analogy is ridiculous. what you're saying is that if the component that your car runs on (gas) becomes product specific (Ford) you could be screwed. let's move this to computers. the component that your car runs on (electricity) becomes product specific (Windows only) you could be screwed. ok. but what's that have to do with microsoft. oh. what you want to say is that a specific brand of car (Ford) comes with a sunroof that isn't very good. and you want to replace it with a better sunroof, but Ford won't let you. valid complaint. but MY POINT is that most people will say "it's got a sunroof. that works for me. so who cares if i could have a better sunroof, the one that's there does what i want it to."
P.S. the real reason that Lotus wouldn't run is that it just plain sucks.
then 4/5 of gas stations would go out of business.
IDIOT!