On 12 November 2017 at 14:26, Ole Ersoy <ole.er...@gmail.com> wrote: > I tend to look at code as just a blueprint proven blueprint / good set of > guidelines for how to implement something.
There's potentially a bit of boilerplate or heavy lifting we can utilize from the existing Chainsaw sources that can be mechanically converted into modern Java, Kotlin, etc. This is also why we haven't rewritten every single C library and application in Rust: who knows what new bugs pop up with a rewrite! Do note that refactoring and rewriting are different concepts. > To me it looks like a migration to nowhere, but if you have users and > clients that are in need of that then by all means. Judging by the subject > I thought this was "Lets turn this 1960 corvette into a Tesla" type > discussion. The existing source for Chainsaw only required Java 1.4 until recently which is a rather old version of Java. Even just recompiling it for Java 8 was a bit of an enhancement simply due to the API docs not looking like they're from the 90's anymore! > Have you used Atom? All (Probably) UI developers have it at their > disposal. It drives Elektron development. It's constantly being worked on > by Github and a gazillion open source developers. No one has to use > Elektron. Just deploy the app to github pages and allow users to use it as > a progressive webapp. Electron is just one more deployment option in > addition to browser and mobile. > Atom isn't the best example of a good Electron app (the ancient Emacs memes about resource usage apply to Atom at about 1000x the level). I'd point to VSCode as a good example of an Electron app, though I don't use it much. > I would think the whole thing could be turned into a decent Angular 5 app > in a few days. After that I'm sure it will do all sorts of things as it's > now a much more attractive base to iterate on. > If you'd like to contribute a proof of concept, that would be great! I'm not a fan of frontend web development anymore (see my comments earlier about Elm being one of the sane places to work there), so I don't know how much I could help with that. -- Matt Sicker <boa...@gmail.com>
