For those not in the know, once upon a time a guy named Stewart Butterfield and some friends tried to make a game, called Game Neverending. Somehow they ended up making Flickr instead! Later, he tried again, this time to make a game called Glitch. Again, he failed, and somehow ended up with Slack. That's why Slack's 404 page is like this ("you found a Glitch!"). To further confuse things they sold the name Glitch off to Fog Creek Software who is now using it as the new name for Gomix, which is the new name for HyperDev.
One of these days that guy will actually succeed in making a game. Until then here's hoping his failures continue to be so successful.
In case you don't know, the team that made Slack first made a computer game called Glitch (https://en.wikipedia.org/wiki/Glitch_(video_game)). Slack was borne out of the chat system from Glitch. I believe this 404 page is meant to be reminiscent of that game.
I was pretty late to the party when it came to getting onto Glitch, but when I did Stewart Butterfield was the person who helped me get around for the first hour or so.
Stewart and Cal Henderson have a history of making a game, and then making a tool out of it later. Flickr came out of a game called Game Neverending, hence the 'gne' extensions on Flickr.
Am I the only one who's like -- you've raised $80M (another $250M on the way?), this 404 page exists, and yet your app still uses over a Gig of RAM for my rather pedestrian work uses? What gives?
Because this 404 page was probably made on a Friday afternoon while fundamental issues inherent with their core framework choices takes longer to fix. Just a guess.
I had a Java II professor who often said in class something along the lines of "between speed and memory, use more memory. Memory is cheap." So it's, somewhat, passed attitude through academia to students.
The point is, I'm using one org, dozen channels, etc -- some are seeing several times this amount of resource usage and with seemingly endless supplies of capital and users complaining, it seems to get less attention than it deserves.
I gave up on the web UI and started using the IRC gateway. Doesn't really miss anything for my usage, but there's always things like wee-slack[1] that offer threads, reactions, etc in an IRC client.
Now that this is on HN I bet their error log monitoring is going to go berserk. There's probably an Ops guy trying to figure out where all the 404s are coming from :)
It's really not that bad. I've seen pages return 200 with a http equiv refresh redirect on all places where 4xx errors and 3xx redirects would be appropriate... that screwed with everything that wasn't a real(-ish) browser.
One of these days that guy will actually succeed in making a game. Until then here's hoping his failures continue to be so successful.