Don Edwards

The Pharoah should be an expert on old cloth...

And that trope is a bit more credible for kids age 16+ than it is for, say, Linus Van Pelt.

And that trope is a bit more credible for kids age 16+ than it is for, say, Linus Van Pelt.

And that trope is a bit more credible for kids age 16+ than it is for, say, Linus Van Pelt.

And of course there can be a huge difference between formal dress uniforms and what they wear in combat.

But Dan never implied that Zeus is not a real god. He simply stated that there are (in his fictional universe) beings who go by that name but are not real gods.
You won't offend Moslems by pointing out that there are beings named Mohammed who are not prophets...

GPS:
IMHO if the GPS satellites were taken out and putting up new ones were not feasible, at least for navigation in populated areas it wouldn't be a big deal. They'd just put scaled-down GPS "satellites" on existing cell towers... which would spur the more-rapid deployment of suitable towers to remote locations that currently have little-to-no cell service. That would be a lot more practical than putting up a completely-different replacement system AND replacing all the GPS-using devices.
There would have to be some tweaking because of earthquakes and such moving towers around, but not much... with the current system, the GPS satellites' opinions on their precise orbital characteristics need to be corrected based on ground observation every month (iirc), because of orbital perturbations caused by pretty much everything in this solar system and maybe the next one over, and are corrected every week (so if something goes wrong on the ground causing a correction or two to be skipped, it isn't a big deal).
Religion:
The way Dan has used names from mythology, he has never made or implied anything about the truth of any part of that mythology. Pandora, in particular, is explicitly an ordinary human in the mythology - not an immortal being of any sort. And it's pretty plain that some immortals take the names of deities from mythology because those names are of deities from mythology - their mythological origin predates the immortals borrowing them.
If you want a webcomic that touches a bit more firmly on mythology, try Gunnerkrigg Court. A number of mythological figures from several different mythologies have appeared there... one of them from the mythology most commonly known as Sesame Street (but not in the same role at all). So far, I think only one being that is explicitly a god has appeared, and one other has been referred to.
Or I'd recommend Brat-halla if it were still going... the way it ended, it really looks like the artists just got tired of it and could be bothered less and less (the last several pages are as seen by a blind character, and then it just stops without anything resembling an ending). But that was after a run of more than a decade, and was a lot of fun for most of that run. It quite explicitly gets into religion and mythology, particularly Norse but also touching on several others on occasion.
Wapsi Square doesn't directly get into religion or the standard mythology, but sort of crafts its own. Major characters include a guy who fought in the Trojan War, a part-phoenix, a couple of sphinxes... and then if you get into the fanfictions in the forum, there you'll find more religious stuff including an appearance by Hades and a few scenes where Jesus has a speaking part.
 

And if you aren't actually trying to write unreadable code (and aren't writing in APL or Lisp) there are few things worse than to have some electrical-engineering calculations written in Cobol by a Fortran programmer and then patched into a Cobol program by a person who understands neither electrical engineering nor Fortran (and isn't all that great at Cobol either).
Now add in that there's a suspected bug somewhere in that mess, and the person assigned to fix (not one of its creators) it is an immigrant whose skills as a Cobol programmer are sound but is unfortunately lacking skills in English.
(She begged me for help. It took me all afternoon to figure out what those two pages of code were doing, then all the next morning to be confident I had deciphered it correctly. And even though I know almost nothing of electrical engineering, it looked wrong. So I sent my explanation of what it was doing to the clients, asking if it was correct. The next day I got a response back - the code was wrong and they provided the correct formula - and spent an hour writing a third of a page of straight Cobol to do the same calculation. I delivered that to the lady assigned, and she actually could understand it.)
That was, oh, probably somewhere around 1995.
Anyone just starting out in programming, take away this message: the MOST IMPORTANT audience for any given piece of code is NOT the compiler. It's the programmer who has to fix or alter that piece of code. You or someone else, in a few hours or in a few years. That person has to be able to read the code. If the code is readable, it can evaluated for correctness and can be fixed as needed. If it's unreadable, it can't be fixed and nobody can be confident that it's correct.

I wrote this one management report (in Cobol 68)... they printed three copies of it, and that took between 90% and 110% of a box of fanfold paper.
One copy got distributed. First few pages went to the head of the company. Next several sets of a few pages went to managers who reported directly to the head. Next sets of a few pages went to managers who reported to them. And so on down the line. I don't think there was anyone who got as many as 10 pages unless they were temporarily handling two positions.
Another copy got filed in Accounting. And the third got filed in Information Systems.
Accounting and Information Systems really loved one thing I did on that report... I figured out how to easily put page footers on it (in addition to page headers) so they could look at the bottom of a page and see where they were in the stack, rather than having to open the binder wide enough to read the page headers. I also did a really good job of guessing what should be in the page footers.
Since I kept the code for the page handling separate, and could easily plug it into other programs, I got assigned to write a lot of reports after that.

Well, some people (not me) will be going WTF...

And if you aren't actually trying to write unreadable code (and aren't writing in APL or Lisp) there are few things worse than to have some electrical-engineering calculations written in Cobol by a Fortran programmer and then patched into a Cobol program by a person who understands neither electrical engineering nor Fortran (and isn't all that great at Cobol either).
Now add in that there's a suspected bug somewhere in that mess, and the person assigned to fix (not one of its creators) it is an immigrant whose skills as a Cobol programmer are sound but is unfortunately lacking skills in English.
(She begged me for help. It took me all afternoon to figure out what those two pages of code were doing, then all the next morning to be confident I had deciphered it correctly. And even though I know almost nothing of electrical engineering, it looked wrong. So I sent my explanation of what it was doing to the clients, asking if it was correct. The next day I got a response back - the code was wrong and they provided the correct formula - and spent an hour writing a third of a page of straight Cobol to do the same calculation. I delivered that to the lady assigned, and she actually could understand it.)
That was, oh, probably somewhere around 1995.
Anyone just starting out in programming, take away this message: the MOST IMPORTANT audience for any given piece of code is NOT the compiler. It's the programmer who has to fix or alter that piece of code. You or someone else, in a few hours or in a few years. That person has to be able to read the code. If the code is readable, it can evaluated for correctness and can be fixed as needed. If it's unreadable, it can't be fixed and nobody can be confident that it's correct.

And if you aren't actually trying to write unreadable code (and aren't writing in APL or Lisp) there are few things worse than to have some electrical-engineering calculations written in Cobol by a Fortran programmer and then patched into a Cobol program by a person who understands neither electrical engineering nor Fortran (and isn't all that great at Cobol either).
Now add in that there's a suspected bug somewhere in that mess, and the person assigned to fix (not one of its creators) it is an immigrant whose skills as a Cobol programmer are sound but is unfortunately lacking skills in English.
(She begged me for help. It took me all afternoon to figure out what those two pages of code were doing, then all the next morning to be confident I had deciphered it correctly. And even though I know almost nothing of electrical engineering, it looked wrong. So I sent my explanation of what it was doing to the clients, asking if it was correct. The next day I got a response back - the code was wrong and they provided the correct formula - and spent an hour writing a third of a page of straight Cobol to do the same calculation. I delivered that to the lady assigned, and she actually could understand it.)
That was, oh, probably somewhere around 1995.
Anyone just starting out in programming, take away this message: the MOST IMPORTANT audience for any given piece of code is NOT the compiler. It's the programmer who has to fix or alter that piece of code. You or someone else, in a few hours or in a few years. That person has to be able to read the code. If the code is readable, it can evaluated for correctness and can be fixed as needed. If it's unreadable, it can't be fixed and nobody can be confident that it's correct.

I wrote this one management report (in Cobol 68)... they printed three copies of it, and that took between 90% and 110% of a box of fanfold paper.
One copy got distributed. First few pages went to the head of the company. Next several sets of a few pages went to managers who reported directly to the head. Next sets of a few pages went to managers who reported to them. And so on down the line. I don't think there was anyone who got as many as 10 pages unless they were temporarily handling two positions.
Another copy got filed in Accounting. And the third got filed in Information Systems.
Accounting and Information Systems really loved one thing I did on that report... I figured out how to easily put page footers on it (in addition to page headers) so they could look at the bottom of a page and see where they were in the stack, rather than having to open the binder wide enough to read the page headers. I also did a really good job of guessing what should be in the page footers.
Since I kept the code for the page handling separate, and could easily plug it into other programs, I got assigned to write a lot of reports after that.

Considering the weather in upper layers of atmosphere, I think virtual stacks are much better for the books involved.

But it turns out that the Library of Alexandria was just an annex/entrance to the real Library, which exists in its own pocket universe accessible from Wapsi Square.

Whoever is responsible for deciding that autocorrect should be turned on by default in any given device/OS, should be sentenced to one year of punishment wherein they MUST say everything by means of that device/OS with autocorrect turned on and not allowed to ever reject or amend autocorrect's changes.
And if they ever start turning on grammar-autocorrect by default, make it five years.

Whoever is responsible for deciding that autocorrect should be turned on by default in any given device/OS, should be sentenced to one year of punishment wherein they MUST say everything by means of that device/OS with autocorrect turned on and not allowed to ever reject or amend autocorrect's changes.
And if they ever start turning on grammar-autocorrect by default, make it five years.

I've contemplated (particularly a few years ago when a certain series of books and shows were popular) getting a shirt with Tinkerbell on it. Either scolding, or laughing her arse off. Alongside the words "Real Sparkles Don't Vampire".

Well, there was, but it sorta just died after an almost-13-year run.

WHAT! You have a birthday and don't tell anyone until afterward? What kind of person are you! You're supposed to tell us these things in a timely manner!
But since you didn't...
 
....
 
Happy berated birthday.
 
ok I'll go hide now

I just had one of those times when you know exactly what a link leads to without clicking it...

I hope you don't mind if I ignore your advice and just skip the whole thing.
 

I just had one of those times when you know exactly what a link leads to without clicking it...

In fact, once you decide to leave your current planet, space is pretty much the only thing that is NOT far away. Other planets - far away. Other stars - seriously far away. Other spiral arms - way far away. Other galaxies - yeep.

Here's one for you.