stefano

A politician wanted votes. To get votes, you need to lower taxes. But that requires money, which there isn't much to go around. So they picked a niche of people (freelancers earning less than 65k) and gave them a tax cut. Making it progressive (i.e. everyone pays 15% on the first 65k and then a higher tax rate on the rest) would either cost too much, or be too small of a cut to gain enough votes.

I'm not OP, but he's referring to the so-called "flat tax" for freelancers.

The limit is 65k. You pay 25% to the mandatory pension fund. Of the remaining, they assume 22% of expenses and tax you 15% on what's left. So you take home ~42k net after taxes. If he were to earn 65.001 euros, he'd take home ~32k net after taxes. You need to earn at least ~80k to break even. So if you earn between 65k and 80k, you're screwed. Needless to say, that 65k becomes a ceiling because if you get a raise, you start earning several thousands of euros less. So either you're stuck at 65k, or you bite the bullet and take the hit until you reach 80k, at which point you can start increasing your take home again. So a 1 euro increase gives you a -10k "raise", while a 15k increase gives you a 0 euros "raise".

It's probably the most stupid tax system in the developed world.

Where's the irony?

Yup. It's a 1080p monitor running at 1080p. I tried all the other available (non native) resolutions and fonts looked blurry in all of them.

Thanks, but I tried that some time ago. It didn't make much of a difference.

I tried. It didn't help, the root issue is that Apple removed anti-aliasing, which is the only thing that can make fonts look readable on a 1080p resolution display. An old MacBook running OSX 10.6 looks perfectly fine on my external monitor.

Thanks, but I already tried that in the past. I didn't notice any difference. Maybe it looks decent if you have a screen with high enough resolution, but ony my 1080p screen it still looks bad.

I had the same problem. I ended up downloading the xip archive from the developers center and installing that, bypassing the app store.

Regarding the first point, I had to give up on using an external monitor because fonts look blurry and give me a headache after a while. The same monitor with Windows and Linux shows perfectly fine fonts. I tried all sort of incantations found on forums, and nothing works.

The London stock exchange would be an obvious candidate.

Swift. Automatic reference counting still requires more developer attention (to break reference cycles) than a GC, but is still easy to get right. Too bad that outside of iOS development it's still unusable.

France and Germany are sovereign states, not businesses.

Did they improve the download size?

> That said, a lot of people say JavaScript is bad. And yet this language is one of the most popular one in the world.

The post is about the fact that just because something is popular, it doesn't necessarily mean it's good. The fact that JavaScript is popular cannot be used as proof that it's a good technology. It had a monopoly of the browser market for decades. If Netscape put COBOL there, everyone would be programming in COBOL today.

Most likely, they're both going to lose.

> reinventing research papers from 20+ years ago

The first(?) paper on type classes, "Parametric overloading in polymorphic programming languages", is from 1988, so they're reinventing things from at least 31 years ago. I guess in 2050 Go will catchup with today's state of the art.

> helps reveal its simple and elegant semantics

JS semantics are neither simple nor elegant. There's a reason there are whole books dedicated to avoiding certain parts of the language, and it's not the syntax.

For example, the syntax of the == operator is trivial. Its semantics however is complex and inelegant (it looks like an equality operator, but it doesn't express an equality relationship).

Does anyone here have experience on using Rust for shared business logic between Android and iOS? It's something I'm considering but it seems there isn't a lot of documentation around it.

> wasted space inside the allocator itself

If you're only allocating fixed-size cons cells, you won't run into fragmentation issues.

That privacy seems a bit overboard though. This is fine if a user can create his account directly inside the app. But it's not very clear how to support a workflow where you have an organization with multiple users authorized by an admin to use the app. How can the admin add a user to his organization, if he doesn't know in advance the user randomly generated email? I guess you could send an invitation code, and let the user enter that code after the apple sign in, to associate the account to the authorized user. This sounds more complex for the user than a workflow where the admin can directly authorize specific emails.

How does authorization (as opposed to authentication) work with apple sign in? With Google sign in you get an actual email that can be pre-authorized on the server. With this, the server only has a phony email to work with, so how can you match that phony email to authorized users?

It's pushing chinese firms to create an Android competitor. In the long term, this might hurt Google a lot.

You'd think people would learn from the 2to3 debacle.

> Surelly with a bit of backward compatibility sacrificed like 2 vs 3.

After 10 years, the 2to3 transition is still ongoing, and lots of companies will be dealing with python2 code for a long, long time. Breaking backward compatibility was a terrible decision. Breaking it again now that most libraries and open source projects have finally moved to python3 would be suicide.

Programming languages should take backward compatibility as one of their most important features, because of the hundreds of millions of lines of code already written and that would need to be changed and validated. This is especially true in a dynamic language where you can't even rely on the compiler to point out the issues.

> The primary problem was Java developers compiling code where they had no idea what the output was doing

Wasn't this the same argument made back in the day against C when comparing it to assembly?

But it's harder to install this, import it, and add a decorator than it is to type "breakpoint()".

Don't the Django ORM and Django Admin do the same thing?

Boilerplate is complexity.

You can also say that EU citizens mostly voted for the current EU parliament.