Did you not notice that the shirt has custom writing on it?

Boy, I recently had to look into the Java backend to figure out… something. I can’t remember.

It turns out that they needed to inject a bean into their class which was itself calling a factory, which according to documentation, instantiated three other classes just to make a fucking HTTP request! What’s worse, that clusterfuck of a (fairly standard) library required the base URL to be declared separately from the actual paths, and both the base URL needed to end with a slash, and each path must begin with one. Every reasonable programmer would assume that this is a mistake because the final path would end up with two slashes, but the library actually required that.

Meanwhile, frontend: fetch('url').then(r => r.json()).then(beHappy)

You sure want to die on this hill.

You can clear your denomination from your file. I don’t know if it survives in a changelog, though.

I think you underestimate the cost of shooting a real guy sitting at a table. Casting, lighting, filming, makeup, props, location, color correction all cost money. And I probably forgot about a few things. Film is ridiculously complex.

In a little town in the Netherlands life was good. The planning committee actually had smart people who made sure to plan the town according to the people’s needs. Kosher butchers, for instance, were placed near Jewish community centers. They could do that because the town had kept records on who lived where, including the people’s religion. It really was a utopia.

Then the nazis invaded, got their hands on those registries, and with utmost efficiency cleared the town of all jews.

I don’t know if this story is true. I read it (probably much better worded) a few years ago. But it honestly doesn’t matter if it’s true.

But I can critisize it for having only one sharp edge instead of 2. Or for being too short or too long. Or for having a handle that’s not shaped well for my hand. (That last metaphor is probably the correct one for the sentiment I’m going for.)

Error: Too many unprocessed floats.

No; since every user defines the perfect program differently. Which should be the default behaviour(s)?

If this is you, I applaud your dedication.

I imagine that similar regulations exist in the EU. For instance, no copy machine will let you copy a Euro bill.

https://en.wikipedia.org/wiki/EURion_constellation

You can, but you shouldn’t. You don’t know what else relies on Math.random. That’s why there’s the wrapper function. That you can override in unit tests without worrying about other, unrelated code.

“You ain’t gonna need it”. It means: Build the thing you need now and don’t try to predict what you’ll need in 3 years. You ain’t gonna need it anyway.

For anyone else having trouble parsing the lower part: “Seeing a shooting star [is] itself a wish for many.”

If you want to see shooting stars, the next good opportunity is around April 22, where the Lyrids produce about one shooting star every three minutes (in good conditions).

If you’re patient but very easily distracted, wait for the Geminids around December 14 producing about 2 shooting stars per minute; or the Perseids around August 12 with slightly fewer.

All of the above assumes you’re in the Northern hemisphere.

https://en.wikipedia.org/wiki/List_of_meteor_showers

If I understand correctly, you want to check the current domain (eg. w3schools) against api.w3schools and www.youtube, and return true for the first and false for the second (or the other way around)

Then technically it’s possible without string splitting:

const href = 'retrieved-from-the-anchor-element';
(new URL(href, location.href).hostname).endsWith(location.hostname)

Thanks for the write-up. Your use case is different from all I’ve ever had. It’s good to be reminded that my world view isn’t universal.

Personally, I would be fine if GIMP had just said, “too many operations, shrinking Undo history” or something like that. No amount of optimization gets rid of this issue. At some point, the machine’s resources are just exhausted.

I see your point regarding global scope. But personally, I’ve never encountered an issue with it. And it’s kinda nice not to have to import fetch every time you need it.

Regarding subdomains, if you’ll humor my curiosity: What’s the use case? I also wonder what an API for this might look like.

const {domain, subdomains, rootDomain} = new URL('https://wikipedia.org/')
//       'wikipedia.org', [], 'wikipedia.org'
const {domain, subdomains, rootDomain} = new URL('https://foo.bar.baz.net/')
//       'foo.bar.baz.net', ['foo.bar.baz.net', 'bar.baz.net'], 'baz.net'

Pretty sure OP’s image is hyperbole.