This ban probably comes as a response to this activist project by the Peng! collective: https://pen.gg/campaign/mask-id-2/ where they used morphed portraits for passports.
So if I understand correctly, the kind of attack enabled by this manipulation is to provide a way for non-passport holders to pass custom controls by using the legitimate passport of the person they morphed their picture with. Is there any other useful kind of attack possible with this scheme?
>Such manipulation of photos is typically invisible to the human eye, the researchers found.
I think its more like attacking a machine learning model - the difference in the photos may not be apparent at all, so a human reviewer might not catch something.
That is unlikely. Germany can't get enough from "non-integrating gap countries"-immigrants. They have the reputation of integrating really well into western society.
Julia is built around multiple dispatch - when making a call, the method to execute is chosen based on the run-time types of all of the arguments.
Once this choice has been made, Julia compiles the method, specialised for the exact types of the arguments.
So, the dispatch process and the JIT compiler are linked - both are reliant on type information every time a function is called.
This specialisation is the only way the Julia JIT uses runtime type information. Unlike JavaScript JITs, Julia does not track things like the types of local variables during execution (although it may do some static inference). Therefore type annotations for local variables can improve performance.
Mostly spot on, although it's very rare for local variables to require type annotation—type inference can easily figure it out for locals. Unless, of course, they are assigned from an untyped external source the compiler couldn't possibly know. You could, for example read something from a JSON source knowing that it should be an number, annotate it with `json["field"]::Float64` and then the compiler will emit code to check the type and throw an error unless the type is actually a Float64.
You actually don't need explicit types in function parameters unless you're trying to control dispatching. Otherwise the compiler will auto-specialize on call. This blog post might be a better explanation on when it's necessary: https://www.stochasticlifestyle.com/type-dispatch-design-pos...
pansa had a great answer so I will just add to that. Multiple dispatch is rare among programming languages and the few which do it only has it as an add-on.
I believe Julia is the only programming language where multiple dispatch is the way all function calls work. There are no exceptions. It is also the only language where it was used to aid a JIT compiler.
Once you dig into multiple dispatch and see how it affects everything from performance to Julia package design and how packages integrate with each other, you will just be blown away.
It is hard to convey how ingenious this solution is. Even the creators themselves have admitted they did not realize how clever this would end up being. They only realized after people started actively using Julia what a gold mine they had hit.
Where's the Windows or Linux version of Xcode 7, then? Or a version of OSX licensed to run on the capable hardware that I already own? I suppose I could spend $500 on a Mac Mini, but then we're back to tokenizerrr's question.
Oh? Where do I find the docs and the download link? It has to run on Linux laptop or my Windows desktop, both which have perfectly capable hardware. I am not buying a Mac for the privilege of developing software for an iPhone.
A Hackintosh is perfectly viable. Assuming you can boot the installer(free from the Mac App Store), it's trivial to set up the necessary bootloader and extensions(certainly easier that making Windows dual boot nicely).
I guess Scala being "the most expressive typed language on the JVM" is true in the sense that it has a ton of features (OOP, FP, Exceptions, null Java backwards compatibility, etc.), but that's just too many features for a coherent language.
It's funny that both java & c# seem to be picking up many scala features in their latest & future versions like traits, lambdas, tuples, pattern matching, case classes, closed hierarchies, declarative generics...
Your language isn't incoherent if you can build features on top of each other with is exactly what scala does.
