time to #detox #twitter. i created account last year because i was working in a startup. now there is no pragmatic use, and you know how it is like over there. sad.

@vbabka there is this bluff among extremist that they spread that being liberal means that you have to like every type of weird shit that people do. no you don’t. you can even find it disgusting. it’s totally cool. the point is pretty simple in the end: mind you own business and let it be.

@vbabka also if i take the word from trolls i learned that my political stance is neonazi-stalinist-woke. have to check which party supports this type of politics!

@vbabka it was collaboration, i did only my part, cannot take full credit :-) i mean at intel most of my colleagues were from other countries. so i felt that i supported my ex-colleagues in the corporate world! for instance, i felt that colleagues with russia nationality would be target for this type of unhealthy management.

s/today/weekend/g

#elonmusk #paradox: one can have #money as much as a state but zero unallocated time units. in a sense, it is ultimate #poverty.

@vbabka good to hear, international news prove that i was doing the right thing.

i.e. i would never post anything about politics to lkml. just wanted to underline this because this is edge/corner case.

and this has zero to do with any politics, i did read the full code of conduct before saying anything but i also need a reason for delay. it is was about liability. i don't really care about politics that much at all.

One idea for #chatgpt and alike would be generation of #legacy #bindings for codebases where any #automatic method will not work, and creating bindings is trivial but manual work.

doing PR today...

never get involved in politics... unless there's a neo-nazi in the government 🤦

Lagging #LKML a bit, and also a bit late with my PR because I've been helping to expose a neo-nazi minister. Cannot believe this could ever happened in #Finland @torvalds

@esoterra thank you :-) i really appreciated your feedback. i have zero use for supporting feedfback for a draft like this because that never has refined anything...

@esoterra i get that but that's not really an unsolvable technical problem (sorry not back up for this claim at this point but it was great point, thanks).

@esoterra why i do such dumps here is that this type of stuff can start shift away your main focus, this way i can kind of sharpen it. and i don't mind being totally wrong on internet :-) that has been my main job for many many years anyway.... maybe i start to use #braindump hash tag for these to make it more obvious.

@esoterra we can agree to disagree at this point (for now) :-) I don't like it but if it works for most all cool. Web is not my main territory, or something I would get paid for the moment (I'm extending kernel atm to have user space vtpm drivers and wrote in-kernel RISC-V Keystone driver) but your comments motivate at least to refine the text one day!

@esoterra any feedback to this thread is welcome (and appreciated) but i don't promise to answer it but if i rework on this, then i will try to address it better. thank you...

this does not disqualify wasm but it is not a design, it is evolution of asm.js. this type of agile/evolutional self-directing model is great for most of the web but for any ABI it is not how you should do it. I could bet money that if things were done from clean slate, we would have something that would not be wasm, even if the end solution would not be riscv. subsetting extensions and layers.

If one can accept that premise, the 2nd premise would be to show that RISC-V "can do it " (even if it sucked). I think this can be made to work.

So 3rd thing to show is that it would be optimal, or more look like "good enough", and objectively better than wasm.

This is roughly how I would start to break up and structure it to a more whitepaperish form....

@esoterra at this point is just a dump with no emphasis to sell it. i just wanted it written down somewhere but i do appreciate your comment because that gives input to refine it possibly in future. frankly, i don't believe this could happen because W3C is too conservative industry body so not a focus point.

i think i already gave some thoughts on some things that you asked but obviously it is my fault (not yours) if it did not get through, i.e. my comms sucks.

so yeah, sorry for dissatisfying answer. i just hate when i loose some idea and mastodon is pretty good to put unconstructive and unfinished ideas :-) I'm sorry for not liking wasm but I stick to that unforutantely without proper study for now,...

I’ve hacked on RISCV for 3,5 months, and some thoughts have developed.

I think that #WebAssembly was a wrong design choice for #web and instead #W3C should have gone with a real micro architecture. #RISCV provides answer for this.

Benefits:

1. Wider than web industry behind it.
2. Made to last decades without breaking backwards compatibility.
3. Ultra-light state transformations (context switches and alike).
4. Well-defined layering and extensions.
5. More open and appealing to open source hackers, moving power away from industry controlled WG’s.
6. Catch up game with many CPU features would stay in sync. E.g. for VM based (i.e. not like SGX which is process based) confidential computing could just map the primitives for the underlying bare-metal CPU architecture.

WebAssembly is in the end really bad implementation of a great idea overally. Forth i interpreter was cool when JVM came out.

Here if W3C and browser vendors dared to take step back, it would result a stable innovation in the web for decades forward.

Transforming RISC-V to WebAssembly is ofc possibly but I don’t see it as an end solution, as all the crappiness of #wasm gets in the way, and e.g. benefit 6 would not even exist.