Linux

48230 readers

500 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 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

300

The Open Source Computer Science Degree (github.com)

submitted 3 months ago by smwygdl@infosec.pub to c/linux@lemmy.ml

37 comments fedilink hide all child comments

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

[–] Suppoze@beehaw.org 5 points 3 months ago (1 children)

I think it's more important than ever. Software is getting slower and slower, and the bloat is ridiculous. Imho this is because we just work with abstractions over abstracions ignorant to how it will be computed on a real machine. I think a more appropriate methapor would be, that you can speak and understand language (program) while being illiterate at the same time (not having a fundamental understanding on how a computer works). Of course this is a exaggeration, you don't need to know about these stuff to be a adequate programmer I think.

[–] Syulang@aus.social 1 points 3 months ago

@Suppoze @dubyakay one thing I liked about programming on Atari 8 bit machines was that your code could and was expected to hit the hardware directly. It was assumed the programmer understood the nature of the hardware and would directly "talk" to it to get it to perform their task. This made coding very efficient. Not a single CPU cycle of byte of RAM was wasted. A program that analysed data from multiple environmental sensors, tabulated, averaged and plotted the results and sent then to a charter plotter would run comfortably on 16kb of RAM.

My phone take a thousand times that to fail to open my emails.