lmz

Pointers were smaller back then.

Why would Scheme be more likely to lead to bytecode than JS?

You're just moving the expensive part around for all these things. And something tells me someone who rails against a "computerized remote control" won't be thrilled with an app being required.

Because mechanical keys are not a good enough security measure.

The idea of a control system requesting a port forward rule using NAT-PMP is itself rather questionable.

Just makes sense that they would put the "heavy hitters" on feature development, not backporting security patches.

command.com also has variables. Syntax not so great though.

Good for them. I assume this is the will of the French people and they are proud of it just like our EU friends here are quite fond of the GDPR.

Good for them if it's the Norks. Wonderful to see the underdog come out on top every now and then.

The weird casing seems to be a minimum accepted prefix for the keywords.

They seem to produce no surplus if they take UBI and just stimulate themselves in VR all day. Maybe I'm too pre-post-scarcity to understand.

Usually the desire is for some of the metadata processing to be reusable between the encrypted and non encrypted formats ("like a regular file, just this data is encrypted"). This is also why eg. Zip files are encrypted per entry, not globally.

Since the kind of data people want available may differ for each file format, here we are.

If the humans have no economic utility and just collect UBI, how long until the computer decides to simply stop them from breeding (and bleeding it dry)?

The comments and field names in the source code are all Dutch. Expected I guess given the context, just wonder if that was generated or if it was derived from the compiled code. I know Delphi has RTTI info.

Ukraine used to be the USSR too.

We could call the final phase a coLLMpiler for good measure.

Well they could output plan.md files that are architecture independent first. Then we can commit those, and only generate the final machine code on demand.

Having the debits move to the new IBAN automatically had to be mandated and built. It doesn't just happen. In markets with large incumbent banks they have no incentive whatsoever to make switching easy.

Imagine the problem that required virtualenvs (or containers). Distro packages don't work well with that. Plus the packages are already outdated most of the time. Unless by "distro package" you mean packaging an entire environment as a distro package, but you'd run into the same problems of multiple installs there.

They're selling whatever the "Certificate of Embodied Production" is. You can tell the article veers towards the abstract around there.

Yes, and they cheered when the power was aligned with them to deplatform the opposition.

That would make it extractable and syncable to other hosts. That's fine if that's what you want but it's an important distinction.

Because the thread: "a lot of non-browser software doesn't check CT logs", you replied saying it's a reason to use the OS trust store, not sure how that fixes things? Maybe it would relieve them of the responsibility of pushing out a distrust update?

The CT log is a property of the individual leaf certificate not a property of the issuing chain. You could have the same CA in the trust store issue an unlogged certificate and non browsers would trust it.

The terms of service document (that all users claim to have read and understood) is obliged to explain rights. The chatbot is not.

X.509v3 just has one issuer Name in the certificate, unless you're talking about something else?

I'm pretty sure the Flash games were quite appealing to the users. The Flash navigation rollovers, restaurant menus -- I'm glad we're rid of those.

> a merciful immigration policy.

In the context of a potential civil war, isn't this basically just importing foreign combatants?

> this was the only widely supported way to pull in shared bits of HTML like headers, navigation, and footers without anything dynamic on either end

Framesets. Not great UI though.