beerman has quit [Quit: Bridge terminating on SIGTERM]
beerman has joined #crux-arm
guido_rokepo has quit [Quit: guido_rokepo]
beerman has quit [Ping timeout: 264 seconds]
beerman has joined #crux-arm
<pitillo>
jaeger: what a shame :(
pitillo has joined #crux-arm
pitillo has quit [Changing host]
<beerman>
shame indeed 😕
<pitillo>
about the riscv device stock
<pitillo>
not sure if shame is the word right word... I meant pity
guido_rokepo has joined #crux-arm
guido_rokepo has quit [Client Quit]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ crux-ports-opt-arm64 ]: ruby: update to 3.2.1
crux-arm-bot has left #crux-arm [#crux-arm]
<jaeger>
They both work in that context
guido_rokepo has joined #crux-arm
guido_rokepo has quit [Quit: guido_rokepo]
<pitillo>
thanks for clariy :) Shame has two translations in spanish (shame like pity or shame like embarrassment, and this last one could sound "hard")
<jaeger>
Same in English, pretty much
<beerman>
another thing thats a shame: I wrote a little application in rust for work to query a certain sql database with the intention to make it a webapp (wasm compile target).. and it doesn't work for that. It works as a cli application, it works as a native desktop app on both linux and windows, but compiling for wasm-unknown-unknown returns 180 whooping errors.
<beerman>
the mysql rust crate is my only direct dependency if you ignore the ui toolkit (egui) and one of its dependencies is incompatible for web compilation
<beerman>
such a sad day
<beerman>
but: programming in rust is fun, in just a few hours i was able to have a working prototype on the cli, and a few hours later I had several subpackages in my own project (a common library of functions i want to make available for all the different frontends) and the different frontends itself.
<beerman>
the compiler so nice with helping when something is wrong
<jaeger>
I haven't used it yet myself but I felt similarly with go, learning just enough to get something working quickly
<jaeger>
On the RISC-V topic, even though the VisionFive 2 order was cancelled, I also ordered a MangoPi MQ Pro and that one appears to be in transit :)
<beerman>
I can imagine that go shares a lot of qualities there, and i have already considered restarting with go
<beerman>
not sure yet
<jaeger>
I mostly like go but I also like C so people think I'm weird
<jaeger>
I figure the best language to use is the one you feel most comfortable with... of course people love to get on the bandwagon of memory safety and while I get that, it should not be the only reason you pick something to use.
<beerman>
I can agree
<jaeger>
My take is that you can produce the same quality of code in something like C but you just need to be more careful
<jaeger>
And I can also understand when people don't want to mess around with memory management and let the language do it for them.
<beerman>
I tried learning C a while ago (like.. 15 years ago or so?) and I didn't keep at it
<beerman>
didn't really do much with it either
<jaeger>
It's hard to keep at it without a goal/project in mind
<jaeger>
True of any language, though
<beerman>
yeah, pretty much
<beerman>
but, I have to say, since I started using neovim with language servers stuff just became so much more fun
<jaeger>
Understandable
<beerman>
it helps to not have to look up everything constantly, I know, shocking 😄
<beerman>
i am way to involved with coding this piece of software that i spent my past afternoons contiuing to hack on it. Right now I started thinking that if I can avoid that one problematic microdependency I have a good chance for it to just work 😄
<beerman>
and it looks like: there is a good chance for that to happen
<beerman>
being a network tool, the next hurdle is to integrate MIBs and OIDs.. but thats another problem 😄