search

foundationkit / FoundationKit

Everything that really should be in Foundation, but isn't. Future-proof with ARC
Other
80 stars 9 forks source link

ARC only? #5

Closed MSch closed 13 years ago

MSch commented 13 years ago

I admit I'm biased, but since it looks like ARC will be the future, what do you think about making FoundationKit be ARC only? I hate the ARC compatibility macros with a vengeance.

eaigner commented 13 years ago

Other submodules don't compile with ARC ... so no chance there.

eaigner commented 13 years ago

But as I said... I'm still voting for a rewrite-all-from-scratch approach. I think this stuff MagicalRecord etc is way too high level anyways for a "Foundation" Kit.

eaigner commented 13 years ago

And I'm not a fan of other peoples crazy code styles ...

MSch commented 13 years ago

It's not hard to migrate stuff to ARC.

I don't think rewriting everything is a good idea, but stuff like MagicalRecord just doesn't belong in some core lib IMO.

myell0w commented 13 years ago

We discussed this, migrating submodules to ARC takes time and we loose the connection to the original repo and therefore have to maintain everything manually. I don't know about you, but I definitely don't have time rewriting everything from scratch that already works

eaigner commented 13 years ago

I don't know, this project was supposed to grow over time anyways, and not to be written over night. The whole reason for this was moving from a cluttered, quick-and-dirty class collection to a fresh and clean library. If this project is going to end up like the other one where everyone is just throwing things together as they please from other repos - whats the point?

myell0w commented 13 years ago

We don't want to do that, but there are some other essential repos and rewriting everything is just a waste of time. No Problem here with moving the external dependencies from FoundationKit to the app template, as mentioned earlier, but no interest in inventing another wheel

MSch commented 13 years ago

@myell0w We don't loose the connection to the original repo, we still can rebase and with rerere we won't have to resolve the same conflicts all the time.

I agree with @eaigner that a quick and dirty class collection is useless. You can never satisfy all needs for different projects with one big library, you just put the essentials in the lib and pull the rest in on a project-by-project basis.

MSch commented 13 years ago

See http://titanpad.com/foundationkit

Consensus says ARC only.