gks
Joined 16 years ago
Joined 16 years ago
Honestly, people use what is best for them. That may be Windows, it may be Linux. Point is, don't knock it if it works for them.
I do some Ruby coding and for that I tend to use MacVim with a few nice plugins.
* 1Password - Password facilitator (http://www.agilebits.com, buy the Mac App Store version)
* OmniFocus - GTD/Todo list (http://www.omnigroup.com/omnifocus)
* OmniOutliner - Best list makinga pp ever (http://www.omnigroup.com/omnioutliner)
* OmniGraffle - Great for development purposes (http://www.omnigroup.com/omnigraffle)
* Acorn - Quick image editing (http://www.flyingmeat.com/acorn)
* VoodooPad - Personal Wiki (http://www.flyingmeat.com/voodoopad)
* Byword - Markdown editor (http://bywordapp.com/)
* Dropbox - Duh (http://www.dropbox.com)
* Fantastical - Calendar app (http://flexibits.com/)
* Launchbar - Launcher (http://www.obdev.at/products/launchbar/)
* Reeder - Google Reader client (http://reederapp.com/)
* Transmit - SFTP (http://panic.com/transmit/)
* VLC - Video (http://www.videolan.org)
Along with iA Writer, Writeroom, Sublime Text, etc etc... there are a lot of great apps. The above is my favorites.
I definitely suggest HomeBrew over MacPorts and Fink. I've had much better luck with it.
TextWrangler is a great free editor. I use Sublime Text 2 for anything that I may need some standard editing. For more complex stuff or if I'm doing more than opening a single file, I prefer MacVim.
uh... I'm not so sure this is a "problem."
I'd rather be "stuck" with a solid, stable, and useful operating system on a device that needs to be reliable and always available.
Am I disappointed in iOS6? Yes, but not necessarily am I concerned that I'm "stuck" with it.
Primarily my disappointments are pretty geeky.
1) Not enough major advancements (inter-app communication)
2) It seems a bit weird to introduce so many non-developer features in the keynote, at a developer conference.
Regardless, I don't think we're "stuck" with it. I think they need to up the game for iOS 7 though, and if they don't then we may have a bit of a problem.
My last year of college was spent carrying a 2010 Air around with me instead of the PowerBook and it was a signficiant difference in weight.
You just have to realize that a laptop isn't the only thing people carry around. So 4.6lbs isn't a big deal, but when you add it all up then the number starts to increase. Extra savings is beneficial.
I was mostly talking about the detractors, but those that do like the display aren't exactly different in the end.
If I were a betting man, I'd say you would probably compare the old iPad to your crappy monitor. Perhaps not as crappy in terms of colors, but in terms of reading text.
It was reading text and technical PDF files that really made me purchase the new iPad. It's such a drastic upgrade in this department that I can't imagine ever going back to the iPad 1 that I gave to my mother.
People kept saying that the iPad's Retina display wasn't worth it and that they couldn't see the difference. Then quickly proclaimed after a week or more of usage that they cannot fathom going back to the iPad 1 or 2 display.
I suspect the same is true of the new MBP display. While it may seem "ok" now. Give yourself time with it and you'll have a hard time going back to anything else.
Scaling is really needed at this point. Primarily due to the size of the screen. If the screen was larger then allowing the native resolution wouldn't be a problem. But at the current screen size (15") you would have a really hard time reading text.
There are images out there of each of the hiDPI resolutions including the 1920 resolution. On my 1920x1200 resolution 23" cinema display it is readable. But even I squint a bit at text on this display and it's 23". I can't even imagine trying to use that resolution at 15".
Sorry, but Apple's "we know better than you" attitude is spot on with this particular thing.
I've been an Apple user for years and bought my first Mac (PowerBook G4) about 10 years ago. My main computer is a Mac Pro (2006) and is in dire need of replacement. I'm pretty peeved that the Mac Pros are not on the upgrade list this week. But I will not argue with them about this particular choice in not allowing native resolution on the new MBP Retina display.
Native resolution on that display would be next to impossible to view easily.
An app written for iOS 6 can run on the iPhone 4S, iPhone 4, and iPhone 3GS (not to mention the iPad 2 and 3, and the newest iPod Touches).
An app written for ICS can only run on those 7% of devices running ICS.
This is how fragmentation works. The only fragmentation happening on iOS is for the original iPhone, iPhone 3G, iPad 1, and the old iPod Touches.
The only one that I don't quite grasp is the original iPad. Running on the same processor as the iPhone 4 and is much faster than the iPhone 3GS. Color me somewhat confused by this one.
If I have to change the way I write my application or can't include features in my application because most users don't have access to the APIs then that is part of what I'd call "Fragmentation."
When only a fraction of your users can take advantage of certain APIs then you have an issue.
I think it's perfectly acceptable that built-in phone features may be limited. You didn't expect to be able to keep the same phone for 10 years did you? Things change.
But two years is the standard contract length in the US. I'd expect phones to get updates for two years so that I can at least target the new APIs and gracefully handle it.
If I designed an app for Android, I'd have to target 2.3 because so few users are on ICS. But with the iPhone I can target iOS 5 and get a majority of users.
I typically skim through every headline posted on HN to see what I may be interested in reading. I can't say I've ever seen a "conservative x is lying" type of post. Perhaps I'm just oblivious, but I've certainly never seen it.
Granted, I wish we'd just avoid the subject of politics, especially when there is no tech reason for it, on hacker news.