stefano

> three to seven transactions per second, but with a centralized trusted entity

The byzantine generals problem doesn't apply when you have trusted entities.

Depending on your age and how much you can deduct, the switch over can come as "low" as 90k. At 100k you should always be ahead in any case. And that's without counting the social security contributions. Depending on how you value them, it might be more convenient even under <90k.

Taxes at that income level are around 50%, including ~20k worth of social security contributions. You're probably mixing up VAT, advance payments and final balance payments to get to that 76%, which is NOT what you're really paying on your income, unless your accountant made some major mistake.

BTW, if you invoiced 65k instead of 80k, you could use the "forfettario" tax regimen, which would result in a higher net income (yes, it's that crazy: you earn more if you earn less).

Fourth option: don't introduce this change at all. It's a debatable stylistic improvement in exchange for a big breaking change that will force your users to go through, update and re-test every single query. Not worth it.

How do you guarantee it doesn't copy a GPL-ed function line-by-line?

Maybe if it comes with clauses for a substantial transfer of technology to EU partners. But I doubt Intel would agree to that.

As an alternative to SPID you can also use your national electronic ID card, which is issued by the state without the involvement of private companies.

Same. The only issue I had with virtualenv was when I copied one to a different directory and it didn't work. It turns out you can't do that. Everything else has always worked fine, and I've been using it professionally for 10 years.

Sanofi will be producing the Pfizer-Biontech vaccine, but it takes a lot of time to set up a new production line. Last estimate I saw was saying July.

This is very true. Just importing Django + Django Rest Framework + some other minor libraries in Google App Engine (standard) leads to painfully slow response times when a new instance spins up. Like, more than 10s to spin up an instance. Although App Engine seems to be 3-4 times slower than my desktop computer from 2014 on this particular task. I wonder if AWS lambda is better.

Having implemented a threaded Forth with WASM, the most annoying problem is that WASM doesn't support jumps to arbitrary memory locations. You can either call functions (and you don't have access to the call stack), jump backward to a previously defined block entry point or jump forward to the end of a previously defined block. Threading then requires a double indirection in the core loop, and you have to use an explicit IP "register" in a global variable.

The premium is actually higher than that. For $100, the developer gets $70. Which means the premium is $30 on a $70 base price, i.e. a ~42% higher price. That's a very steep price for easier payment cancellation.

It was a problem only because somehow they decided that type annotations should evaluate to something meaningful at runtime, instead of being a compile-time only construct like in every other language.