I've got a wireless mighty mouse that doesn't recognise right-clicks, and a wired mighty mouse that works perfectly. I'm not sure whether there's a design problem with the wireless version, or whether quality control is poor. Maybe the gp poster has a bad one.
Please go back and read what you wrote: "...For All *DEBTS*...". That quote is only relevant when paying off a debt, such as rent paid in arrears. The important detail is that you're free not to do business with Apple if you don't agree with their payment policy. If you bought on credit and then had cash payment rejected, at that point your legal tender argument would make sense.
Sure, if the beta particles were captured and used as the current output of the battery, your calculations would be reasonable. If the beta particle has plenty of energy though, wouldn't it be able to dislodge more than one electron in whatever medium captured it? What's the mean free path through silicon of a beta particle somewhere in the middle of the energy spectrum for Radium's emissions?
It might only take one hundredth of Hanford's waste...
It's being released in the US first, where I understand there's sod all 3G coverage. By the time it reaches more technologically-advanced countries maybe it will get 3G. Wait and see. I'm still not sure there would be any point to that though; My provider thinks that £5/month for 120Mb of data is a good deal, so non-voice services are going to end up pretty expensive. WiFi is the way to go.
John Siracusa has already written a great article on Time Machine over at Ars Technica. ZFS would have allowed Time Machine to back up only changed blocks in files, but apparently the current implementation has to copy whole files around.
Two companies that are infinitely more qualified come to mind immediately- Bosch and MOTEC (Magneti Marelli is a little too tied to Ferrari, I think.) 3/4 of the world's auto racing engineers cut their teeth and/or use MOTEC ECUs.
More qualified still are the two companies (alongside Magnetti Marelli) which actually _do_ make ECUs for Formula 1 - TAG and Pi Research. (Bosch and Motec electronics get used in other formulae.) I'd add that Honda and Williams make their own ECUs. I've been out of the game for a few years now, though, so I'm not sure whether any other teams have started doing so.
Microsoft would have an awful lot of ground to make up if they really are planning to provide manufacture ECUs. I expect that the story is wrong, and that Microsoft are branding somebody else's product. Or, they are buying an existing company.
Bonjour is the new name for Rendezvous. It isn't an application like Fire or iChat, it is a mechanism for programmes to find each other over a network. If you're using iChat, you're using a programme that includes Bonjour; It is how iChat finds other iChat users on the local network.
"October 29, 2004: OpenOffice.org 2.0 Aqua port slows. With lack of a dedicated X11 team, 2.0 doesn't even compile "out of the box" for X11, and Cocoa development has slowed as well. The only current Mac OS X non-X11 development is the NeoOffice/J [neooffice.org] fork of OpenOffice.org 1.1.2, which is all the time I (Ed) have for myself. We desperately need your help! Go checkout 680 and help Eric Bachard, Eric H., and all the other Mac OS X diehards port it today! Check out the mailing list archives for the most recent 411."
OpenOffice 1.x on X11 is nice enough, although I had trouble when trying to run it on user accounts other than my main one. NeoOffice/J is good, if slow to start. However, the OpenOffice Cocoa port is vapourware, so best not to get your hopes up just yet.
Don't be so sure. There was a nice demo on television a year or so back ("Top Gear" here in the UK) that Gatso cameras are good to about 170ish mph and no more. At that speed the camera didn't even trigger.
Wrong, at least on your first point. launchd is APSL-licensed open source. Oh, and these chaps seem quite happy with the APSL, so it'd be churlish to begrudge Apple that choice of license.
From an educational perspective, I'd be interested to know which Unix design ethics it violates, though.
64-bit UI.... because that'll give you really high-res mouse pointer coordinates? Because you'll be able to have 2^64 menu items? Maybe so that each pixel can be 64-bit?
If you're writing an app that requires / would benefit from 64 bit arithmetic or memory addressing, writing the GUI and the business logic in the same executable is going to be dumb. If you're writing a text editor, who needs a 64 bit app?
Sure, in an ideal world one would have the freedom to write a 64 bit monolithic app, even if it did stink. In reality, having to write a separate UI layer and business engine isn't going to be a problem.
Say, have "Microsoft got the 64-bit answer right" yet? I seem to remember them taking ages over deciding whether to support AMD/IA64 at all or just Itanic, and hadn't released a final version of the OS. Maybe they've shipped Windows for 64-bit at last.
Hmm. On the few occasions when I'm listening to an album properly, the (very short) gaps are annoying. However, gapless playback doesn't make any sense at all when shuffling songs, which is what I do almost all the time.
Microsoft has a pretty firm grip on the operating system market. It uses that grip to co-opt other markets, such as that for web browsers and media players. I understand that this is referred to as "an abuse of monopoly powers."
Apple has a monopoly on squat. True, it has a pretty big share of the music download business, and an extremely nice portion of the portable music player market. There is still some life left in those areas for other companies, though, and it's hard to see what vaguely-related business they could stomp on with their new-found musical might.
DRM still sucks though, no matter what the source. I'd still trust Apple more not to shaft us that MS, though.
He's referring to the "Reverse Takeover" theory. Apple provided the money, but NeXT provided the (originally, acting) CEO and the technology. It's a slightly lame insult to use against Apple, but since they've ended up as a stronger company I'm sure they don't mind.
Not quite true. The chipset supports WMA decoding, but Apple would have had to write some user interface (plus maybe some other interfacing code) to enable it, which they didn't bother to do. Omission is a whole different ball game from restriction.
I would disagree with one of your points. Software development isn't, despite the best efforts of some people, and should never be, an engineering discipline. Coding is a creative discipline closer to the "mystic gestalt of painting" than the design of gears.
Copyright could be the way to protect software, but the definition of "derivative works" needs to be tightened up considerably. In a book, sentences are the basic creative unit, and copied sentences may be easy to spot. In software, the basic creative unit is much harder to pick out. (Is it a function? Maybe a module?) SCO are trying to manipulate the difficulty in working out which parts of a software work are derivative by pointing to similar lines of code, which is like being unable to see the wood for the trees.
Slashdot Mirror
I've got a wireless mighty mouse that doesn't recognise right-clicks, and a wired mighty mouse that works perfectly. I'm not sure whether there's a design problem with the wireless version, or whether quality control is poor. Maybe the gp poster has a bad one.
Please go back and read what you wrote: "...For All *DEBTS*...". That quote is only relevant when paying off a debt, such as rent paid in arrears. The important detail is that you're free not to do business with Apple if you don't agree with their payment policy. If you bought on credit and then had cash payment rejected, at that point your legal tender argument would make sense.
HTH
Sure, if the beta particles were captured and used as the current output of the battery, your calculations would be reasonable. If the beta particle has plenty of energy though, wouldn't it be able to dislodge more than one electron in whatever medium captured it? What's the mean free path through silicon of a beta particle somewhere in the middle of the energy spectrum for Radium's emissions?
It might only take one hundredth of Hanford's waste...
It's being released in the US first, where I understand there's sod all 3G coverage. By the time it reaches more technologically-advanced countries maybe it will get 3G. Wait and see. I'm still not sure there would be any point to that though; My provider thinks that £5/month for 120Mb of data is a good deal, so non-voice services are going to end up pretty expensive. WiFi is the way to go.
And as for video calls, ugh....
John Siracusa has already written a great article on Time Machine over at Ars Technica. ZFS would have allowed Time Machine to back up only changed blocks in files, but apparently the current implementation has to copy whole files around.
5 /4995
http://arstechnica.com/staff/fatbits.ars/2006/8/1
More qualified still are the two companies (alongside Magnetti Marelli) which actually _do_ make ECUs for Formula 1 - TAG and Pi Research. (Bosch and Motec electronics get used in other formulae.) I'd add that Honda and Williams make their own ECUs. I've been out of the game for a few years now, though, so I'm not sure whether any other teams have started doing so.
Microsoft would have an awful lot of ground to make up if they really are planning to provide manufacture ECUs. I expect that the story is wrong, and that Microsoft are branding somebody else's product. Or, they are buying an existing company.
Bonjour is the new name for Rendezvous. It isn't an application like Fire or iChat, it is a mechanism for programmes to find each other over a network. If you're using iChat, you're using a programme that includes Bonjour; It is how iChat finds other iChat users on the local network.
From OpenOffice.org:
"October 29, 2004: OpenOffice.org 2.0 Aqua port slows. With lack of a dedicated X11 team, 2.0 doesn't even compile "out of the box" for X11, and Cocoa development has slowed as well. The only current Mac OS X non-X11 development is the NeoOffice/J [neooffice.org] fork of OpenOffice.org 1.1.2, which is all the time I (Ed) have for myself. We desperately need your help! Go checkout 680 and help Eric Bachard, Eric H., and all the other Mac OS X diehards port it today! Check out the mailing list archives for the most recent 411."
OpenOffice 1.x on X11 is nice enough, although I had trouble when trying to run it on user accounts other than my main one. NeoOffice/J is good, if slow to start. However, the OpenOffice Cocoa port is vapourware, so best not to get your hopes up just yet.
Don't be so sure. There was a nice demo on television a year or so back ("Top Gear" here in the UK) that Gatso cameras are good to about 170ish mph and no more. At that speed the camera didn't even trigger.
Did he order it from Apple? If so, they've usually given upgrades or refunds when changing specs or prices.
Wrong, at least on your first point. launchd is APSL-licensed open source. Oh, and these chaps seem quite happy with the APSL, so it'd be churlish to begrudge Apple that choice of license.
From an educational perspective, I'd be interested to know which Unix design ethics it violates, though.
64-bit UI.... because that'll give you really high-res mouse pointer coordinates? Because you'll be able to have 2^64 menu items? Maybe so that each pixel can be 64-bit?
If you're writing an app that requires / would benefit from 64 bit arithmetic or memory addressing, writing the GUI and the business logic in the same executable is going to be dumb. If you're writing a text editor, who needs a 64 bit app?
Sure, in an ideal world one would have the freedom to write a 64 bit monolithic app, even if it did stink. In reality, having to write a separate UI layer and business engine isn't going to be a problem.
Say, have "Microsoft got the 64-bit answer right" yet? I seem to remember them taking ages over deciding whether to support AMD/IA64 at all or just Itanic, and hadn't released a final version of the OS. Maybe they've shipped Windows for 64-bit at last.
Mine was shipped on 28th and arrived half an hour ago. Woo hoo!
Apple's tracking page seems to have been down all day, which is painful if you're expecting a delivery.
I know it's not so convenient as having digital out built in, but look at this:
e /index.php
http://www.griffintechnology.com/products/firewav
I'm happy that Apple have left the choice of whether to spend on digital audio out up to the buyer, rather than ramp the price of the mini.
OTOH, get the thing configured with built-in bluetooth and, with a BT headset you're away. How cool would that be?
Hmm. On the few occasions when I'm listening to an album properly, the (very short) gaps are annoying. However, gapless playback doesn't make any sense at all when shuffling songs, which is what I do almost all the time.
Ah, the "Home on iPod" feature that disappeared from the Panther release. I'm rather hoping that it'll reappear in Tiger.
Microsoft has a pretty firm grip on the operating system market. It uses that grip to co-opt other markets, such as that for web browsers and media players. I understand that this is referred to as "an abuse of monopoly powers."
Apple has a monopoly on squat. True, it has a pretty big share of the music download business, and an extremely nice portion of the portable music player market. There is still some life left in those areas for other companies, though, and it's hard to see what vaguely-related business they could stomp on with their new-found musical might.
DRM still sucks though, no matter what the source. I'd still trust Apple more not to shaft us that MS, though.
Most likely, using one or the other of these. I don't think they'll be worrying about being left behind just yet.
He's referring to the "Reverse Takeover" theory. Apple provided the money, but NeXT provided the (originally, acting) CEO and the technology. It's a slightly lame insult to use against Apple, but since they've ended up as a stronger company I'm sure they don't mind.
Not quite true. The chipset supports WMA decoding, but Apple would have had to write some user interface (plus maybe some other interfacing code) to enable it, which they didn't bother to do. Omission is a whole different ball game from restriction.
I'm guessing it's in Windows Services for Unix, but could be wrong.
Thank you :)
Ah, I'd managed to convince myself it was an urban myth.
> Hell, a handful of coins would kill people from a few thounsand feet up.
Oh yeah? What's the terminal velocity of a coin?
I would disagree with one of your points. Software development isn't, despite the best efforts of some people, and should never be, an engineering discipline. Coding is a creative discipline closer to the "mystic gestalt of painting" than the design of gears.
Copyright could be the way to protect software, but the definition of "derivative works" needs to be tightened up considerably. In a book, sentences are the basic creative unit, and copied sentences may be easy to spot. In software, the basic creative unit is much harder to pick out. (Is it a function? Maybe a module?) SCO are trying to manipulate the difficulty in working out which parts of a software work are derivative by pointing to similar lines of code, which is like being unable to see the wood for the trees.