That’s because, to my understanding, the prerequisite to be able to launch one is “handle the raw, unfiltered firehose of all the traffic on the entire platform”. A relay has to be a mirror of the entire company’s hosting infastructure, and you’d have to essentially do it for free. It’s no puzzle to me why no one’s done it yet.

For a few years now, Windows has had the capability of marking certain directories as case-sensitive. So you can have a mixed-case-sensitivity filesystem experience now. Yeah. :/

I feel like the “we don’t know what this function does” meme is kinda bad. There’s no reason beyond maybe time crunch why you shouldn’t be able to dissect exactly what it does.

Despite this, the notion of a load-bearing function is still very relevant. Yeah, sure, you know what it does, including all of the little edge case behaviors it has. But you can’t at this time fully ascertain what’s calling it, and how all the callers have become dependant on all the little idiosyncracies that will break if you refactor it to something more sensible.

It has been several times now where a part of my system of legacy code broke in some novel fantastic way, because two wrongs were cancelling out and then I fixed only one of them.

Wow, I found the one other MATE user. Cheers.

It’s not clear at all, no.

Is this proposal patently ridiculous? Yes. Do I believe there’s at least one legislator in Mississippi who unironically believes in this bill exactly as written, and is playing this completely straight? Considering all that’s happened so far, why not?

Satire doesn’t work when the obvious hyperbolic nonsense is within actual expected behavior of the satirized.

I won’t claim one way or the other that this is or is not satire. I don’t know who this legislator is and I don’t really care. But no, with the whole article you’re pasting everywhere in this thread as my only context clue, I certainly didn’t find enough evidence to be convinced he doesn’t actually believe this.

Sure, but then the wait staff expects you to tip at least 20% for simply being given one, and if you don’t you’re an asshole.

Security questions don’t care what you put in there. It’s not an exam. It’s basically just an alt password.

I just generate a string of alphanumeric text from my password generator and stuff those in there. If I lose my password vault somehow I’m cooked anyway, so.

Worse still, the pattern does not continue like one would expect.

• Nominal: 2x4 – Actual: 1.5" x 3.5"
• Nominal: 2x6 – Actual: 1.5" x 5.5"
• Nominal: 2x8 – Actual: 1.5" x 7.25"
• Nominal: 2x10 – Actual: 1.5" x 9.25"
• Nominal: 2x12 – Actual: 1.5" x 11.25"

There’s just an arbitrary point where they decided to take an extra 1/4" bite out of it. I’m not sure whether that’s more of an effect of shrinkage from kiln drying being proportional to the original length or an effect of industry practice to mill smaller boards to eke out more cuts per tree.

And for the record, yes, I am aware the discrepancy is not entirely explained by shrinkage. They do a planing step after drying. But the shrinkage is a not insignificant part of it. They have to round down to the nearest convenient dimension from wherever the shrinkage stops.

If longer boards shrink more, the finished boards would necessarily have to be smaller. I question whether that’s the effect at play, though, because I believe there was a phase in the industry where that extra quarter inch wasn’t taken off, and they changed their minds about it later.

I wonder if it may well have gone down with the combination of boom in population and rapid urbanization around coasts.

This is somewhat a “people live in cities” graph, but not as stark of one I expected. Not all big cities are so educated, plus there are a lot of rural places that draw in a surprising number of people with advanced degrees.

Still, I’m amused that Interstate 29 in specific lights up like a string of Christmas lights.

I’ve yet to see any open lemm.ee prejudice anywhere. AFAIK it’s the largest completely inoffensive instance and that’s exactly what I was looking for.

What?

This is a discussion about televisions.

I got a 1U rack server for free from a local business that was upgrading their entire fleet. Would’ve been e-waste otherwise, so they were happy to dump it off on me. I was excited to experiment with it.

Until I got it home and found out it was as loud as a vacuum cleaner with all those fans. Oh, god no…

I was living with my parents at the time, and they had a basement I could stick it in where its noise pollution was minimal. I mounted it up to a LackRack.

Since moving out to a 1 bedroom apartment, I haven’t booted it. It’s just a 70 pound coffee table now. :/

can you burn a Luigi board?

I’m surprised I’ve yet to hear of a homebrew industry of completely cutting out the microcontrollers and soldering in a Pi or something to drive the raw display. I don’t predict it to be easy, but it doesn’t seem completely unobtainable?

Flashing a custom bootloader would be even better, but I assume that hasn’t been done because they got that shit cryptographically locked down at the chip level.

The first four of them are “just how floats work”, yeah. Has nothing to do with JavaScript.

typeof NaN
// "number"

Classic, yes, very funny. “NaN stands for ‘not a number’ but it says it’s a number”. But for real though. It’s still a variable that’s the Number type, but its contents happen to be invalid. It’s Not a (Valid) Number.

The next three are just classic floating point precision moments.

The Math.max() and Math.min() ones are interesting. Seems that under the hood, both methods implicitly have a fallback “number” that it compares to any argument list you give it that will auto-lose (or at closest, tie) with any other valid number you can possibly give it, so when you give it nothing at all, they leak out. Honestly, makes sense. Kinda ludicrous it needs to have defined behavior for a zero-argument call in the first place. But JS is one of those silly languages that lets you stuff in or omit as many arguments as you want with no consequences, function signature be damned. So as long as that paradigm exists, the zero-argument case probably ought to do something, and IMO this isn’t the worst choice.

Every other one is bog standard truthy/type coercion shitlery. A demonstration of why implicit type coercion as a language feature is stupid.

I think the phrasing they wanted was “The person with the least disincentive to do the ethical thing”.

These people aren’t inherently more ethical. They simply have the fewest barriers standing in the way of turning it into action.

Technically all you need is a DNS server.

No computer knows where <whatever.tld> is located, unless that route is hard-coded in a host file somewhere. It always has to ask a DNS server for that information. If that DNS server doesn’t know, it will probably try asking some other DNS server, and so on up a chain. Eventually, it reaches a master DNS server that either has the answer on-hand somewhere in a database, or it says, “lmao, that doesn’t exist”. All the DNS servers and your PC down the chain take that answer. They might memorize it for a little while and hand it out to anyone who asks them, but after a while they’ll ask their way up the chain again to see if the answer has changed since the last time they asked.

In order to “create” a TLD, all you have to do is make a DNS server that doesn’t ask up the chain. Just pre-program the list of valid domains yourself. You can make them anything you want. You can even “steal” existing domains and make them point to anywhere you want. Nothing is stopping you. Your DNS server will confidently report its pre-programmed answers to anyone who asks.

The catch is that any Internet-enabled device that you want to be able to use your fancy new custom domains needs to be configured to ask your DNS server in particular. People would have to manually set your DNS server as their master server to ask, or they’d have to set it to ask some other DNS server that is itself pointed through some chain up to your DNS server. This is an explicitly opt-in system, and getting a significant mass of people to do that voluntarily is practically impossible. But it’s not technically impossible.

The only reason you don’t have to do this manually with every single device you buy is because most devices either come from the manufacturer with a hard-coded list of DNS servers they should trust by default, or a device on the local network whispers in their ear and tells them who the local DNS server is and the device just goes along with it. It’s still technically an opt-in system; devices are simply either already “pre-opted in”, or there’s a system running on your network that auto-opts-in every device that connects, and most devices are designed to accept that auto-opt-in the moment they detect it.

Provided you manage to get the devices you want to listen to your DNS server, you may additionally want to set up a root certificate authority. The thing that makes the little padlock show up in your browser URL box to let you know the connection is secure. Kind of like the DNS server thing, this is also very simple–just run a cheeky little OpenSSL command or two and you can be a root CA in no time–but it suffers from the same “opt-in” problem. You have to manually configure any device you want to use your system to trust your certificates. Most devices just come with a list of “acceptable authorities” built-in, and those defaults are all most people are using. But nothing is stopping you from adding anything you want to that list at any time. You’re just limited to doing it on a device-by-device basis.

At my company, we’ve set up our own custom DNS server and our own root CA. We serve internal websites at a custom TLD we made up, and we sign them with our custom certificates to keep the connections secure. But that only works because we’ve manually configured our workstations to ask our internal DNS server for DNS requests, and we’ve manually configured all the workstations to trust our root certificate authority. A random device that connects to our network that isn’t configured with either of those things will not resolve any of our custom domains, nor will it securely connect to them. It also breaks if the configured devices aren’t on the local company network, since the DNS server isn’t reachable from the public web. Which is fine for us, since those internal websites aren’t reachable on the public web either. But yeah, that’s an example of the limitations.

If you want to create a TLD that will be auto-accepted by everyone who is already running the default chains of trust (which is probably what most people actually mean when they ask something like this), you have to seek out the big daddy at the root of that chain of trust and ask them to poof your TLD into existence for you. That would be ICANN, and they probably won’t do anything like that without a big fat check and a lot of corporate lobbying.

tl;dr - The tech is built in such a way that nothing is stopping you from making your own toy, and anyone can play with your toy without needing to do much. But if you want your TLD to “just work” for everyone in the world without asking every single one of them to explicitly opt-in, which is probably what you actually want, then no, you basically can’t do that.

As for memory management, macOS is the better option due to its fully integrated virtual memory system which is often on and continuously provides addressable space up to 4 per process.

Wow, 4 whole memories per process?!

Rinse aid is what we call a surfactant. It disrupts the surface tension of water, which in turn lessens its ability to cling to surfaces.

You know how when you get a smooth surface of glass or plastic wet, there will be a lot of beads of water that just cling there and don’t go anywhere? Unless they grow big enough to start finally running down the side? That’s surface tension in action. Adding the rinse aid will reduce water’s ability to bead up like this on dishes. Instead, water will be more likely to run down the surface in unbroken sheets instead of beading up.

The primary intent is that more water will simply drip off the dishes due to gravity. This does make dishes come out dryer after a drying cycle, and/or decreases the time the drying cycle takes or the energy it requires to get the same effect. But the main reason wanting water to drip off of dishes is to prevent limescale on them.

When water evaporates, only the water disappears into the air. Anything that was dissolved in that water gets left behind. If your water is hard, that will mean there’s a bunch of calcites that will stay behind as a whitish powder called limescale. So if you wash dishes with hard water, let the rinse water stay beaded up on them, and dry it out via only evaporation, you get some limescale buildup on them in the form of so-called “water spots”.

If instead you add rinse aid, more of the water will drip off the dishes, taking all the dissolved calcites with it. Less water has to evaporate, fewer calcites are left behind on the dishes, so less limescale and fewer water spots. Thus why many brands of the stuff show photos of crystal-clear glass on the box. A water-spotted glass will be cloudy and speckled. Rinse-aided glass will–supposedly, anyway–be clearer.