The others also haven’t denied what I’m saying. Think about it.
Partly correct yes. All shortcomings of OH can be worked around. You can of course always just use the UDP, TCP and EXEC binding to do your stuff. Start time is slow? Just create one rule that loads the other rules in one by one after a given time. Problem solved.
But really that’s not how it should be. The core should be stable and each core bundle would only provide one way to do a thing (like the UNIX philosophy) and workarounds should not be necessary. .thing/.item files are contradicting this goal.
But I really don’t know why you fight against this improvement. You will barely notice if your .thing files are read in by the core-xtend or by a separate service io-thing-files.