Posts
3931
Following
252
Followers
407
OpenPGP: 3AB05486C7752FE1

Jarkko Sakkinen

yhteiskunta toimis varmaan paremmin, jos ihmiset tykkäisi enemmän star trekistä kuin star warsista. sen sijaan, että tapeltaisiin pilotit tai huput päässä, niin juteltaisiin mukavia neutraaleissa kokovartalotrikoopuvuissa, ja 3D-tulostettais sitä mitä nyt sattuis tarviimaan. #startrek #starwars #yhteiskunta #society
1
0
0

Jarkko Sakkinen

0
0
0

Jarkko Sakkinen

closed my #linkedin, i've never needed it, and had account for the first time in 2003, so i guess it is useless...
1
0
1

Jarkko Sakkinen

a recent track with my friend kirna from a #nullzone compilation (also opening track for the compilation): https://nullzone2007.bandcamp.com/track/lumo-ava #psytrance #suomisaundi
0
0
0

Jarkko Sakkinen

https://www.msxgoto40.com/en/news/msx3-to-be-presented-at-goto40/ #msx #msx3 interesting development, i've always hated these office computers, and miss the home computers :-)
0
0
0

Jarkko Sakkinen

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.
0
0
0

Jarkko Sakkinen

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

Jarkko Sakkinen

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.
0
0
0

Jarkko Sakkinen

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
1
0
2

Jarkko Sakkinen

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.

2
0
3

Jarkko Sakkinen

#notetomyself `curl -sS https://starship.rs/install.sh | sh -s -- -h` (tested on #linux and #macos)
0
0
0

Jarkko Sakkinen

#remindertomyself #git:

git submodule foreach --recursive git reset --hard
git submodule foreach --recursive git clean -f -d -x
0
0
1

Jarkko Sakkinen

I don’t like the policy of #buildroot in that you have to subscribe to the mailing list, in order to be able to send bug fixes. Not possible, when you try to proactively limit the incoming #email flow to the minimum.

0
0
0

Jarkko Sakkinen

a cosmetic #bug in #git:

suppilovahvero in keystone on  jarkkojs/spirs via △ v3.25.1
$ git add ../keystone/patches/linux/linux.vtpm.patch
fatal: ../keystone/patches/linux/linux.vtpm.patch: '../keystone/patches/linux/linux.vtpm.patch' is outside repository at '/home/jarkko/work/nisec/spirs/keystone'
1
0
0

Jarkko Sakkinen

#ctags and/or #cscope are tbh better options for browsing #kernel than #clangd because two former ignore kernel config/build when scanning for new tags. perhaps get_compile_commands.py could be improved a bit. #linux
0
0
0

Jarkko Sakkinen

Edited 1 year ago

#remindertomyself when editing #email with #aerc use CTRL-j and CTRL-k to move between header fields and the message body. I’ve got stuck to the CC list a few times and have sorted it out by killing the whole process, so this is definitely an improvement :-)

The key for finding out how to fix this was man aerc-tutorial. I was cursing for a while because man aerc was not giving me the answers, until I realized that there is another man page!

0
1
1

Jarkko Sakkinen

#notetomyself on #macos:

defaults write -g NSWindowShouldDragOnGesture -bool true 
0
0
0
Show older