Sven, It's hard to disagree, with what you say. The main goal I'm trying to achieve is to split these classes/objects into separate source files to make them readable, navigable and intelligibl. We can consider simply splitting it into separate files and concating them with some build tool or maybe updating them to ES6 or next and transpilling to ES3. Another option to consider is a Flow typechecker.
What I really want is to open a door for further development and improvement non necessarily serious modification right now straight away. P.S. I proposed TS just because I personally like it. On Fri, 17 May 2019 at 22:31, Sven Meier <[email protected]> wrote: > Hi, > > as one of the few maintainers of that code I'm not in favor of this: > IMHO it is not worth to introduce a new language and to complicate the > build process just to generate ~2500 lines of JS code. Code which is > closely tied to the browser, pretty stable, thoroughly tested and *almost > never seen much less touched by anyone else than the committers*. > I really appreciate the work you have put into this, but I don't see any > advantage. I'd rather reduce and improve the current code in JavaScript. > > I don't want to be a spoilsport, but on an official vote to switch to > TypeScript I will give a -0 at best. > > Regards > Sven > > > -- > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
