Linux

66521 readers

341 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

144

'Rust makes coding fun again': Why Linux is moving away from C, according to Greg Kroah-Hartman (www.zdnet.com)

submitted 4 days ago by HaraldvonBlauzahn@feddit.org to c/linux@lemmy.ml

93 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] zaphod@sopuli.xyz 1 points 3 days ago (1 children)

I searched for about six weeks how to fix that and it disappeared when I changed the position of the program’s data segment.

So it was a linker issue? I wouldn't call that undefined behaviour in multithreaded code.

But industry is still working with a fifty year old language written for systems where 32 kilobytes were a lot of memory.

Especially for embedded and DSP stuff there are so many architectures that aren't even supported by the Rust compiler. And on those systems 32 kiB of RAM is sometimes a lot of memory.

[–] HaraldvonBlauzahn@feddit.org 1 points 3 days ago

So it was a linker issue?

No, that would have resulted in a linker error, not random undefined behaviour

But industry is still working with a fifty year old language written for systems where 32 kilobytes were a lot of memory.

Especially for embedded and DSP stuff there are so many architectures that aren't even supported by the Rust compiler. And on those systems 32 kiB of RAM is sometimes a lot of memory.

These niches still exist but they get rapidly smaller every year. Because:

Cheap hardware gets more powerful
Demands rise... even some electric toothbrushes are networked now
Rust support for embedded devices is rapidly expanding

Plus:

In some domains, security is becoming a real issue