The flash in the hybrid drives won't be used as that kind of cache (you're thinking of the Vista's ReadyBoost).
This flash will be a write cache for the hard drive so that the hard drive doesn't need to spin up as often (this will potentially enhance your battery life). As you make changes to your data, it will be written to the cache and then flushed to the drive (a) when the cache is full or (b) when the drive is spun up for some other reason (a read, for example). Presumably, if the drive is already spun up, the flash won't be used at all and data will go straight to the disk.
We can make a computer that fits in an oversized watch, but you wouldn't want to use it, either.
If I could easily drop in in a docking station with a real keyboard and monitor, I would love to have a computer in a wristwatch even if it was difficult to use without the docking station. I would always have a real docking station if I were doing real work, but a small screen with stylus interface would be fine for the times when I absolutely needed to look something up.
My primary development machine is a laptop, but I usually use it while docked (real keyboard and larger monitor attached).
I don't see why the flipstart machine couldn't be used the same way. It's not like processing power is the bottleneck for most coding excercises (ignoring compile time).
Fortunately, the appearance is the easiest thing to change. You can put a different interface in front of the user with each iteration without having to make any changes to the backend. Of course, by doing that, you keep the user from gaining as much familiarity with the app as development progresses (which usually hurts their ability to give meaningful feedback).
Don't send them the documentation, send them an application that they can play with. Then, based on their feedback, write you're own detailed specs and update the application accordingly. As time goes on, your application will begin to have all the fleshed out features that the user needs, and, since the user was involved from the beginning, they'll be familiar with how the app fits into their work flow (this should keep them from asking for radical or contradictory changes with each iteration).
Get the user involved as early as possible. Writing software can be fun, but if the product isn't something the user can/will use, then you've wasted you company's money.
Actually, even if this bill fails, the simple fact that it's been proposed makes it far more likely that similar bills will be proposed in other places. If it's well written, then it can act as a template for other proposals. Heck, the discussion it's already caused is valuable.
If it's a good idea, eventually it will get traction.
This is purely speculation, but it seems likely to me that the contracts that allow Apple to sell the Labels' music also require that Apple not sell any DRM-less tracks from anyone.
Until said contracts become public (don't hold your breath), we'll never know.
The company could keep their own patch set with DRM added and use it internally if that's what they want. But they could not force the kernel maintainer to include their patches in the vanilla kernel. That said, there's no reason that the maintainer couldn't accept the patches and make their inclusion a kernel config option.
Actually, if the patches are well written, that's what I'd expect to have happen.
You say this as if it's possible to have a system where the majority of the population isn't poor. As long as there is scarcity, the majority of people will be poor. There's no way around it that I'm aware of.
I can't comment on how mature Ruby is, but I do remember it having some of the same Perl-like attributes that made me search for a Perl replacement in the first place.
The flash in the hybrid drives won't be used as that kind of cache (you're thinking of the Vista's ReadyBoost).
This flash will be a write cache for the hard drive so that the hard drive doesn't need to spin up as often (this will potentially enhance your battery life). As you make changes to your data, it will be written to the cache and then flushed to the drive (a) when the cache is full or (b) when the drive is spun up for some other reason (a read, for example). Presumably, if the drive is already spun up, the flash won't be used at all and data will go straight to the disk.
We can make a computer that fits in an oversized watch, but you wouldn't want to use it, either.
If I could easily drop in in a docking station with a real keyboard and monitor, I would love to have
a computer in a wristwatch even if it was difficult to use without the docking station. I would always
have a real docking station if I were doing real work, but a small screen with stylus interface would
be fine for the times when I absolutely needed to look something up.
My primary development machine is a laptop, but I usually use it while docked (real keyboard and larger monitor attached).
I don't see why the flipstart machine couldn't be used the same way. It's not like processing power is the bottleneck for most coding excercises (ignoring compile time).
Fortunately, the appearance is the easiest thing to change. You can put a different interface in front of the user with each iteration without having to make any changes to the backend. Of course, by doing that, you keep the user from gaining as much familiarity with the app as development progresses (which usually hurts their ability to give meaningful feedback).
Don't send them the documentation, send them an application that they can play with. Then, based on their feedback, write you're own detailed specs and update the application accordingly. As time goes on, your application will begin to have all the fleshed out features that the user needs, and, since the user was involved from the beginning, they'll be familiar with how the app fits into their work flow (this should keep them from asking for radical or contradictory changes with each iteration).
Get the user involved as early as possible. Writing software can be fun, but if the product isn't something the user can/will use, then you've wasted you company's money.
Also, they can't force users to upgrade to new versions of Office just to be able to open new Office files.
Actually, even if this bill fails, the simple fact that it's been proposed makes it far more likely that similar bills will be proposed in other places. If it's well written, then it can act as a template for other proposals. Heck, the discussion it's already caused is valuable.
If it's a good idea, eventually it will get traction.
What Office features aren't supported by ODF?
Is there a list somewhere or are these just vacuous claims?
The MacBook Pro seems to be getting traction in our senior management and anyone who does web design.
Maybe us developers will get them when the next round of purchasing starts.
from future import division
would fix this for you if it really bothers you.
Actually, lots of people have abandoned PHP for Python and Ruby.
It may never completely go away, but there are alternatives to using it.
This is purely speculation, but it seems likely to me that the contracts that allow
Apple to sell the Labels' music also require that Apple not sell any DRM-less tracks
from anyone.
Until said contracts become public (don't hold your breath), we'll never know.
The company could keep their own patch set with DRM added and use it internally if that's what they want. But they could not force the kernel maintainer to include their patches in the vanilla kernel. That said, there's no reason that the maintainer couldn't accept the patches and make their inclusion a kernel config option.
Actually, if the patches are well written, that's what I'd expect to have happen.
Microsofts format fails the 4th criterion:
(4) Controlled by an open industry organization with a well-defined inclusive process for evolution of the standard.
Some time ago I needed to buy a new hard drive and I found the best deal at Office Max ($99 for 200G).
In fact, I've found Office Max and Office Depot to be pretty competitive (at least for non-cable hardware)
with BestBuy and the rest.
Out of curiosity, when does this patent expire?
Ogg makes me happy since it's better quality for similar file size as mp3.
If I have to pay for it, make it lossless like flac.
You've got it backwards. Capitalism is a method of handling scarcity.
If there was no scarcity, there would be no need for any sort of economic system.
The state keeps the people poor
You say this as if it's possible to have a system where the majority of the population isn't poor. As long
as there is scarcity, the majority of people will be poor. There's no way around it that I'm aware of.
No, profits are what you have left over after paying expenses like salaries.
Arguably, bonuses can be paid out of profits (depending on how things are accounted for).
Potentially stupid question: is OGG commonly supported by players?
I don't remember seeing OGG listed on any packaging this Chrismas...
So if you write to every single block once a second continuously for 14 months, you'd start to see failures.
I wouldn't worry about it if I were you.
I can't comment on how mature Ruby is, but I do remember it having some of the same Perl-like attributes that made me search for a Perl replacement in the first place.
Is there some reason why you can't patent methods required in a standard?
What about on-line merchants? How are they supposed to compare your signature or view you ID?
Seriously, what protections do they have?