Posts
4457
Following
315
Followers
470
Linux kernel hacker and maintainer etc.

OpenPGP: 3AB05486C7752FE1

Jarkko Sakkinen

I learned over the weekend (I was at a local #rustlang meetup) that interrupt controller caps #riscv for competing with #ARM on real-time tasks. I also learned about #CLIC. Just wondering are there any other extensions making waves or is CLIC where the world is converging.

More information:
https://ieeexplore.ieee.org/document/9660345
2
0
1
@wamserma thanks, ya, i send another message to the customer service and see if that brings more positive outcome. to add, my reviews stating what happened were rejected because they don't comply with review guidelines.
0
0
0
@troglobit thanks for the compassion, i'm not even pissed for some reason because the situation is so ridiculous :D cannot honestly believe this
1
0
0

Jarkko Sakkinen

Great my money was literally stolen by #Amazon. No delivery and no refund because 30 days from delivery date was passed. A delivery date, of which I had no idea.
2
0
0

Ludovic :Firefox: :FreeBSD:

Coming to fosdem this year? you use ? Want to sign your key? Good news, I'm organizing a key signing party (https://en.wikipedia.org/wiki/Key_signing_party).

details are at https://ludovic.hirlimann.net/2024/01/key-signing-party-at-fosdem-2024.html

please boost or share, so people come and attend.

0
2
1

K. Ryabitsev šŸ

Would be nice if all package managers understood/aliased all common English verbs meaning "remove this package", because I can never remember if it's "remove", "erase", or "uninstall".
5
5
21

Jarkko Sakkinen

Edited 1 year ago
Right, someone reminded me yesterday that if you want rigid memory allocation scheme with heap, you can implement that with heapless crate. It will deliver allocation errors from pre-allocated heap per-allocation. For stuff that I might be doing with #Rust in user space that is good enough.

The de-facto response from Rust application for OOM is panic.

#rustlang
0
0
2
@alerque I'm mostly looking at things from operating systems and alike side and I have total buy-in uapi and drivers side because merits are really something I count (i.e. preventing subcategories of exploits thanks to compiler) but the "core" side of the equation is totally alien to me. Sorry, totally off-topic but just writing these down merely as remarks.
0
0
0
@alerque And also sort of might be a bit harsh and controversial to say this but when there's big noise about a new language feature (which in the end means zero value at least at its epoch) I just think "when are these language features going to end". I mean on C side in kernel we were before like C89 + gnu extensions and now I suppose we are like C11 standard('ish).

This rapidness might work for user space but especially for core kernel features feels a bit brutal to say the least...

I'm actually just opening my views because in LKML I see "yes Rust" and "please no Rust" so trying to address "in-between-but-doubtful-of-Rust" camp's concerns :-)
1
0
0

Jarkko Sakkinen

Edited 1 year ago

@alerque Actually (and this is literal fact) before I did one day cargo install bat, I had an alias for along the lines of cat <file> | vim -R - sort of thing so it was literally just way to shortcut that and not much else.

The way Rust community looks at a ā€œchangeā€ is sort of ā€œthis would nicer way to do thisā€. The way kernel community looks at a ā€œchangeā€ is more like ā€œwe have this alarming situation that we need to absolutely deal with right here an right now or data centers or whatnot will be doomedā€.

And even my fav language C is in the end for me an opcode generator, not more or less. Rust is yet another opcode generator with static analysis built-in. I just vote for the tech first and totally disregard ā€œlanguage levelā€ kind of merits. What works the stuff that goes best to the cores best WFM me best in the end :-)

1
0
0
@monsieuricon well deserved. i mean you've done extra-ordinary work with tooling that really makes the world a better place :-)
0
0
2

K. Ryabitsev šŸ

Just to prove that not all mail we get is odd or threatening.

ā™„ļø
3
12
67

Jarkko Sakkinen

Edited 1 year ago
@alerque starship.rs is a good example on how to engineer properly with rust, as it solves an actual problem: how to remove overhead from shell prompt. i.e. not "here's my own incompatible version" :-) i've been totally committed end user for a number of years now...

it actually does the opposite: it improves compatibility because e.g. the same prompt translates from something like bash to something like powershell.
1
0
0
@alerque well that's exactly what engineers do. other way around is sort moving responsibility to the user by breaking backwards compatibility :-) Almost anything can be refactored and refined. It takes time and is difficult but it is optimal for the users.

For instance, I like that bat has syntax highlighting but I would scrape it any day if GNU's version added the same feature, and I would not tbh care if it was implemented in Rust or not. This sort of culture drives to loose commitment and saturated software ecosystem,.

This article really never gets old: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/
1
0
0

Jarkko Sakkinen

LOL, took year after grabbing #kilohearts #phaseplant to realize how take pitch tracking away from sampler: set harmonics to zero.

i like to phase plant as a replacement for one shot sample player because a sound can be mixed fully within a plugin which makes stuff easy to translate between projects and even #DAW's. you get nicely self-contained packages from #preset's. it provides measurable value over using stock plugins this way.

also one thing that is IMHO done better in any other synth i'm aware is preset management as you can easily configure additional directories, which can be e.g. in dropbox.

they've really thought of these boring file management aspects, which make it one of the best options for being a go-to synth.
0
0
0

Jarkko Sakkinen

cool my #riscv #keystone page table bootstrapping fixes for #cva6 are all merged to upstream. i debugged the issues over a month so nice to see that it was worth it. actually learning how #opensbi is implemented was in all cases definitely a good lesson to learn.
0
0
1

Jarkko Sakkinen

Edited 1 year ago
In 99,999% of cases it would be better if people would work out with existing and established open source communities to enable #Rust rather than making their "better" completely new version of any possible asset.

It is slow, tedious, complicated and sometimes even quite discouraging but if you are successful then you are also doing something of high measurable value. And by going through the long and hard path also the end users will get the governance of long-term support, which they IMHO deserve.

At least for me the end user is the king of the hill, not developers. We need to do the hard and nasty part.

#rustlang #opensource
1
0
2

Today, on January 11th, we have to remember who died in 2013: Aaron Swartz AaronSwartz

You may know him from his contribution to or creation of:

blank • Markdown
blank • The Creative Commons License CreativeCommons
blank • RSS rss blobcat_rss
blank • Reddit

We must never forget him and his contributions to our world forever - especially due to circumstances of injustice and the cause he became a martyr for.

0
7
1

Jarkko Sakkinen

Edited 1 year ago
@oldladyplays the point of failure in my case was the web version of https://novationmusic.com/components which works perfectly in chrome. possibly could give a shot a ff if webmidi has since been fixed.

i just put this because it is not really literal truth that google has somehow "failed". google has not failed more than any other browser vendor.
0
0
0
Show older