palordrolap

You’ll forgive me if I ever-so-briefly misread your boilerplate link as “And then I woke up.”

thatsthejoke.gif

Sounds a bit like the S&M methodology. SpaceX & Musk

Cygwin on Win7 back in the day was pretty close tbh.

JavaScript, like some other languages of the time, was designed with the Robustness Principle in mind. Arguably the wrong end of the Robustness Principle, but still.

That is, it was designed to accept anything that wasn’t a syntax error (if not a few other things besides) and not generate run-time errors unless absolutely necessary. The thinking was that the last thing the user of something written in JavaScript wants is for their browser to crash or lock up because something divided by zero or couldn’t find an object property.

Also it was originally written in about five minutes by one guy who hadn’t had enough sleep. (I may have misremembered this part, but I get the feeling I’m not too far off.)

I don’t know about that. Non-binary files have been put into bin directories for decades at this point. (Feel free to marvel at the analogy.)

Delete the contents and it’s not just binaries going to the bit-bucket.

The joke here is more “Tony Lazuto said to execute these files.”

I’d say it’s more like setting up a handler for a callback, signal, interrupt or something along those lines.

Function declarations by themselves don’t usually do that. Something else has to tell the system to run that function whenever the correct state occurs.

That doesn’t account for unconditional come-froms.¸but I expect there’d have to be a label at the end of some code somewhere that would give a hint about shenanigans yet to occur. Frankly that’d be worse than a goto, but then, we knew that already.

perl -le 'use bignum;print+pack"H22",(61966753*385408813*916167677<<2)->to_hex()'

Alas, Perl doesn’t bignum by default

The first one is clearly wrong because no-one (oh alright, almost no-one, Toe-Jeans Georg) wears leg-wear on our toes.

Third option: The top layers are covered by a poncho and only the eight pairs at the bottom have leg-wear. This works when considering each subtree as a separate tree in its own right, up to arguing about how many ponchos are then required.

Fourth option: The top two branches wear leg-wear and those below go in footwear of some sort.

Well, it is theoretically possible for code to cause a compiler to segfault. As for how, well that’s a different matter. You’ll need deep knowledge of the compiler, or else the assuredness that it can’t possibly happen. Because then it will.

Hasn’t Office worked under Wine since forever?

(And if not, what are the show stoppers?)

Lawful good is asking for trouble. Before they know it, they’ll be inundated with e-mails to their personal company address with poorly worded help requests. They’ll spend half their time making and updating tickets on the user’s behalf that would have been mostly automatic if they’d gone the Lawful Neutral route. They need to insist requests are sent to the main support address. I’m assuming that’s tied directly to the ticketing system.

When I was being Lawful slightly-better-than-neutral, I’d create the ticket and then put a paragraph in the reply telling them to please not e-mail me directly in future, because one day I might be unavailable and their e-mail could go unseen for hours or even days.

Repeat offenders would eventually do it at a time when things were busy too, so I’d be concentrating on the tickets and not things to my personal address, so that slight delay often helped it sink in.

Better than a 200 JSON reply containing the 4xx. “Aay it worked!” “oh.”

wait until you learn about .tar.lz

Kind of redundant. Both .zip and .rar store an index of files within the archive and are a bit ‘inside-out’ when it comes what we get from tar.gz.

That is, ZIP is pretty close to what you’d get if you first gzipped all your files and then put them into a .tar.

RAR does a little more (if I remember correctly), such as generating a dictionary of common redundancies between files and then uses that knowledge to compress the files individually, but better. Something akin to a .tar file is still the result though.

Bzip2 compression is often surprisingly good with text files, especially log files. It seems to “see” redundancies there - and logs often have a lot of it - far better than gzip and sometimes even lzma.

Anyway, if I saw a bunch of tar.bz2 files, that’s what I’d expect to find in them.