Designer News
Where the design community meets.
Joined about 7 years ago
+1 on this. Asset originals, if they are many and usually large, should not be versioned with plain Git. Cloning becomes a pain, and the repo size swells with further changes.
I believe Pixelapse can also act as version control. The pros include being able to visually see version diffs and history. The actual file sharing works a lot like Dropbox, with a desktop client. They got acquired by Dropbox, so probably the main caveat to using them is a future platform migration.
I firmly believe versioning asset originals should be different than versioning asset exports. Exports, given they are already optimized files, should be included directly in the main codebase and versioned with the code.
See http://hlfcoding.github.io/hlf-jquery for an example of the template in action.
Definitely agree re. parse direction being right to left. I'm also definitely assuming that a more specific (not in specificity) selector yields less searching by the browser, and in this case not for the child, but the parent, which in this case would be an immediate matching parent, not any ancestor.
Its glyphs have a slightly inconsistent vertical placement. I've used it on projects at large font sizes, and vertical-alignment with icon fonts and other elements proved harder than with Helvetica or similar.
CSS parsing tends to be much lower on the list of browser performance concerns, and perhaps may not make the list at all. It's also probably less of a problem if it's restricted as a child selector (>
) and not used on wildcards (.foo :not(...)
).
Peng hasn't upvoted anything yet.
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
Good:
Needs work:
Consider removing: