Break backwards compatibility - when/what?

[pmario]

@TW_Tones

• As far as I can see, the main place this is a problem is in the composition of tiddlers. We already permit other markups and @pmario’s Custom Markup, and “space space” paragraph etc… all tackle this with backwards compatible additional features.

I did request the fix of the paragraph generation, because I could not fix the problem with the custom-markup code. It’s one of the reasons, why it’s still in experimental state. I could create workarounds, but those workarounds cause other consistency problems. Workarounds make the code more complex, more fragile and less maintainable.

I did try again and again, but the issue is so low level, that there is no way to work around it, without changing the core code. … which is not 100% backwards compatible.

[pmario]

@jeremyruston

I have found that an unexpected consequence of the path that TiddlyWiki has taken is that sometimes we have to put the needs of users before the needs of developers. By that I mean that most developers would prefer to be able to use the latest and greatest features of the platform, but our users are actually better served by being able to run TiddlyWiki on the broadest range of platforms.

I can live with a TiddlyWik Version 5.2.4 that works as it is. So if IE is needed and v5.2.4 works with it … Stay with it, but don’t expect any new features. … If v5.2.3 worked with an IE configuration but v5.2.4 does not. Stay with v5.2.3.

Done.