>also want to support the latest Safari Sure.
>I'm curious though, what is it that needs cleaning up? Or you just mean best practices updates and reformatting to make it easier to read? Yeah, mostly just things like ES6 classes, const, maps, sets, etc to make the code more organized and readable. On Mon, Oct 21, 2019 at 12:06 PM ocket 8888 <ocket8...@gmail.com> wrote: > I would say you probably also want to support the latest Safari, given the > high population of Mac users known in the pool of operators/users. > I'm curious though, what is it that needs cleaning up? Or you just mean > best practices updates and reformatting to make it easier to read? > > On Mon, Oct 21, 2019 at 10:43 AM Robert Butts <r...@apache.org> wrote: > > > Quick question: would anyone be opposed if we used modern JS in the TM > UI? > > This is currently ECMAScript 2018, but I'm really asking if we're ok > > allowing any standard supported by the latest Firefox and Chrome. > > > > Of course, we could use a big framework like Angular, or a shim/polyfill > > compile tool like Babel. But TM's UI is really small, it's always been a > > single file, and IMO really isn't worth the overhead of big things like > > that. > > > > My thought is, TM administration is an admin thing, even when TC has > > Self-Service, it's never something a CDN client will need to see or work > > with. So requiring modern browsers for admins/devs seems reasonable. > > > > This isn't something I or anyone is planning or prioritizing at the > moment. > > I was just thinking it'd be nice to clean up the TM UI if I can find the > > time, wanted to get consensus before I wrote anything unsupported by old > > browsers. > > > > Thanks, > > >
