From Newsgroup: comp.programming

On 07/01/2026 21:48, r4dnRd wrote:

[in reply to r4dnRd <r4dnRd@usenet_reborn.tui>]

I came across this article, this is a guy I know from some hacker events in Germany like CCC Congress etc
This is a way for CPU's to handle low level programming with out having to translate to ASM etc... or so I think.

Introduction to SIMD programming in pure Rust

https://kerkour.com/introduction-rust-simd

Thank you for this article, it is very useful as every article Silvain writes.

[...]

To access these CPU features in other languages like C you may need to write assembly and as usual rust saves you from that.

The mid-level C programmer just finds a suitable library.
Rust's approach on the other hand is a nice example of a
monolithic architecture and the feature bloat, which are
rather the typical outcome of the most common incompetence.

Julio

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.programming

[in reply to r4dnRd <r4dnRd@usenet_reborn.tui>]

On 07/01/2026 21:48, r4dnRd wrote:

[in reply to r4dnRd <r4dnRd@usenet_reborn.tui>]

I came across this article, this is a guy I know from some hacker events in Germany like CCC Congress etc
This is a way for CPU's to handle low level programming with out having to translate to ASM etc... or so I think.

Introduction to SIMD programming in pure Rust

https://kerkour.com/introduction-rust-simd

Thank you for this article, it is very useful as every article Silvain writes.

[...]

To access these CPU features in other languages like C you may need to write
assembly and as usual rust saves you from that.

The mid-level C programmer just finds a suitable library.
Rust's approach on the other hand is a nice example of a
monolithic architecture and the feature bloat, which are
rather the typical outcome of the most common incompetence.

Julio

LOL The "better than you" rhetoric.

Sometimes people just write a piece of software to prove themselves
there was some ammount of understanding, to learn how things work or
for the simple pleasure of exploration. It is not always i write good
code for living or make it useful to someone else, nobody was born
taught or just sit and write their own network stack themselves ready
for production in one night (unless you have done it regularly).

The library is not to prove competence, is a document of exploration
something useful might come after that. Obviously it might not be
useful to build something with it but it is just a document you write
when exploring something.

I guess there is people who was born taught and competent :D
--
r4dnRd
Nevermind i he might be coding all night...
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.programming

On 06/03/2026 18:39, r4dnRd wrote:

[in reply to r4dnRd <r4dnRd@usenet_reborn.tui>]

On 07/01/2026 21:48, r4dnRd wrote:

[in reply to r4dnRd <r4dnRd@usenet_reborn.tui>]

I came across this article, this is a guy I know from some hacker events in Germany like CCC Congress etc
This is a way for CPU's to handle low level programming with out having to translate to ASM etc... or so I think.

Introduction to SIMD programming in pure Rust

https://kerkour.com/introduction-rust-simd

Thank you for this article, it is very useful as every article Silvain writes.

[...]

To access these CPU features in other languages like C you may need to write
assembly and as usual rust saves you from that.

The mid-level C programmer just finds a suitable library.
Rust's approach on the other hand is a nice example of a
monolithic architecture and the feature bloat, which are
rather the typical outcome of the most common incompetence.

LOL The "better than you" rhetoric.

The irony being that you think you are the one who should say that.

The most common incompetence and/then the most common nonsense.

To put it charitably.

*PLONK*

-Julio

--- Synchronet 3.21d-Linux NewsLink 1.2