It's mostly security. It doesn't matter at this point, but once I implement server-side permalinks and user accounts, I wouldn't feel comfortable having both parts on the same server.
But seeing how it's actually cheaper to rent multiple small servers instead of a single big one, it was (in hindsight) a good decision wrt resources as well. As it is, I can simply deploy a few arenas and let them share the load.
Anonymous
6:57 AM
@Dennis Modularization is almost always a good thing
@Mego I think it is in this case. This actually has yet to happen with the new backend, but v1 has an unkillable process on a few occasions that left TIO down for a few hours and forced me to hard-reboot the server. With several arneas, that wouldn't matter that much.
@Mego Some interpreters spawned sub-processes that survived after killing the main process. Since every process tree has its own MCS range now, it's much easier to identify and get rid of them.
Anonymous
@Dennis That's extremely odd. I suppose killing the entire tree should've been happening.
Anonymous
I mean, I suppose you should've been killing the entire tree
I'm not sure what you mean? I was just suggesting that other formats should be supported too. And I provided a relatively easy-to-implement solution. I was talking about graphical output.
@AndrewSavinykh I thought I had already made the change and was serving deflate-min.js only for an unofficial TIO client that relies on it, so I excluded it from the repo. The latest commit sources pako.min.js. github.com/TryItOnline/tio.run/blob/master/index.html#L614
@Mego That sounds neat, but definitely something for v2.
There are two things right now I'd like to add to Nexus's frontend:
1. A user-selectable encoding. The current defaults should remain defaults, but all valid encodings should be selectable. Ideally, it should also check if the characters in question can actually be encoded using that encoding.
2. An on-screen keyboard, preferably QWERTY-like. For SBCS's, it should somehow accomodate all characters.
In case you're interested in implementing either one of those, I'd be immensely grateful.
@Downgoat why, I like the idea, the art of golfing is to spot things that an automated process cannot. By all means we should use automated processes to reduce the tedium of golfing, like checking for common patterns.