They allow the extension to be the fire emoji
Which is a shame because the people who created Mojo are definitely not amateurs.
But, when you're trying to show off your Unicode support to Californians, emojis get more reaction than umlauts.
These things seem unrelated—experienced people are allowed to have fun too. I don't see how this correlates with lack of experience at all. This just speaks to your personal bias against having fun.
Yes. Yes you can.
And God help us all.
I am literally going to put some CSS emoji easter eggs in my web app right now... o_O
Edit: I got my htm and html backwards and now comment not sense. Fixed now but obviously the folks below were right / responding to an earlier version.
That way if I change my site infrastructure from, e.g. static html, to php, to mediawiki, to cgi-bin, to asp, to ruby on rails, all my URLs can stay the same (because cool URLs don't change) throughout, without containing misleading legacy baggage.
Oh, yeah. I mean, you have to configure the server to treat extensionless files as html/cgi/php/whatever anyway, so you could just have it load extensionless URLs from .html/.cgi/.php files, but I prefer to keep my server config as "surprise-free" as possible. If `/article/foo` is served from the file `$DOCUMENT_ROOT/article/foo` on the filesystem, I find that less confusing for everyone than if it's served from `$DOCUMENT_ROOT/article/foo.php`.
It's a matter of personal preference, for sure. Just like `.htm` over `.html`. (Or `.jpg` over `.jpeg` for that matter.) I wouldn't say the way I do it is "right", but it's a trade-off that works for me.
Where the inertia of the history of 3-letter extensions in DOS and the likes is what caused this convention, of course
.rust.programming.language would make far more sense than pretending Rust will ever need to work in DOS.
You are not looking close enough. While Java source code has four characters in its file extension (.java), the output of its bytecode compiler has five characters in its file extension (.class).
perl -> pl
python -> py
rust -> rs
ruby -> rb
javascript > js
But java?
java -> ja? jv? jav?
Clearly Sun should've gone with a different name for the language entirely, I dunno, maybe they could've named it after an oak tree instead:
oak -> ok
Hmm, maybe I could get used to "jv" after all.
Then Perl tried to steal it.
No one uses the latter, though.
typical java, prioritizing verbosity at the expense of efficiency /s
Not entirely sarcastic though, looking at e.g. DescriptiveFooThingFactoryFactory
The Spelt Out File Extension Pattern?