If you don't mind, I'd like to ditto that and adorn with a "why I ditto(?)"
To me, the words "card" and "record" have semantic meanings to me that don't quite fit the semantic meaning of "tiddler". Well, the semantic meaning I've attached to "tiddler" is, to me, much broader/flexible than card or record. To me, a "tiddler" is an information component, as per knowledge componentization <https://blog.okfn.org/2007/04/30/what-do-we-mean-by-componentization-for-knowledge/> (which I prefer call "information/knowledge/content componentization".) Whatever "language" a tool uses, I happily adopt that language. Once that language is ingrained, I do tend to get annoyed at the change in language and having to rejig my mindset. So I stubbornly tend to keep using the old language because I've become attached to it and visualize/understand everything in this terms. Well, until I get used to the new language. (That said: I still call my Seagull "M4" a Seagull "Merlin" as per original name many years after the name change, because "M4" to me sucks.) Regardless, I am wildly enjoying this discussion about name/jargon, because of all the awesome intertwingled insights. Cheers and thank-you all for yer thoughts ! >> Well. Not sure. I still prefer Tiddler as FRAGMENT. A bit more. >> >> Why? The problem with "Record" and "Card" is both imply >> self-contained-wholeness. Basically echoing database structural units. >> >> I'd need convincing our "Atomic Units" should be conceptualized that way. >> That is NOT how I experience the "fragment" in TW/XEMEMEX. >> >> It is actually NOT so self-contained or self-substituent. >> >> Just thoughts >> TT >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki/bd62bbf1-c748-468c-ac0a-49904c8d7397n%40googlegroups.com.
