i'm kind of bummed that they didn't mention Locomotive, which really makes getting started with Rails very very easy. it seems like every Rails tutorial starts with "OK compile Ruby, install Gems, install Rails, install and configure MySQL, and 10 hours later, you can use this really simple framework!" when with Locomotive and SQLite3, you can basically just download one app, click two buttons, and start typing.
It takes a real genious to recognize that there is more than one time direction, and that it is "truly true" and not just mathematical sophistry or convenience. But the name of that genious is Albert Einstein, not Alex Mayer.
That's an interesting theorem. May I suggest another... One may not become an arbiter of genius until one learns to spell 'genius.'
this is totally inaccurate... you know you can inline assembly and plain C code in Objective-C, right? likewise, Finder, a Carbon app, has been building on Intel as part of the Marklar project for some time..
You are able to add a FW800 card to any PC via a PCI card, therefore is shouldn't take too much to include it in a laptop, if it was really all that important right now.
we're talking integrating it into a laptop... that would require Intel to redesign a chipset, unless they want to make a 1-off motherboard for just Apple (probably not).
They could've added their own chip, driving up costs, weight and heat, while decreasing battery lifetime.
not sure they could... that's an Intel motherboard. Apple's not making them anymore. what they could do is exert pressure on Intel to include support for fw800 in the future.
Re:May I please have more cooling rather than less
on
New iMac disassembled
·
· Score: 1
Uh, I wouldn't call EFI a big difference, it will be likely worked around pretty quickly. The Intel chipset support is all in there, even for P4 systems. A bigger issue is the TPM.
the point i'm trying to make is that you can't base the hackability of the real os x for intel on what the dev machines were like. not that hacking os x will be insurmountable for that particular reason. that 60% figure you originally stated isn't really relevant.
the developer builds were made to run on the developer boxes, which bear little resemblance to what Apple is selling today. for example, the dev boxes use BIOS, these Intel Macs use EFI. black and white difference.
the more i look at it... the more i like it. i do think it's good! the fact is, no matter how i take it apart, no matter how i break it down, it remains consistent.
2006 will be the year that Linux takes over the desktop, 2007 will be the year that Duke Nukem Forever is released and 2008 will be the year that clean energy comes into vogue!
sadly, my sources say the green energy happens before Duke Nukem Forever, which precipitates a new, unfortunate name... Duke Solarem Forever, which causes the game sales to tank. if only they got it out a year sooner!
but when you do make this decision, the point is that there are tools that can read the contracts built into your code and inform the process. either you've done it using a refactoring, and the IDE does *all* of the work for you, or you make the change and the IDE gives you a laundry list of changes you need to address.
while dynamic typing can eliminate a lot of BS in small codebases, in really large ones, it's exactly Java's cranky, repetitive verbosity that makes large changes easy because your tools understand a great portion of your code as much as you do.
Ahh, yes... If only the owners of other sleazy, immoral and downright criminal corporations spendt more of their illgotten gains on charity, well the world would definitly be a much better place.
while i tend to find issue with Microsoft as much as anybody, they're no Union Carbide or General Electric... have a sense of scale.
it's difficult to use like a hammer, either. it isn't long enough to generate enough leverage, and i'd be happier if the weight were distributed more to one end.
The device does not contain a cellphone, which is a little confusing.
it doesn't have a can opener, either. what if i get stranded out in the woods? i'm stymied.
For the price, it would be nice to have Windows XP on the device. Even if it had to be in a dual-boot configuration, it'd make gaming easier.
i'd also like a port of OS/390, in case i want to convert my international banking corporation over to these.
Slashdot Mirror
sounds like i'm going to end up with my hand up my ass...
i'm kind of bummed that they didn't mention Locomotive, which really makes getting started with Rails very very easy. it seems like every Rails tutorial starts with "OK compile Ruby, install Gems, install Rails, install and configure MySQL, and 10 hours later, you can use this really simple framework!" when with Locomotive and SQLite3, you can basically just download one app, click two buttons, and start typing.
is it me, or are we just steps away from inventing the Infinite Improbability Drive?
another big thing that PDFs allow that Web pages don't really do (although there were efforts in this direction) is allow embedding of fonts.
this is totally inaccurate... you know you can inline assembly and plain C code in Objective-C, right? likewise, Finder, a Carbon app, has been building on Intel as part of the Marklar project for some time..
http://www.macnn.com/articles/05/12/28/intel.powe
http://www.zdnetindia.com/news/hardware/stories/1
http://www.google.com/search?q=apple%20intel%20mo
unless you have some other datapoint, i think it's pretty clear it's an Intel motherboard.
as far as i understood, this problem had a lot to do with an epidemic of bad capacitors in the industry and not anything having to do with the iMac design itself.
the developer builds were made to run on the developer boxes, which bear little resemblance to what Apple is selling today. for example, the dev boxes use BIOS, these Intel Macs use EFI. black and white difference.
protein blindfold? is it made out of tofu? sounds messy.
the more i look at it... the more i like it. i do think it's good! the fact is, no matter how i take it apart, no matter how i break it down, it remains consistent.
I WISH YOU WERE HERE TO SEE IT!
pushing opium on the Chinese, maybe.
while dynamic typing can eliminate a lot of BS in small codebases, in really large ones, it's exactly Java's cranky, repetitive verbosity that makes large changes easy because your tools understand a great portion of your code as much as you do.