That’s not how legal jurisdiction works in the EU. Member states are still sovereign; if you’re liable for something in France and you get off a plane in Germany then France still needs to ask Germany nicely, and sans an extraditable conviction nothing is likely to come of it.
He’s not smart enough. More like the Grand Negus.
So you’re a practiced expert and cannot understand how those who are not practiced experts can have trouble?
It does rather sound like proposing an immediate 25k hike in house prices, yeah.
Experience. For what it’s worth, the instinct I distrust is absolutism.
I think it’s like the distinction between art and obscenity; it’s not a nuanced distinction in the case in question. If it were, I’d largely trust UK courts to get it right (they are by-and-large capable of this, and much less politicised than their US counterparts).
I’m coming around to it.
I think unqualified freedom to say anything can lead to negative utility, pragmatically speaking. Malicious lies bring less than nothing to discourse.
I’m concerned that the libel system can be abused, of course; and I don’t approve of arresting octogenerians under the Prevention of Terrorism Act for shouting “nonsense!” at Jack Straw. But I don’t see there being a need to draw a distinction between online and in person speech, and I think that incitement to riot isn’t something I’d typically defend.
Having said that: I hope the woman in question (who has a history of being a deniable pot-stirrer) gets a trial rather than copping a plea, because the bounds of these things are worth testing.
That’s a cracking article.
My own use of jvm errors tends to follow the same kinds of patterns: I think the major fault with that model is having RuntimeException as a subclass of Exception, because it’s really intended for abandonment-style errors. (The problem is that lots of people use it instead as an exception system in order to cut down on boilerplate.)
I find it eye-opening that the author prefers callsite annotation with try
(although I’m not going to argue with their experience at the time). I can see this being either “no big deal” or even “a good thing” to Rust users in particular - mutability and borrowing annotations at both callsite and definition aren’t required to make the language work afaict (your ide will instantly carp if you miss 'em out) but the increased programmer visibility is typically seen as a good thing. (Perhaps this is down to people largely reviewing PRs in a browser, I dunno.) Certainly there’s tons of good food for thought there.
In which case, perhaps unqualified “freedom of speech” isn’t all it’s cracked up to be.
(I appreciate that Chomsky’s opinion resonates more with 1968 than now.)
Was at the time (as per usual).
Cf. previous comments about dogwhistles.
I’m not sure why it’s “obviously” good to move from one mechanism to two: as a user I now have to categorise every path to work out which is appropriate.
What I said was less about adding to a function signature than it was about adding to a facade - that is, a system boundary, although the implementation may be the same depending on language. People typically use exceptions pretty badly - a function signature with a baggage-train of internal exceptions that might be thrown by implementation guts is another antipattern that gives the approach a bad rep. Errors have types too (or they should have), and the typical exception constructor has a wrapper capability for good reason.
I think you’re spitting the situation on the wrong horn of Jefferson’s dilemma. They have the freedom to speak. It comes with the danger of being arrested if that speech meets the requirements of being an exhortation to violence.
I take it that you can see a distinction between “Vance fucks couches” and “burn those people in their hotel”. They are not the same thing.
If the distinction is hard to determine - that’s why there’s a judicial process.
That’s fine, and for that there are sum types. My own opinion differs - it’s a question of taste. Being able to bundle the handling of exceptional situations aside from the straight-line logic (or use RAIi-style cleanup) is notationally convenient.
Yes, you can do the same with monads; use the tools available to you.
Checked exceptions are powerful but misunderstood. Exception types are a useful part of the facade to a module - they express to a caller how it can go wrong even if used correctly.
Runtime exceptions are typically there to express contract-breaking by callers; although as an alternative return mechanism I’ve seen them used to simplify the inner workings of some frameworks.
I think they get a bad rep because there aren’t a ton of good examples of how to use them - even the java classpath had some egregious misuse initially that helped turn people off the key ideas.
Look up the original judgement on the Maya Forstater tribunal. “In a functioning democracy, some beliefs are not worthy of respect,” or words to that effect. If you think inciting racist riots shouldn’t be criminal, then write to your MP about it.
The way the electoral roll is managed varies from place to place.
Avoiding automatic voter registration tends to favour the more traditionally conservative demographic; it’s racist and classist, but the people who turn up to vote on local electoral issues are too, by and large. It requires engagement to change.