You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2018. It is now read-only.
The current "OS X Framework" name defies convention, is difficult to work with, and is generally ill-conceived. All other frameworks I know of are built, within their targets, by their "display" name. It makes them easier to find, easier to debug, and easier to work with. This should be changed. Seriously.
Now that I'm looking at it.. the "iOS Library" should be called "libBlocksKit", or whatever the convention is there, as well.
The text was updated successfully, but these errors were encountered:
The current "OS X Framework" name defies convention, is difficult to work with, and is generally ill-conceived. All other frameworks I know of are built, within their targets, by their "display" name. It makes them easier to find, easier to debug, and easier to work with. This should be changed. Seriously.
Now that I'm looking at it.. the "iOS Library" should be called "libBlocksKit", or whatever the convention is there, as well.
The text was updated successfully, but these errors were encountered: