grodriguez100

Or 386K requests per seconds, depending on where these billions are coming from :-)

And also because historically iPhone users have been more inclined to pay for apps than Android users.

The original Pixel Dungeon uses a homebrew “engine” (that’s the PD-classes stuff). Shattered uses libgdx.

Yes, you are right. The pricing page is confusing and it does not explain clearly that all the paid plans are not needed for ACME stuff.

I am not sure if this is an oversight or done on purpose..

Yes it does offer free wildcard certs (for ACME); see: https://zerossl.com/documentation/acme/

“By using ZeroSSL's ACME feature, you will be able to generate an unlimited amount of 90-day SSL certificates at no charge, also supporting multi-domain certificates *and wildcards*. Each certificate you create will be stored in your ZeroSSL account.”

I'm curious, if the Android issue does not apply to you, why are you looking for alternatives to LE ?

> One of the fixes this release is untrainable SIGKILLs programs for illegal memory accesses, which is a perfectly boring and sensible security practice

The signal raised for page faults should be (and actually was, before 14.4) SIGSEGV, and not SIGKILL. This behaviour is even defined by POSIX.

There is no reason why this should change, specially not in the final release instead of in the public betas and early access releases (where the change was not present).

> Some of these problems could be a de-emphasis on the Intel experience.

Unlikely since several of the issues seem to happen only on Apple Silicon.

Uhm, yes, you are right.

I don't think the EU DMA changes will require that JIT is supported. Supporting alternative browser engines is something that can be done perfectly without JIT.

Yes, Apple had their own Java runtime in the past, but this was discontinued. I think Mojave (10.14) was the first version without official Java support from Apple.

I find it difficult to imagine how a change like this (sending a SIGKILL to the process instead of SIGSEGV on a page fault) can be done in the final release and not in one of the EA releases or betas. It is clearly a breaking change with no easy workaround (since SIGKILL cannot be caught), for a behaviour which is well defined by POSIX.

Even if you momentarily ignore the reasons why someone thought this could be a good idea, why not do it in one of the pre-releases or betas??? Doesn’t look like the kind of thing you’d want to do in a last minute change.

The real problem in my opinion is the fact that you cannot go back after a macOS upgrade. So if something like this happens, you literally have no option but waiting for Apple to release a fix, if they want to do it at all.

“The problem does not affect most typical Mac users, as Java was deprecated for the Mac back in 2012.”

This is misleading. What was deprecated was the browser Java plug-in distributed by Apple. That’s very different from “deprecating Java”.

There is no “special treatment for Java”. This is a well known technique that has been used for ages in the implementation of JITs. The behavior it relies on is specified by POSIX.

That xkcd comic was the first thing that came to mind as well.

The article explains how Base64 is “problematic because it has more than a dozen variants”. So instead of picking one, let’s invent a new standard.

Yes, I know.

In Spanish we say that a day is “largo” (long), not “full”, in the same sense as in English.

However 14.4 was released days ago (March 7).

The article says that the issue “is affecting all Java versions from Java 8 to the early access builds of JDK 22” now.

> I’m assuming it’s not common as you would expect it to have come up during betas and pre -release seeds.

The article specifically says that the issue was not present in early access releases, so it was not possible to discover it before the actual release.

Thank you for educating me. Obviously your insightful comments don’t waste anyone’s time.

What’s wrong with making a comment? It’s not like there’s a limited supply of them. If you don’t find a comment interesting you can just ignore it, no harm done.

Nitpicking, but “the game creation tool I have been working on for the past few years” and “I started it […] in October 2022” don’t combine very well.

Thanks!

How did you do this? I mean the combination of prose and code samples. I would love to see more.

> I think this is mostly right - "superset" in that JSR modules can depend on npm modules

This is not what most people would think when a registry is said to be a “superset” of another.

> Even though Linux filesystems are generally case insensitive

Linux filesystems are generally case sensitive.

I think the point is that he thought it was too late in 1985, then people thought the same ten years later (1996), then the original article (from 2014) tries to explain how 2014 is not too late either (“the best time is now”).

In other words, it is always easy to think it is too late when looking back. But it is never too late if we try to look forward and imagine the things that have not invented yet and which will be around in 10-20 years time.

Being diagnosed should not prevent you from making an advance directive as long as you are in full possession of your mental faculties. That’s how it works in Spain at least. In certain cases this may involve a medical evaluation.

In Spain this is possible. It is called “testamento vital” or “documento de voluntades anticipadas”, and the goal is just that: to declare, in a legally binding way, your wish to receive or not receive certain kinds of medical treatments in the future, in case you can no longer decide when the time comes. This includes euthanasia in cases where it is legally allowed. Alzheimer is one of such cases.