Sort of :) Explore the "c drive" to learn about the libs. I couldn't find an uncompressed version of the main code, but in the Chrome devtools most scripts are uncompresed.
This is a work of art. The ProgressQuest game loading screen is one of the funniest things I've seen in a while. Like all well-told jokes, it's in the timing.
ProgressQuest[1] was an actual "game" many years ago. It was kind of the progenitor of the current incremental/idle games. Looks like its basically the whole thing compiled to this ui.
Somebody took 'undefined behavior means that your compiler may optimize out large swathes of code in favor of execve("/usr/games/nethack"); way too seriously" :-)
Accidental "works best in browser X" 90s reference right there.
I find Safari superior to every other browser on any platform in every possible metric except for dev tools, which took a nose dive when they ditched the open source WebKit one for this calamity.
Those using IE6 also thought it was the best for a long time. Only because developers adhered to it's quirks, though, so stuff worked there (and not in "better browsers"). In the same way people accommodate Safari today, otherwise you would have felt left out a long time ago.
>Those using IE6 also thought it was the best for a long time.
And it was. Is was also closed source and had its own ideas of what standards mean (even though its “version” of the box model actually makes more sense and it's generally preferred by most developers today. Oh yeah, and Ajax.)
Webkit, on the other hand, is open source and a huge proponent of standards compliance.
The joke isn't "works best in IE" the joke is "Safari is the default browser that ships with the OS, few people get a better browser, and even though it's a piece of shit you have to continue supporting it."
>I find Safari superior to every other browser on any platform in every possible metric except for dev tools
I could remove nearly 15% of my CSS if I stopped supporting Safari at work and I wouldn't need a hundred different quirky workarounds to make the sites look even remotely how they're supposed to look. It fights me every inch of the way and then has some of the worst dev tools for debugging where any issues are.
I'd rather support IE8 for eternity if it means I never have to write another `@media screen and (min-color-index:0) and(-webkit-min-device-pixel-ratio:0) {}` in my CSS again.
I've been writing CSS for years, everyday, don't remember the last problem I've had with Safari or any other modern browser, as a matter of fact.
I do get an ocasional glitch with Firefox, but it's very rare.
Perhaps if you described the problems you experienced instead of the hacks you are using to identify Safari this could be a more fruitful conversation.
Safari is a freaking amazing browser, lots of people use it by choice.
I create websites for the healthcare industry. I know exactly what I'm saying. There are some clients that I still need to write IE7 fallbacks for - and a single client that I still write IE6 fallbacks for. Lucky for me our contract has dropped IE7-9 support by default unless it is specifically requested by the client.
Apologies, but offhand I can only think of flexbox issues (specifically related to wrap/min-width, which has been fixed in version 11) and with interactive form validation (which was only just fixed in version 10 or 10.1). I run into various issues when testing on iPhones and the largest section of edits caught in any internal QC are always iPhone/Safari related. With relative certainty nowadays - if it works in Firefox, it works in Chrome and Edge. But then I always need to write some workaround or another for Safari.
The biggest issue is that even when these bugs are fixed - I still need to support them for an extended period of time because for whatever godforsaken reason, Safari updates are tied together with operating system updates. Want the newest Safari? Buy a new iPhone. It's the Windows XP/IE8 problem. Where IE8 had to be supported only because many users were still using XP and couldn't upgrade to IE9 even if they wanted to.
Safari is not an evergreen browser and that's a fair criticism.
However, you can run the latest browser and OS (and most people do) on a 5 year old device, which is about as much as the battery will last anyway. The situation is much worse on Android.
I suspect it just uses the original levels as is. I replayed E1M1, and literally every single thing - items, secrets, even wall decorations - was where it was in the original map (don't ask me why I still remember these things...). The only differences are in replaced graphics. Also, the secret room elevator does take you to the secret map, which, at the first glance, also looked like the right thing.
129 comments
[ 4.2 ms ] story [ 267 ms ] threadIs this open source? So we could see how it was made?
Uncheck that box and you'll have a chance :D
I guess it's an in-joke about people leaving IRC-clients running in persistent shell-sessions and never checking in.
That said, it can be a lot of fun :)
[1] http://progressquest.com/
Note: units intentionally left blank
- Half Life 3
- Defrag <3.
- Running Windows93 inside Windows93 inside Windows93 inside Windows93...
A work of art, indeed. Kudos!
I'd like to throw some event handlers on "Puke Data" to allow changes to the dsp graph.
Accidental "works best in browser X" 90s reference right there.
I find Safari superior to every other browser on any platform in every possible metric except for dev tools, which took a nose dive when they ditched the open source WebKit one for this calamity.
I can't really disagree with you, but Safari is exclusive to macOS...
And it was. Is was also closed source and had its own ideas of what standards mean (even though its “version” of the box model actually makes more sense and it's generally preferred by most developers today. Oh yeah, and Ajax.)
Webkit, on the other hand, is open source and a huge proponent of standards compliance.
>I find Safari superior to every other browser on any platform in every possible metric except for dev tools
I could remove nearly 15% of my CSS if I stopped supporting Safari at work and I wouldn't need a hundred different quirky workarounds to make the sites look even remotely how they're supposed to look. It fights me every inch of the way and then has some of the worst dev tools for debugging where any issues are.
I'd rather support IE8 for eternity if it means I never have to write another `@media screen and (min-color-index:0) and(-webkit-min-device-pixel-ratio:0) {}` in my CSS again.
I do get an ocasional glitch with Firefox, but it's very rare.
Perhaps if you described the problems you experienced instead of the hacks you are using to identify Safari this could be a more fruitful conversation.
Safari is a freaking amazing browser, lots of people use it by choice.
>I'd rather support IE8 for eternity…
I don't think you know what you're saying.
Apologies, but offhand I can only think of flexbox issues (specifically related to wrap/min-width, which has been fixed in version 11) and with interactive form validation (which was only just fixed in version 10 or 10.1). I run into various issues when testing on iPhones and the largest section of edits caught in any internal QC are always iPhone/Safari related. With relative certainty nowadays - if it works in Firefox, it works in Chrome and Edge. But then I always need to write some workaround or another for Safari.
The biggest issue is that even when these bugs are fixed - I still need to support them for an extended period of time because for whatever godforsaken reason, Safari updates are tied together with operating system updates. Want the newest Safari? Buy a new iPhone. It's the Windows XP/IE8 problem. Where IE8 had to be supported only because many users were still using XP and couldn't upgrade to IE9 even if they wanted to.
However, you can run the latest browser and OS (and most people do) on a 5 year old device, which is about as much as the battery will last anyway. The situation is much worse on Android.
OH BOY do I know your pain.
Ah well, it's not like those XP machines that the NHS loves so much were an attack vector in a recent, prolific cyber attack, no no.
now it's crashed and won't reload.
is there a work around for my workflow?
I wonder how many hours I could waste looking for more Easter eggs ;]
Nice :)