My 2008 (Core 2 Duo) MBP died last week and I figured I'd upgrade rather than repair it (I felt the Core 2 Duo was aging fast). I borrowed my mother's low-end MBA for the time being and Fell In Love. It was great for Xcode development/tricked-out Emacs for remote dev. (pretty much all you need).
However, I ended up with a tricked-out MBP 15" w/ SSD & Hi-Res screen - the reason is I need the peripherals &etc. for heavy apps like Logic. But let me tell you, if you're going MBP 15" - cough up for an SSD, but also ... get the Hi-Res screen. It's only $100 extra and you will feel as if you have an absurd amount of screen real estate.
I think the ability to combine C code in Obj-C allows for the usage of a huge legacy code base. However, I wouldn't be surprised if there was a design decision at some point that deliberately made it harder to port NextStep (NS) objects back to C. Creates lock-in...
The thing is, this team at Engadget has a really tight bond with its core fans ... their podcasts were more like listening in on a conversation between best friends rather than formal tech podcasts. It was just their style -- they/Josh wanted to up the game as far as they could, I mean, take a look at The Endgadget Show. Hell, compare their progress with Gizmodo's. I just feel like I have lots of faith in this team and Josh.
I don't have any inside knowledge w/ Josh / Nilay's exit, but I can say Enagdget editors tend to last about three years. Peter "left" and worked on rcrdlbl right after AOL acquired Engadget (twoish years into the site's life), then Ryan left after three years of tenure (2008), now Josh is leaving... not a surprise.
Blogging the Engadget way is hard. You have to always be on your game, making sure posts are timed, etc. It's not a picnic. These guys are really good at what they do, and having a corporate overlord wears on you.
I have totally been working on a site that would recommend music based on what your friends have been listening to. Similar to this, except it didn't have the great idea of tracking everything you listen to online through extensions. This is such a great idea. Congratulations guys!
Normally, my (favorite) CS professor would weigh code clarity more strongly than performance. However, he would sometimes put up assignments that focused almost entirely on the performance, in which he obviously changed the grading weights.
My question is, when will they force other clients to begin to use the Quickbar/#Dickbar? Or do you think this is just testing the waters?
P.S. I wouldn't mind them having it there if it wasn't so much darker and more distracting than the rest of the interface. I know it's supposed to catch your attention, but still.
