abbott
Joined 16 years ago
Joined 16 years ago
Illustrator is still highly relevant for its strength, vector based work, while Sketch has surpassed Photoshop for UI.
The momentum is only increasing, even with bugs and issues found in Sketch. It's obvious the interface design community desires better tools. I wonder if Adobe Comet stands a chance with disruption we're seeing?
This restuarant appears out of nowhere in Bushwick/warehouse district. Being a North Carolina native I was a huge skeptic walking in. Mr. Ho has an NC (and SC) flag on the wall, usually not a symbol of pride outside the state (even for me), but in the case of BBQ it's respectable and makes a statement to anyone who know's anything about pulled-pork BBQ.
If you're ever in Brooklyn, definitely check it out. There's something to be said about eating, drinking, and enjoying the vision of an entrepreneur. Impossible to do with your stereotypcial start-up.
A launch for a client also went through the same problem in 2010, and that was after 5 years of managing other WP installs (including 2 VIP WP sites). I've seen it happen too many times for it not to be Automattic's problem to address more so than they're doing now.
Stay away from self hosted WP unless your install is absolutely bullet proof, and cross linking, especially to resource files from other WP sites is the last thing you should ever do because you do not control their security which can directly affect yours, or at least your black list vulnerability due to associated content.
Our office used to be above Automattic's in SF, and I love those guys, and what Matt has done for the web, but with great power comes with great responsibility.
Stanford academic guidelines endorsed and supported by Apple, Inc.
I wonder what approach Evan Doll uses at Flipboard...hmmm?
I am also anti-nibs:
Examples — NIB caching; Managing UI in two places (class & IB); Nightmare managing versioning and diffs (same from @SeoxyS), especially in a team environment; "Having classes that may be instantiated both from code or from NIB deserialization adds a layer of complexity and messiness to your app" (Repost from @SeoxyS); Want a custom UI implementation? Forget about using NIBs
Without NIB's — yes you have to write a lot more code. Concerns of code bloat are overblown. Your viewcontrollers are likely already bloated without inline UI implementations.
It really comes down to personal preference especially on smaller projects/apps, but I'd argue if you have ever worked on a large scale app that you are responsible for maintaining and enhancing long term, your opinion of NIB dependencies will change. This is especially true as your team pushes the limits of the UI and app performance. If I was going to teach you how to write an app, I'd explain what NIBs are (known pros and cons) and let you decide for yourself. Just like explaining to (my) kids about religion.
Fun fact, not all WWDC examples use NIBs. Say what?! Blasphemy!