Hmm, you think it's clear cut that people in the US shouldn't be allowed to read whatever official statements the new government of Afghanistan decides to release? Or do you mean something different?
No, I mean it's clear cut that it's a terrorist organization. I'm the kind of person to think people should read Mein Kampf and the little red book in order to understand history, I won't argue we should prevent people to have access to knowledge.
But I get one company may want to avoid being the one hosting it.
Oh, I agree, though I have to admit I haven't read either of those.
Note, though, that the correct idea you expressed that the Taliban are a terrorist organization would be self-contradictory to anyone who defines terrorism ahistorically as non-state or unlawful violence to achieve political aims, since now the Taliban are the Afghan state and are legalizing their terrorism.
> Hosting the websites of terrorist groups is something few people would advocate
The problem is not to remove those, the problem is to do that outside of a proper legal process.
Because it's easy to say "yeah, ISIS are terrorists, remove their forum", but the word "terrorist" has been abused to much you pretty much guaranteed it's going to be the justification to remove "content we don't like".
Agreed, it's very heavy for no reason given it's doing pretty much nothing. It's buggy, slow, sluggish at times, with delay on clicks and scroll. It's really a terrible UI given how simple the problem is, and how much money they got.
It's not like they have 1000 of concurrent events like facebook, and their frontend should have nowhere the complexity of their backend. I don't understand how it's even happening.
The most absurd aspect of it is that how slow loading a single tweet is. The timeline could have the excuse of a slow and complicated backend call (but it doesn't, the backend is actually doing ok), but several seconds for one single tweet?
Which probably works by stapling bytecode to a precompiled interpreter. A tried and true strategy, but not necessarily what people want when asking for AOT compilation.
It's only a few steps away from what Graal/Truffle do: unroll the interpreter loop over the bytecode, then keep re-running dead code elimination and inlining passes - you end up with something very close to optimized native output.
Not an installer no. The installer part is not provided, the result is an executable that works out of the box. The installer would then take that and put it somewhere, but you don't need to. It can even work from a USB key.
nuitka takes your python code and all its deps, turns it to c code, and compiles that into a standalone executable that is both faster and doesn't need a separate python vm to be installed.
Expect it does require libpython and at least on Ubuntu 20.04 it links against the dev version of the library. So not only can you not run the resulting binary on any random Ubuntu 20.04 you also need to install same version of the python and the "-dev" version.
I did try this. With the "stock" python3 (3.8.something) I couldn't get nuitka to compile my code (or the example from the docs). With python3.9 I could start the compilation, but I didn't have libpython-dev shared object and finally with python3.9-dev I was able to make the binary. However after transfering it to another Ubuntu 20.04 machine I couldn't run it since it was linked against libpython3.9-dev.
Just as side note. The same python code (i.e. the .py file) would run on both machines out of the box.
And of course, one day, it will be abused.