(Interestingly, everyone's replies focus on the *side note* in my OP, but OK...)
Some notes: - Take care to not confuse the *core* with the *standard distro*. - I believe Jeremy has expressed that a critical aspect with several separate components is the administrative burden to manage/update them. - @Arlen... you do the coolest experiments. @Sylvain, you write * What are essential functions for the core? Who will decide of this? > It's an open source project so anyone can theoretically decide whatever they want for their fork. There is only one owner of the main fork so he obviously decides for that one. My main OP point though, is that if plugin management was seamless then this would/could have a positive impact on the decision making process about what should go into core or not. It would simplify the whole question a lot, I think. > * What if my modules combination has some incompatibility issues? For a > "simple" user with no coding skills, who will fix this? > One could argue we already deal with this issue. I don't see how a smaller core or more plugins would change this aspect - ? <:-) -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/2fb4a885-f0aa-4528-809c-5f209020c07f%40googlegroups.com.
