Seems to me this makes it much easier to go after those who link to torrents, though I suppose the jury is still out on the legality of linking to copyrighted material.
Want to write a cool new widget for Tiger? Use JS.
Exactly. Apple hasn't made much noise in the public that widgets are simply HTML + CSS + JS and many of the Apple default widgets use XMLHttpRequest (which the AJAX folks also love) to do client side request without reloading.
In fact, Google's first hit for "xmlhttpquest" is this Apple page where its support in Safari 1.2 is touted for web developers:
For years, advanced client-side developers have frequently wanted a clean way to maintain a "connection" with the server so that transactions can occur in the background, and newly updated data gets inserted into the current page. Many have tortured themselves by using techniques such as hidden self-refreshing frames and "faceless" Java applets.
AJAX's promise and implementation may exist today in Google's tools, but the largest installed base of AJAX-like applications may turn out to be Apple widgets (hundreds are available for Dashboard now, though many sophisticated ones use Cocoa plugins or BSD system calls instead of XMLHttpRequest).
-- Shameless promotion: If you're a Mac user still on Panther 10.3.9, you can try out Dashboard widgets in Amnesty.
As usual per rumors of this type (although I suppose this source is somewhat more credible than Dvorak's wild guesses), people assume that such a move (Mac hardware based around x86) means that Apple would sell a standalone version of OS X that runs on any x86 hardware. My guess: not likely.
Apple would still be selling a closed-box solution and thus provide drivers for their platform only. OS X would still run on Macintoshes only, notwithstanding their x86 internals. A custom chipset similar to the old MacOS ROM could also help prevent tinkerers from trying to "extend" OS X to non-Apple machines. As others have mentioned, Apple doesn't want to get into the "support every x86 platform" game..."it just works" is still a motto for them.
Same problems here. The website was returning "errors" re: my battery serial number. So I called and spoke to a guy who sounded a bit confused -- he put me on hold and them came back with (honest truth) "Can you please call back at a later time? We're having some problems here." Went back to site and it was down. Now there only seems to be a Powerbook battery exchange in its place (I have the iBook battery). Oh well, maybe I'll try again tomorrow.
Users will now be prompted before a widget downloads to their hard drive.
Another problem, besides "auto-install on download" is that Dashboard's "warning" to a user on newly-installed widget launch is a simple yes/no proposition without any indication of the access sought by the widget.
It would be nice to see Apple adopt something similar to Amnesty Widget Browser, which presents the following dialog on newly-installed widget launch.
I was going through some code from 2002, frustrated at the lack of comments, cursing the moron who put this spaghetti together, only to realize later that I was the moron who had written it.
First, I just have to get this off my chest: I think this is pure B.S. Coding styles vary so much, that if you can't recognize your own code, then programming is something you barely have a hold on.
Now, as to answer: code should be readable, especially using mixed type names, a consistent naming style and comments for non-intuitive constructs. But -- and this is a big but:
If your code is meant to be shared with other programmers and you don't have a design document.....then you or your employer is an idiot, plain and simple.
If you have a project that needs support from more than one programmer (i.e. any commercial enterprise save DIY shops), then blaming "lack of comments" is just displacement. Blame the project manager instead.
I agree, but their desktop strategy is markedly different from their web application strategy, and it's not clear (to me at least) why Google wants Mac and Linux users (to wit: spending time and resources making sure GMail works in Mozilla, Firefox and Safari) on the web, but isn't interested in those very same users when it comes to desktop applications.
As an example: How much could it cost to port their video uploader to the Mac? Maybe $50,000 to one consultant...seems like a drop in the bucket to get video from 28 million Macintosh users (who, given iMovie is free, are arguably more likely to have video content in the first place).
Google provides an application (the Google Video Uploader) to upload video content to their servers. As expected, the program is Windows only. So, I guess Google wants your video, as long as you're not a Mac or Linux user.;-)
Interestingly, all of Google's desktop applications are all Windows only. Given their hiring blitz and their well-advertised work incentives, Google could easily find Mac and Linux programmers, so the lack of support for other platforms must be intended. Other companies can make the argument that the cost is too great, but Google can clearly afford it. So, what exactly is the strategy here?
Same here. On restart I went into some funky graphics mode (looked like a crash on an old C64) alternating between a light blue screen, a light green screen and some multicolored vertical lines. This is a brand new machines with XP Pro and basically only Visual Studio installed.
I almost had a heart attack because I didn't back up code I wrote last night (dumb to apply updates without backing up, yes I know).
A hard reboot fixed it for me, but I'm still a little nervous.
Copyright, no (unless it was a derivative, e.g. Photoshop copy of the X-Men "X", which it doesn't appear to be).
It could be a Trademark issue, but the markets don't overlap, and so there woudn't be a likelyhood of confusion. Notwithstanding the fact that it would be hard to protect a generic "X" (unlike say, Exxon's fanciful and very protectable double-x).
That was my initial impression as well, but that is clearly not the case. As the developer, Arben Kryesiu has been extremely vocal about his "creation" of CherryOS and has granted many interviews proudly describing his "inspiration" to write CherryOS -- hardly a "fly-by-night" developer who got caught up in a lie and skipped town after delivering a bogus product.
The "company" that owns CherryOS, Maui-X Stream, has the following in their bio:
Jim Kartes is the president of Maui-X Stream. He and Arben Kryesiu started the company in the winter of 2003.
So, this publicity hounding "developer" is a also co-founder of the company, and hence: the company is not an innocent player in all of this.
We secured distribution online originally by getting signed by Garageband, which I admit was a stroke of luck. Next, we partnered with CDBaby and used them to sell CDs directly to consumers (which became important after Garageband withered and released us from our contract). This (as others have mentioned) led us to getting listed on iTunes and dozens of other online music outfits. After that, playing out, swapping gigs, and making mini tours was a great way to get exposure. Getting signed allowed us to get written up in zines and even Billboard, so there is indeed something tangible about "getting signed." Your press kit is forever yours to build up and sell yourself, so make sure you get as much press as possible (even local press).
Now, to stroke the gods of honesty: "making it" takes luck, talent, luck, connections, luck and luck. Take every avenue afforded to you, even - to the chagrin of all Slashdotters -- signing with a minor or major. Get a good lawyer and you won't get suckered into signing all your rights (esp. to the sound recordings) away.
For those interested who have one ear bent in the late 90s era indie pop (e.g Pavement, Superchunk), you can check us out on iTunes.
Did you know Google Gulp sits in your stomach until 2038??? Nobody has bothered to challenge them on this. There is also evidence that it will burn a unique number on your hard stools during this time. Fact: every flush will go through Google's sewage processing and they'll be able to track everything you eat.
And next year, don't buy the Google Fedora(TM). It's spyware.
This article from the Washington Post follows-up the story in Wired. In short (and I suppose unsuprisingly), college isn't an option due to their illegal status (no loans, no in-state tuition). Of the two who have graduated high school: One of them is hanging drywall, and the other files papers at a Social Secuirty office.
Google has never advertised openings for Mac OS X developers. Their Engineering listings contain specific openings for Windows and Senior Windows Developers.
Interestingly, for a company willing to advertise an "homage" to OS X, they don't seem to be in a hurry to hire developers for any Mac OS X hosted client-side solutions (Google Toolbar, Desktop Search).
The explanation for this behavior: when the Macintosh was developed, it had no hard drive, so if you wanted to copy a file from one floppy to another, there had to be some notion of "half-mounted" disks to drag-and-drop files to/from.
And given that the boot disk contained the operating system, truly "ejecting" it was impossible.
Thus, "Eject" meant "remove this disk so I can put another disk in" and "Put Away" meant "I'm done with this disk now, so I want to be able to put it away."
Slashdot Mirror
Will he get sued?
Someone will.
Seems to me this makes it much easier to go after those who link to torrents, though I suppose the jury is still out on the legality of linking to copyrighted material.
NBC: The Complete 1994 Prime Time Season.
In two colors: black ($1.29) and white ($1.99).
Exactly. Apple hasn't made much noise in the public that widgets are simply HTML + CSS + JS and many of the Apple default widgets use XMLHttpRequest (which the AJAX folks also love) to do client side request without reloading.
In fact, Google's first hit for "xmlhttpquest" is this Apple page where its support in Safari 1.2 is touted for web developers:
AJAX's promise and implementation may exist today in Google's tools, but the largest installed base of AJAX-like applications may turn out to be Apple widgets (hundreds are available for Dashboard now, though many sophisticated ones use Cocoa plugins or BSD system calls instead of XMLHttpRequest).
--
Shameless promotion: If you're a Mac user still on Panther 10.3.9, you can try out Dashboard widgets in Amnesty.
As usual per rumors of this type (although I suppose this source is somewhat more credible than Dvorak's wild guesses), people assume that such a move (Mac hardware based around x86) means that Apple would sell a standalone version of OS X that runs on any x86 hardware. My guess: not likely.
Apple would still be selling a closed-box solution and thus provide drivers for their platform only. OS X would still run on Macintoshes only, notwithstanding their x86 internals. A custom chipset similar to the old MacOS ROM could also help prevent tinkerers from trying to "extend" OS X to non-Apple machines. As others have mentioned, Apple doesn't want to get into the "support every x86 platform" game..."it just works" is still a motto for them.
Same problems here. The website was returning "errors" re: my battery serial number. So I called and spoke to a guy who sounded a bit confused -- he put me on hold and them came back with (honest truth) "Can you please call back at a later time? We're having some problems here." Went back to site and it was down. Now there only seems to be a Powerbook battery exchange in its place (I have the iBook battery). Oh well, maybe I'll try again tomorrow.
Users will now be prompted before a widget downloads to their hard drive.
Another problem, besides "auto-install on download" is that Dashboard's "warning" to a user on newly-installed widget launch is a simple yes/no proposition without any indication of the access sought by the widget.
It would be nice to see Apple adopt something similar to Amnesty Widget Browser, which presents the following dialog on newly-installed widget launch.
CNN is running an article featuring Gates' prediction that the iPod is on the way out.
Bill has really got to learn the difference between prediction and predilection.
I was going through some code from 2002, frustrated at the lack of comments, cursing the moron who put this spaghetti together, only to realize later that I was the moron who had written it.
..then you or your employer is an idiot, plain and simple.
First, I just have to get this off my chest: I think this is pure B.S. Coding styles vary so much, that if you can't recognize your own code, then programming is something you barely have a hold on.
Now, as to answer: code should be readable, especially using mixed type names, a consistent naming style and comments for non-intuitive constructs. But -- and this is a big but:
If your code is meant to be shared with other programmers and you don't have a design document...
If you have a project that needs support from more than one programmer (i.e. any commercial enterprise save DIY shops), then blaming "lack of comments" is just displacement. Blame the project manager instead.
I agree, but their desktop strategy is markedly different from their web application strategy, and it's not clear (to me at least) why Google wants Mac and Linux users (to wit: spending time and resources making sure GMail works in Mozilla, Firefox and Safari) on the web, but isn't interested in those very same users when it comes to desktop applications.
As an example: How much could it cost to port their video uploader to the Mac? Maybe $50,000 to one consultant...seems like a drop in the bucket to get video from 28 million Macintosh users (who, given iMovie is free, are arguably more likely to have video content in the first place).
Google provides an application (the Google Video Uploader) to upload video content to their servers. As expected, the program is Windows only. So, I guess Google wants your video, as long as you're not a Mac or Linux user. ;-)
Interestingly, all of Google's desktop applications are all Windows only. Given their hiring blitz and their well-advertised work incentives, Google could easily find Mac and Linux programmers, so the lack of support for other platforms must be intended. Other companies can make the argument that the cost is too great, but Google can clearly afford it. So, what exactly is the strategy here?
Same here. On restart I went into some funky graphics mode (looked like a crash on an old C64) alternating between a light blue screen, a light green screen and some multicolored vertical lines. This is a brand new machines with XP Pro and basically only Visual Studio installed.
I almost had a heart attack because I didn't back up code I wrote last night (dumb to apply updates without backing up, yes I know).
A hard reboot fixed it for me, but I'm still a little nervous.
Copyright, no (unless it was a derivative, e.g. Photoshop copy of the X-Men "X", which it doesn't appear to be).
It could be a Trademark issue, but the markets don't overlap, and so there woudn't be a likelyhood of confusion. Notwithstanding the fact that it would be hard to protect a generic "X" (unlike say, Exxon's fanciful and very protectable double-x).
That was my initial impression as well, but that is clearly not the case. As the developer, Arben Kryesiu has been extremely vocal about his "creation" of CherryOS and has granted many interviews proudly describing his "inspiration" to write CherryOS -- hardly a "fly-by-night" developer who got caught up in a lie and skipped town after delivering a bogus product.
The "company" that owns CherryOS, Maui-X Stream, has the following in their bio:
Jim Kartes is the president of Maui-X Stream. He and Arben Kryesiu started the company in the winter of 2003.
So, this publicity hounding "developer" is a also co-founder of the company, and hence: the company is not an innocent player in all of this.
Fixed CDBaby link is here. Sorry 'bout that!
We secured distribution online originally by getting signed by Garageband, which I admit was a stroke of luck. Next, we partnered with CDBaby and used them to sell CDs directly to consumers (which became important after Garageband withered and released us from our contract). This (as others have mentioned) led us to getting listed on iTunes and dozens of other online music outfits. After that, playing out, swapping gigs, and making mini tours was a great way to get exposure. Getting signed allowed us to get written up in zines and even Billboard, so there is indeed something tangible about "getting signed." Your press kit is forever yours to build up and sell yourself, so make sure you get as much press as possible (even local press).
Now, to stroke the gods of honesty: "making it" takes luck, talent, luck, connections, luck and luck. Take every avenue afforded to you, even - to the chagrin of all Slashdotters -- signing with a minor or major. Get a good lawyer and you won't get suckered into signing all your rights (esp. to the sound recordings) away.
For those interested who have one ear bent in the late 90s era indie pop (e.g Pavement, Superchunk), you can check us out on iTunes.
And most importantly: good luck!
Oh, mass. My bad.
Since I already own the way superior LaserDisc edition, why should I care?
P.S. Does anyone know if there's a tube amp powered MP3 player? I want some way of adding back the "warmth" to my ripped ELO LPs. TIA.
Did you know Google Gulp sits in your stomach until 2038??? Nobody has bothered to challenge them on this. There is also evidence that it will burn a unique number on your hard stools during this time. Fact: every flush will go through Google's sewage processing and they'll be able to track everything you eat.
And next year, don't buy the Google Fedora(TM). It's spyware.
Sincerely,
Google-Gulp-Watch.org
This article from the Washington Post follows-up the story in Wired. In short (and I suppose unsuprisingly), college isn't an option due to their illegal status (no loans, no in-state tuition). Of the two who have graduated high school: One of them is hanging drywall, and the other files papers at a Social Secuirty office.
For OOPing, silly.
What's sad here is, he likely got pressured into giving up a copy or two to some friends, who probably SWORE they wouldn't share it.
;-)
Since one his friends is named "BitTorrent" he should've known that friend was going to share it.
Looks like one of those newfangled 'words in the dictionary' that arent suppose to be trademark-able to me. Whats wrong with the world.
What's wrong is that you think "newfangled 'words in the dictionary'...arent suppose to be trademark-able".
Go to the store. Do you see:
- Tide
- Scope
- Crest
Good. Now open your dictionary.
Any word makes a fine trademark as long as its not generic in its market. The "dictionary test" is a myth.
Google has never advertised openings for Mac OS X developers. Their Engineering listings contain specific openings for Windows and Senior Windows Developers.
Interestingly, for a company willing to advertise an "homage" to OS X, they don't seem to be in a hurry to hire developers for any Mac OS X hosted client-side solutions (Google Toolbar, Desktop Search).
The explanation for this behavior: when the Macintosh was developed, it had no hard drive, so if you wanted to copy a file from one floppy to another, there had to be some notion of "half-mounted" disks to drag-and-drop files to/from.
And given that the boot disk contained the operating system, truly "ejecting" it was impossible.
Thus, "Eject" meant "remove this disk so I can put another disk in" and "Put Away" meant "I'm done with this disk now, so I want to be able to put it away."