I have an 8 year old mid-range MacBook Pro (pre-unibody) that I upgraded to 4GB ram, a 120GB SSD, removed the optical drive & replaced with the original 5400 spinning platter and set up the SSD+HD as a "fusion" drive and the GeekBench scores are barely below the low-end 2016 MacBook. I was only able to do this because it's from before Apple's anorexia infected their laptops. Still a great machine aside from having to bake the logic board every month or so because of the bad solder on the graphics chip (which didn't start failing until just after apple ended their extended replacement for it). Apple doesn't make computers anymore, they make sealed-off, anorexic "devices"
OS X is an evolution of NEXTSTEP, which was started in the late 80s. They saw that OS 9 was a dead end and Apple needed something "new" and "modern", so they went with NEXT (and for a good while there was this set of compatibility APIs called carbon, PROBABLY had a lot of mac classic code). You can still see a lot of similarities between Xcode today and what they were using on NEXT in the early 90s. new code, old code, it makes no difference. It ALL has flaws.
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
Actually, there is no limit. If your site sees a ton of pageviews, they ask that you check w/ them before adding Maps to your site, so they can make sure they have the capacity to support it... c'mon, it's a free service, the least you can do is ask 'em if htey can handle your 200k pageviews/day:P
"My primary problem with Google Maps, though, is that they do have a limit on how many maps you can serve in a specific time period before they cut you off. It's great if you have a low-traffic page, but if you get slashdotted or just start getting popular, your maps *could* disappear. I say "could" because I don't know if Google Maps is enforcing the limit, but they do state it exists. So even if they're not enforcing it, they could do so whenever they choose."
the flash tour says that "trusted sites" will be rendered using the IE method "for better compatability". so the rumors were right:-\
A million web developers just cried out in horror
on
Netscape 8.0 Released
·
· Score: 5, Insightful
From the flash tour: "If a site is considered trustworthy, Netscape automatically renders it using the Internet Explorer method, for maximum compatability."
So do you think Apple should stop updating it's core APIs and making stuff better/easier to use for it's developers, or just start back-porting all new stuff to old OSes just so that mr I installed 10.1 and think it rocks can quit bitching about not being able to use Safari? Apple is already slowing down their releases. Tiger is taking about 18 months where Panther was what? 12?
Best guess is that it will be "backported" to Panther in the form of Safari 1.3 (which they had several developer previews of months back), and will have all the stuff Safari 2.0 does, minus the RSS support. The 1.3 previews were pretty much in-line w/ what Safari 2 had at the time, so I assume they've kept it up to date internally.
it's called a JOKE... you know, HUMOR... forget it. Some people can rant and spout off 60 equations from memory but a pathetically simple joke manages to elude them.
BTW, this is slashdot... being serious here is against the rules.
Slashdot Mirror
I have an 8 year old mid-range MacBook Pro (pre-unibody) that I upgraded to 4GB ram, a 120GB SSD, removed the optical drive & replaced with the original 5400 spinning platter and set up the SSD+HD as a "fusion" drive and the GeekBench scores are barely below the low-end 2016 MacBook. I was only able to do this because it's from before Apple's anorexia infected their laptops. Still a great machine aside from having to bake the logic board every month or so because of the bad solder on the graphics chip (which didn't start failing until just after apple ended their extended replacement for it). Apple doesn't make computers anymore, they make sealed-off, anorexic "devices"
OS X is an evolution of NEXTSTEP, which was started in the late 80s. They saw that OS 9 was a dead end and Apple needed something "new" and "modern", so they went with NEXT (and for a good while there was this set of compatibility APIs called carbon, PROBABLY had a lot of mac classic code). You can still see a lot of similarities between Xcode today and what they were using on NEXT in the early 90s.
new code, old code, it makes no difference. It ALL has flaws.
http://en.wikipedia.org/wiki/Replicator_(Stargate)
The plans are to have Rails 2.1 ruby 1.9 compatible.
That is incorrect. The Signal vs Noise weblog (by the guys behind Rails) is PHP-based, the Ruby on Rails website is not.
Underwater pool? I think you mean cement pond?
Actually, there is no limit. If your site sees a ton of pageviews, they ask that you check w/ them before adding Maps to your site, so they can make sure they have the capacity to support it... c'mon, it's a free service, the least you can do is ask 'em if htey can handle your 200k pageviews/day :P
"My primary problem with Google Maps, though, is that they do have a limit on how many maps you can serve in a specific time period before they cut you off. It's great if you have a low-traffic page, but if you get slashdotted or just start getting popular, your maps *could* disappear. I say "could" because I don't know if Google Maps is enforcing the limit, but they do state it exists. So even if they're not enforcing it, they could do so whenever they choose."
did you REPORT IT? if you do report it, something more than "that iPhoto bug" would be helpful too.
RTFP. he said it WASN'T very cool.
the flash tour says that "trusted sites" will be rendered using the IE method "for better compatability". so the rumors were right :-\
From the flash tour:
"If a site is considered trustworthy, Netscape automatically renders it using the Internet Explorer method, for maximum compatability."
WHY?!
FLAMEBAIT? heh, we'll see...
A/V software w/ major security holes...
So do you think Apple should stop updating it's core APIs and making stuff better/easier to use for it's developers, or just start back-porting all new stuff to old OSes just so that mr I installed 10.1 and think it rocks can quit bitching about not being able to use Safari?
Apple is already slowing down their releases. Tiger is taking about 18 months where Panther was what? 12?
Best guess is that it will be "backported" to Panther in the form of Safari 1.3 (which they had several developer previews of months back), and will have all the stuff Safari 2.0 does, minus the RSS support. The 1.3 previews were pretty much in-line w/ what Safari 2 had at the time, so I assume they've kept it up to date internally.
There's a difference, w/ VS, there's still the possibility of getting work done... That chance isn't there using FrontPage ;)
Web developer.
it's called a JOKE... you know, HUMOR... forget it. Some people can rant and spout off 60 equations from memory but a pathetically simple joke manages to elude them.
BTW, this is slashdot... being serious here is against the rules.
next time, finish reading TFA. He said it quit working in QT, but worked in iTunes, then later it worked in QT again.
next time RTFA /.
oh, right... this is
I want the IM wars back... MSN Messenger 1.0 released w/ AIM support... AOL updates AIM protocol... MSNM releases patch to fix aim, AOL updates again, MSNM patched again, lather, rinse, repeat... (around '99,2000 if I rmemeber right)
yep, and there'll be a command key on the steering clickwheel you hold in to brake
which of course is million million
don't you mean V'ger? =)
You probably should have finished reading that post before adding your witty comment ;)