Jarkko Sakkinen
Posts
4417Following
316Followers
471OpenPGP: 3AB05486C7752FE1
Jarkko Sakkinen
jarkko
xtcly, get fuck off your dirty fingers from greeland trump (you fucking loser): https://www.bbc.com/news/articles/c791xy4pllqo
0
0
0
Jarkko Sakkinen
jarkko
Through some random recruitment offers I've noticed a new trend: startup websites with AI generated graphics.
If I wanted to make sure that my next startup gets neither talent nor funding that would be also the angle in branding that I'd take!
If I wanted to make sure that my next startup gets neither talent nor funding that would be also the angle in branding that I'd take!
0
0
1
@namenlos Yeah also some comments seem to have misconception that I would somehow think that cargo is bad :-) I'll clear that one up: I think cargo is great.
Especially for complex software Cargo.lock and high-granularity version control for dependencies is an asset that keeps software safe and stable.
Especially for complex software Cargo.lock and high-granularity version control for dependencies is an asset that keeps software safe and stable.
0
0
1
@namenlos Also at least once a month I end up in my professional life to a situation (could be related also e.g. C code) where I need to somehow verify whether a bug is:
1. A bug in software.
2. A toolchain bug.
In those situations a bag of tricks to cut out most of the toolchain is really an asset. 99,99% toolchain is not the stimulus but it is nice to be able exclude that because I've also bumped in to that 0,01% in the past ;-)
1. A bug in software.
2. A toolchain bug.
In those situations a bag of tricks to cut out most of the toolchain is really an asset. 99,99% toolchain is not the stimulus but it is nice to be able exclude that because I've also bumped in to that 0,01% in the past ;-)
0
0
0
@namenlos I have some real world situations mainly with custom JSON targets where without cargo does make sense or at least debugging binary output is easier with less layers. Like when I need to look at DWARF output that a compiler target generates. Obviously I use cargo when I possibly can because it obviously makes sense then ;-) To do Rust with cargo the existing books really have zero value or insight that I would find useful compared to the already pretty great documentation. For low-level hacking a book would be useful.
0
0
0
0
0
0
Jarkko Sakkinen
jarkko
Fix for LARGE event log buffers (bug was reported for 16 MiB region): https://lore.kernel.org/linux-integrity/20241221113318.562138-1-jarkko@kernel.org/T/#u
#linux #kernel #tpm
#linux #kernel #tpm
1
1
1
Jarkko Sakkinen
jarkko
@laho So for low-level programming, or starting with it with any tool, you don't need that much information to begin with it as you don't have complex frameworks to learn. Just how you tell the toolchain where the entry point is and basic stuff like that...
Thus, it is good way to start Rust when you mind is still in virgin state and not been inducted by the cargo cult just yet ;-)
Thus, it is good way to start Rust when you mind is still in virgin state and not been inducted by the cargo cult just yet ;-)
0
0
1
@namenlos when I was young everyone started with Turbo Pascal just enough to generate lookup tables with it and then moved to Turbo Assembler :-) At least you have language constructs and a high-level build language. Don't get what you are complaining about TBH.
0
0
0
An example of “Hello World” with raw Rust:
#![feature(no_core,lang_items,start)]
#![no_core]
#![no_std]
#![no_main]
#[lang = "sized"]
pub trait Sized {}
#[lang = "copy"]
pub trait Copy {}
#[no_mangle]
#[start]
pub extern fn _start ()
{
loop {}
}
You can compile it I think with:
rustc +nightly --crate-type bin -C link-arg=-nostartfiles test.rs
In such book you could obviously use core and std but this is as minimal as it can get (almost) ;-)
2
2
8
An example of “Hello World” with raw Rust:
#![feature(no_core,lang_items,start)]
#![no_core]
#![no_std]
#![no_main]
#[lang = "sized"]
pub trait Sized {}
#[lang = "copy"]
pub trait Copy {}
#[no_mangle]
#[start]
pub extern fn _start ()
{
loop {}
}
You can compile it I think with:
rustc +nightly --crate-type bin -C link-arg=-nostartfiles test.rs
In such book you could obviously use core and std but this is as minimal as it can get (almost) ;-)
2
2
8