Jarkko Sakkinen
Posts
4534Following
316Followers
479OpenPGP: 3AB05486C7752FE1
@AndreasBackx Don't get me wrong. I appreciate your comments. interesting topic.
For sudo, I think it would make sense to me in the case, if the upstream project would start to rewrite itself in Rust similarly as kernel is rewriting itself in Rust. Security is more a process than a tool.
For sudo, I think it would make sense to me in the case, if the upstream project would start to rewrite itself in Rust similarly as kernel is rewriting itself in Rust. Security is more a process than a tool.
0
0
1
Jarkko Sakkinen
jarkko
@AndreasBackx This sort of makes me think if I should just switch back to GNU ls...
Considering sudo-like command the more important factor is committed and experienced maintainers than implementation language tbh.
I mean this is just stupid: https://github.com/ogham/exa/issues/1243
With bat I think I live on the edge... Syntax highlighted source code dump is useful enough.
Considering sudo-like command the more important factor is committed and experienced maintainers than implementation language tbh.
I mean this is just stupid: https://github.com/ogham/exa/issues/1243
With bat I think I live on the edge... Syntax highlighted source code dump is useful enough.
2
0
0
Jarkko Sakkinen
jarkko
@AndreasBackx True, there's exceptions to the rule. I use exa and bat [1] :-) How do exa and eza differ anyway?
[1] https://github.com/jarkkojs/home/blob/main/.bashrc
[1] https://github.com/jarkkojs/home/blob/main/.bashrc
1
0
0
I mean factors larger binaries with non-standard output, and you really have limited use for the added fanciness. They are only great at breaking backwards compatibility, if you put them into scripts.
This does not mean that Rust in command-line sucks in general. I think tools such as Starship and Typst are just great. They invent.
This does not mean that Rust in command-line sucks in general. I think tools such as Starship and Typst are just great. They invent.
0
0
2
@lari @hiljaisuus Mä oon tienannut open sourcella sen verran, että se on riittänyt monta vuotta putkeen verokoneisiin, ja maksanut paljon veroja myös.
Se ei vituta, koska teen asioita mitä tekisin vaikka sossun asiakkaana, mutta mun mielestä siinä on joku epäsuhta, että Internetin infrastruktuurin kehittämisestä verotetaan rankemmin kuin vaikkapa some-influensseria, joka kiertää verot holding-yhtiön kautta.
Verotuksessa tuntuu epäreilulta, ei mikään tietty prosentti, vaan että aktiivisuus on kaikista raskaimmin verotettua, ja passiivisuus vähiten (esim. pääoman verottaminen). Ne voisi olla edes samalla viivalla.
Se ei vituta, koska teen asioita mitä tekisin vaikka sossun asiakkaana, mutta mun mielestä siinä on joku epäsuhta, että Internetin infrastruktuurin kehittämisestä verotetaan rankemmin kuin vaikkapa some-influensseria, joka kiertää verot holding-yhtiön kautta.
Verotuksessa tuntuu epäreilulta, ei mikään tietty prosentti, vaan että aktiivisuus on kaikista raskaimmin verotettua, ja passiivisuus vähiten (esim. pääoman verottaminen). Ne voisi olla edes samalla viivalla.
1
0
12
75% time went to exclusion, i.e. finding that the bug is in the enclave itself, not in kernel, SDK or the security monitor. Last two weeks was peeking and poking with loader.S. I even wrote a new driver for Keystone in the process so that I could exclude the driver (OTT driver is, well, I don’t want to say anything impolite…).
1
0
1
Jarkko Sakkinen
jarkko
Edited 1 year ago
I nailed the Keystone SATP change bug on CVA6 after only 1.5 months of constant debugging:
1
0
1
Jarkko Sakkinen
jarkko
"Sometimes smart thinkers just don’t know when to stop, and they create these absurd, all-encompassing, high-level pictures of the universe that are all good and fine, but don’t actually mean anything at all."
Is this a description of Haskell or NixOS? I'm sorry, a bad joke. Please don't get upset.
https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/
Is this a description of Haskell or NixOS? I'm sorry, a bad joke. Please don't get upset.
https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/
0
0
1
@suihkulokki To add, Pentium had two instruction pipelines that you wanted to keep busy so ordering opcodes correctly was super important, and compilers were not that great giving the best results, so all had to be done in hand-written assembly.
0
0
1
@suihkulokki
"with PHONG shading no less, metal shading, phong env mapping" -from one comment.
Tbh, all phong shading was just the standard environment mapping trick (you precalculate the light to 2D texture) that everyone was using during that time but still impressive work. I know this for a fact because I've talked to some members of the group (complex is from my birth town).
There's one trick that not that many knew at that time, and also one of the first ways I learned how you can do *data* cache optimization for profit. Before Pentium, all the focus was mostly on instruction pipeline.
When you have a 2D texture of pow2 size, you partition it into 8x8 tiles with one byte per pixel (VGA was 320x200 8-bit framebuffer), i.e. do this sort of precalculation step instead of directly interpolating the original texture. This on average takes away a lot of cache misses even tho adds a bit of complexity to the inner loop. 8x8 tile is a great fit for Pentium cache lines.
On instruction cache you of course similarly make your inner loop fit nicely to the cache line and order instruction dependencies so that the dependencies between opcodes are minimal and you get maximal throughput out of the CPU.
Pentium sort of started the era of memory optimization. Now most if not all optimization of code is a caching exercise...
"with PHONG shading no less, metal shading, phong env mapping" -from one comment.
Tbh, all phong shading was just the standard environment mapping trick (you precalculate the light to 2D texture) that everyone was using during that time but still impressive work. I know this for a fact because I've talked to some members of the group (complex is from my birth town).
There's one trick that not that many knew at that time, and also one of the first ways I learned how you can do *data* cache optimization for profit. Before Pentium, all the focus was mostly on instruction pipeline.
When you have a 2D texture of pow2 size, you partition it into 8x8 tiles with one byte per pixel (VGA was 320x200 8-bit framebuffer), i.e. do this sort of precalculation step instead of directly interpolating the original texture. This on average takes away a lot of cache misses even tho adds a bit of complexity to the inner loop. 8x8 tile is a great fit for Pentium cache lines.
On instruction cache you of course similarly make your inner loop fit nicely to the cache line and order instruction dependencies so that the dependencies between opcodes are minimal and you get maximal throughput out of the CPU.
Pentium sort of started the era of memory optimization. Now most if not all optimization of code is a caching exercise...
1
0
2
@suihkulokki BTW, Jugi's track never gets old... What a great tune.
0
0
0
@suihkulokki And not having that weak and distorted sound that Sound Blaster provided and my friends with Amiga's were picking on me :-) Still remember watching DOPE for the first time with proper sound (also demonstrated on that page): https://www.youtube.com/watch?v=HtXxM0pezAs
2
0
1
Jarkko Sakkinen
jarkko
I still regret selling my Gravis Ultrasound MAX. I might buy one of these some day. It is amazing achievement. Before GUS Amiga sounded so much better than any of the Sound Blaster crap hardware with its 8-bit DACs. GUS was a game changer in the 90s. https://www.tindie.com/products/kdehl/gravis-ultrasound-gus-pnp-replica/
1
0
1
@slink E.g. for reviewing upstream patches it is pretty lousy user experience. So yes, you are correct that you can send email as plain text but it does not treat plain text too well, if plain text is your main thing, and HTML email is a 2nd class citizen.
0
0
1