Nintendo aims to make a profit on its hardware. Microsoft and Sony are willing to support massive losses on the hardware sales in order to gain market share. Both those companies have other businesses that can support them while doing this. Nintendo doesn't really.
Nintendo's competitors will always put out much more powerful hardware platforms because they're willing to lose a lot of money to do so, gambling that they will eventually become profitable over the long run. This generation, that gamble doesn't seem to have paid off well for Sony. I'm not sure how Microsoft did. They lost quite a big bundle on those pre-Jasper Xbox 360s, but they seem to have climbed out of that pit.
Given that their competition is willing to push those stakes so high, you could argue that it's essential that Nintendo take a different tack.
Having said that, it really seems like they should consider commodity hardware platforms as a base for future products. When you've got a bunch of companies who are already taking the performance/cost gamble for you, and who are coming up with hardware that beats most custom products, it's almost silly to ignore it.
> Let's see: there's iOS and Android, and what else really?
You're not a developer, I see. You need to multiply all the commonly-used versions of iOS and Android by all the different base hardware platforms, then figure out other factors such as screen size & density and platform-specific quirks. Compound that by the fact that new OS versions and new hardware platforms come out every month, and you've got quite an impressive matrix, assuming you care about supporting them well.
Sorry, that info dates to the N64. All the systems since then have been easy to program. What might have made the Wii difficult was just the fact that it didn't have programmable shaders whereas its competitors did.
"Sumagen’s HIV/AIDS vaccine is also supported for its R&D cost from the HIV/AIDS vaccine development fund, jointly launched by the Bill and Melinda Gates Foundation and the government of Canada."
Indeed, most cables you get already come with wire ties. Instead of just throwing away the tie and unraveling the whole length, you should only lengthen the cable as much as you need, then use the tie to secure the rest. If you happen to need the whole length, then wrap the wire tie around the cable end. You can use it later when you either need less, or you need to put the whole cable away. (Keeping your cables tied up when you put things in a drawer or box helps prevent creating a tangled mess of cable spaghetti.)
And when you plug in something new, take care to route the cable in a sensible way. Don't just thread it through wherever there's space, but try to put it below things more likely to move, and above things less likely to move, and together with similarly-routed cables.
Having said all this, if you have enough gadgets, you will end up with some cable mess. Either live with it, or deal with spending time to clean it up (and undo/redo it each time stuff shifts around).
It doesn't necessarily mean "change the core of who you are to be more like others".
It can also mean "change how you interact with others to avoid being preyed upon". And this doesn't mean "permanently change", but rather "dynamically change, according to needs of the situation".
If you can't distinguish between appropriate and inappropriate behavior, you're going to have a hard time, regardless of the details.
There is no image of the camera, but just the body of the rover and its surroundings.
You can do the same thing yourself by taking a a few of images of yourself with your arm bent in different directions (ie, elbow forward, elbow back) while still keeping the camera in more or less the same place. You can then stitch them together and your arm will disappear. Or, you can make it look like you have multiple arms.
The (Bosch) fuel pump on my old Saab was inside the gas tank. Gas ran through the motor to keep it cool. I suppose that since gas isn't conductive, a completely submersible fuel pump is even easier to make than a submersible water pump (as used in deep wells).
If the whole purpose of the backup system is to provide electrical power, then you'd think they'd consider the power sources needed for it.
We generally assume that the purpose of a backup system is to actually operate when the main system fails. Providing assurance that it will is an engineering job that requires enumerating the possible failure modes and providing contingencies for them. The customer should presumably have that assessment done, then decide which of the contingencies that they'll pay for (hopefully based on some cost/benefit/likelihood balancing strategy).
In this case, either they didn't do the right assessment, or else they didn't think this mode of failure was likely. Either way, you hope they learn something.
If we can figure out how to put a pump into a well full of water deep underground, it should not be too difficult to figure out how to do something similar with a fuel pump, relatively speaking. To have not done so is a fail.
Still would prefer a debate format where each candidate sits in a sound-proof booth, and the moderator controls the mute buttons on each. Not sure about having electric shockers in each chair, though. Maybe that can wait until the next election.
The issue comes into being most likely due to off-by-a-fraction errors when doing non-integer scaling of multiple elements.
One solution is just to get all your fractions right across the entire rendering pipeline. That is hard, and maybe impossible in some cases.
An easier solution is just to render to a canvas that is an integer multiple of the "base" or "expected" case, then finally apply a single scaling from that canvas to the display size at the last moment before the image is displayed.
For instance, let's say that software was developed for a 100 dpi display, and for a given device, that works out to a 1366x768 resolution (if its screen were 100 dpi). Now the screen is really 1920x1080, but that is not an integer multiple of 1366x768, so instead we render to a canvas that is 2x both dimensions: 2732x1536. The rendering here should be without any issues, since it's an integer multiple of 1366x768. From here, there are two paths to follow. If the display controller of the device can automatically scale 2732x1536 to 1920x1080, then let it do that. Otherwise, have the GPU scale the the canvas size to the display size, then display that. (Typically, the display controller can do a better job with multiple tap filters.)
Note that this requires extra rendering power and bandwidth vs. the first solution. However, that's what hardware is good at, right?
Note also that doing non-integer scaling will always result in what looks like "blurriness" around what would have otherwise been sharp pixel edges. This is not avoidable, really (unless you want really ugly results where some lines are fatter than others).
I, for one, hate mobile applications of websites. The regular website should just work well on any platform. That's the whole point of standard platforms.
Of course, I understand that I am free to ignore such apps. However, producing such an app should not be an excuse to not make the website work right.
(And I do understand that making a website "work right" across lots of browsers and platforms is hard. Consider it a challenge that only wimps decline.)
Slashdot Mirror
That's almost certainly a display post-processing step after the Wii's usual graphics pipeline.
I'd imagine that when running in Wii mode, the clock rate is exactly the same as the Wii's.
Nintendo aims to make a profit on its hardware. Microsoft and Sony are willing to support massive losses on the hardware sales in order to gain market share. Both those companies have other businesses that can support them while doing this. Nintendo doesn't really.
Nintendo's competitors will always put out much more powerful hardware platforms because they're willing to lose a lot of money to do so, gambling that they will eventually become profitable over the long run. This generation, that gamble doesn't seem to have paid off well for Sony. I'm not sure how Microsoft did. They lost quite a big bundle on those pre-Jasper Xbox 360s, but they seem to have climbed out of that pit.
Given that their competition is willing to push those stakes so high, you could argue that it's essential that Nintendo take a different tack.
Having said that, it really seems like they should consider commodity hardware platforms as a base for future products. When you've got a bunch of companies who are already taking the performance/cost gamble for you, and who are coming up with hardware that beats most custom products, it's almost silly to ignore it.
> Let's see: there's iOS and Android, and what else really?
You're not a developer, I see. You need to multiply all the commonly-used versions of iOS and Android by all the different base hardware platforms, then figure out other factors such as screen size & density and platform-specific quirks. Compound that by the fact that new OS versions and new hardware platforms come out every month, and you've got quite an impressive matrix, assuming you care about supporting them well.
Sorry, that info dates to the N64. All the systems since then have been easy to program. What might have made the Wii difficult was just the fact that it didn't have programmable shaders whereas its competitors did.
And what kind of extrapolation did they do? Did they use linear extrapolation and somehow believe it would match an exponential demand curve?
(If confused, please watch the Internet's Most IMPORTANT Video http://www.youtube.com/watch?v=umFnrvcS6AQ )
From Sumagen's website:
"Sumagen’s HIV/AIDS vaccine is also supported for its R&D cost from the HIV/AIDS vaccine development fund, jointly launched by the Bill and Melinda Gates Foundation and the government of Canada."
... interrupting my, um... I wonder what's new on Facebook?
Indeed, most cables you get already come with wire ties. Instead of just throwing away the tie and unraveling the whole length, you should only lengthen the cable as much as you need, then use the tie to secure the rest. If you happen to need the whole length, then wrap the wire tie around the cable end. You can use it later when you either need less, or you need to put the whole cable away. (Keeping your cables tied up when you put things in a drawer or box helps prevent creating a tangled mess of cable spaghetti.)
And when you plug in something new, take care to route the cable in a sensible way. Don't just thread it through wherever there's space, but try to put it below things more likely to move, and above things less likely to move, and together with similarly-routed cables.
Having said all this, if you have enough gadgets, you will end up with some cable mess. Either live with it, or deal with spending time to clean it up (and undo/redo it each time stuff shifts around).
Depends how you define "adapt".
It doesn't necessarily mean "change the core of who you are to be more like others".
It can also mean "change how you interact with others to avoid being preyed upon". And this doesn't mean "permanently change", but rather "dynamically change, according to needs of the situation".
If you can't distinguish between appropriate and inappropriate behavior, you're going to have a hard time, regardless of the details.
There is no image of the camera, but just the body of the rover and its surroundings.
You can do the same thing yourself by taking a a few of images of yourself with your arm bent in different directions (ie, elbow forward, elbow back) while still keeping the camera in more or less the same place. You can then stitch them together and your arm will disappear. Or, you can make it look like you have multiple arms.
The information is free. You can download the bits no charge. But if you want a high quality print on good paper, that's another story.
The (Bosch) fuel pump on my old Saab was inside the gas tank. Gas ran through the motor to keep it cool. I suppose that since gas isn't conductive, a completely submersible fuel pump is even easier to make than a submersible water pump (as used in deep wells).
If the whole purpose of the backup system is to provide electrical power, then you'd think they'd consider the power
sources needed for it.
We generally assume that the purpose of a backup system is to actually operate when the main system fails.
Providing assurance that it will is an engineering job that requires enumerating the possible failure modes and
providing contingencies for them. The customer should presumably have that assessment done, then decide which
of the contingencies that they'll pay for (hopefully based on some cost/benefit/likelihood balancing strategy).
In this case, either they didn't do the right assessment, or else they didn't think this mode of failure was likely.
Either way, you hope they learn something.
If we can figure out how to put a pump into a well full of water deep underground, it should not be too difficult to figure out how to do something similar with a fuel pump, relatively speaking. To have not done so is a fail.
Yes; I said that more in jest than in seriousness. Really, we want party leaders who value their country more than their party.
Still would prefer a debate format where each candidate sits in a sound-proof booth, and the moderator controls the mute buttons on each.
Not sure about having electric shockers in each chair, though. Maybe that can wait until the next election.
We don't want a 3rd party so much as we'd just like to get rid of the two we have now and have a couple of choices that don't stink so much.
The issue comes into being most likely due to off-by-a-fraction errors when doing non-integer scaling of multiple elements.
One solution is just to get all your fractions right across the entire rendering pipeline. That is hard, and maybe impossible in some cases.
An easier solution is just to render to a canvas that is an integer multiple of the "base" or "expected" case, then finally apply a single scaling from that canvas to the display size at the last moment before the image is displayed.
For instance, let's say that software was developed for a 100 dpi display, and for a given device, that works out to a 1366x768 resolution (if its screen were 100 dpi). Now the screen is really 1920x1080, but that is not an integer multiple of 1366x768, so instead we render to a canvas that is 2x both dimensions: 2732x1536. The rendering here should be without any issues, since it's an integer multiple of 1366x768. From here, there are two paths to follow. If the display controller of the device can automatically scale 2732x1536 to 1920x1080, then let it do that. Otherwise, have the GPU scale the the canvas size to the display size, then display that. (Typically, the display controller can do a better job with multiple tap filters.)
Note that this requires extra rendering power and bandwidth vs. the first solution. However, that's what hardware is good at, right?
Note also that doing non-integer scaling will always result in what looks like "blurriness" around what would have otherwise been sharp pixel edges. This is not avoidable, really (unless you want really ugly results where some lines are fatter than others).
If not, they must not be Sirius.
Then would this be the relevant XKCD? http://xkcd.com/937/
Is this still SlashDot?
that you had to do this instead? Clearly, it must be something big.
And just how did you do it? Did you just use Gimp, find some nice images to threshold, cut and paste, or did you set up a custom pipeline?
(Note regarding tone of this message: please read with "awe", not "sarcasm".)
I, for one, hate mobile applications of websites. The regular website should just work well on any platform. That's the whole point of standard platforms.
Of course, I understand that I am free to ignore such apps. However, producing such an app should not be an excuse to not make the website work right.
(And I do understand that making a website "work right" across lots of browsers and platforms is hard. Consider it a challenge that only wimps decline.)
Only if they have all the latest features. You don't want to show up with last year's model, or you'll never hear the end of it.