I have some old jekyll websites that I only very infrequently need to update. Each time something in the ruby / gem / bundler / jekyll chain setup is broken, and with some weird errors it is stackoverflow search time. Very time consuming, highly annoying. I postponed my last typo correction, to first make up my mind on whether to port to astro that I use currently.
The rayban metaglasshole comes to mind. Now its just journalists who fool people in the street with AI face recognition tricks, and its all still fun and games. But this is clearly a horror invention, merrily introduced by jolly zuck, boss of facelook.
Haha, I basically barged into here ready to post a video of Greyson. Amazing stuff, I'm surprised more people haven't been successful (or interested in) teaching their dogs ride stuff.
> Irdest is a networking research project that explores different technologies and ideas on how to build more sustainable, user-controlled communication networks.
I am confused. You are referring to wasm modules here? And Component Model / WASI / WIT will give us polyglot interface-based programming then, right? Call each other's methods through the WIT interface between components.
Even the component model has nothing to say about the concept of methods. All you have are top-level functions with immutable arguments and immutable results. You can't hold on to an instance of an object created by the other language. You could hold an integer handle, but then you don't get garbage collection across the two languages.
So no, we're still a long way from the abstractions of a JVM, even taking the component model into account.
It's a good step in the direction of better interoperability between languages, though, don't get me wrong.
For the audience that would be looking to use the WASM Component Model, and not be an infrastructure implementer of it, whether or not they meet some definition of a method, the component model does define things called resources [1] that have "methods". You'll hold a "handle" to it like you would in your own programming language with the expected drop and/or GC semantics (once implemented [2]) because code is generated to access it like any other FFI like C/C++.
With that in mind, the other confusing thing one may come across is composition vs linking within your WASM runtime that supports the Component Model. When you hear "composition" think of compile-time merging of libraries such that the bundle may have less unresolved dependencies of WASM code/implemented component interfaces. Anything unresolved needs to be linked at runtime with your WASM runtime of choice, like wasmtime [3]. Pretty interesting reading/potential after reading if you ask me -- sounds like you could implement something like a custom Java classloader hierarchy [4].
But I'd agree with a statement saying it is still a long way for general usage.
If the idea is to claim to be an escort that only accepts cash, and then report already-possessed cash as income, while also depositing into a bank, then that could have been phrased more clearly. As it stands, it says to actually be as escort and get more money that you have to launder.
Plus, there has got to be more critical information -- left out of the comment -- on how to get such a scheme to work. I highly doubt that most countries have left a massive hole in their anti-money-laundering systems that allows a person to simply claim to have massive transactions in cash with no (or easily fakeable) documentation.
Haha there's an episode of Better Call Saul where nerdy, middle-aged Dan is noticed by the authorities as spending far more than he earns, and he explains it away as being an escort for rich fetishists who like seeing him sit on pies.
