#developed linux

[shadowblade8192]

likes charge reblogs cast

[wayfire-official]

Tonight I woke up at 4am due to considerable stomach pain, and in my half-sleep I was very convinced that it was because of a bug in a script my belly was running, and I spent half an hour dream-debugging it to no avail until I finally realised that my belly doesn't run scripts

[nixcraft]

me_irl

[heart-ghost-studyblr]

Getting old is interesting. I've always been a middle ground between sports (skateboarding, surfing, jiu-jitsu) and an avid student. Over time, it's clear that you can't keep trying the same tricks, just as you can't study the same way.

Today, as I'm writing an article about event-driven architectures, I realize that final exams in college were much easier, just like it's not as easy to jump the same stairs on a skateboard as I did when I was 18. In the image, you can see my favorite note-taking app, Obsidian, and my Neovim terminal. I'm diving deep into Java, and for that, I'm taking a Spring Boot bootcamp offered by Claro through the DIO Innovation One platform.

[mutter-official]

should i switch to jetbrains ides

they are a) not electron, b) either open-source or based on an open-source codebase, and c) look really powerful

don't get me wrong i love neovim but the constant terminal-wrangling is starting to be a bit much + i want features like code completion and doc peeking that just work out of the box

[flooferland]

I find kernel level anti-cheats and generally client-side anticheats like BattleEye, EasyAntiCheat, and Vanguard really stupid, because they really aren't stopping cheaters, all they're doing is discouraging them while sacrificing performance, user privacy, Linux support, and generally risking accidentally banning casual user.

I started developing my own anti-cheat for a game and it hit me, you should never have any anti-cheat on the client. All anti-cheats should be server-side, because to this day players are still figuring out ways to bypass these anti-cheats, like using hardware-level exploits which are physically impossible to detect unless they start serving anti-cheats as AI-powered robots that are physically in your room looking at you while you game.

Think about it.. Wall hacks let you see other players through walls, easy solution right? Just don't tell the client where the other players are, do server-side calculations for occlusion, you already have a system for it to do it client-side since it saves performance not to render players that aren't on the screen. But nope, because it would slightly increase server costs, even if it makes cheating impossible to perform.

The number one rule in multiplayer is "NEVER TRUST THE CLIENT UNDER ANY CIRCUMSTANCE", and these huge game dev corporations are consistently not following it, then complain about having cheaters while going "Oh, it must be the Linux users!!! Not our flawed approach at anti-cheat!!!"

[cool-retro-term-official]

maybe my hate for c++ really is just that I haven't seen my relationship with this language as an actual relationship and more of a "owning a tool to do your job". Maybe I, also, have to give to the language. Maybe it's not all about getting all I want from it, but also letting it express itself, listening to what it says, and giving to it. Maybe I've been a monster to g++. Yes C++ has its rough edges, yes sometimes it doesn't agree with you, yes it has feelings, needs and opinions, and those doesn't always match those of the programmer. Seeing "non trivial constructor" type of error shouldn't make you angry and think "what's that supid language ???!!", but should instead make you realize the language has understanding issues. I'm autistic and I got my quirks, it's a programming language and it has its quirks. They can be beautiful, they can be ugly. It's not its fault, it isn't yours, things aren't always easy. Giving to the language means helping it in these hard times. Take care of your languages, they might not be people, but they still deserve respect.

Except javascript.

[codingquill]

What happens when you start your computer ? ( Booting a computer )

We studied this in the lecture today, and it was quite interesting. What makes something a hundred times simpler than it is? Creating a story about it. That's why I made this super fun dialog that will help you understand it all.

I've set up a drive to compile everything I create related to the Linux operating system. Feel free to explore it for more details on the topics discussed in the conversation below. Check it out here.

Have a fun read, my dear coders!

In the digital expanse of the computer, Pixel, the inquisitive parasite, is on a microventure with Binary, a wise digital guide. Together, they delve into the electronic wonders, uncovering the secrets hidden in the machine's core.

Pixel: (zooming around) Hey there! Pixel here, on a mission to demystify the tech wonders . There's a creature named Binary who knows all the ins and outs. Let's find them!

Binary: (appearing with a flicker of pixels) Pixel, greetings! Ready to explore what happens inside here?

Pixel: Absolutely! I want the full scoop. How does this thing come alive when the human outside clicks on "start"?

Binary: (with a digital chuckle) Ah, the magic of user interaction. Follow me, and I'll reveal the secrets.

(They traverse through the circuits, arriving at a glowing portal.)

Pixel: (inquiring) What's the deal with this glowing door?

Binary: (hovering) Pixel, behold the BIOS - our machine's awakening. When the human clicks "start," the BIOS kicks in, checking if our components are ready for action.

(They proceed to observe a tiny program in action.)

Pixel: (curious) Look at that little messenger running around. What's it up to?

Binary: (explaining) That, Pixel, is the bootloader. It plays courier between the BIOS and the operating system, bringing it to life.

Pixel: (excitedly buzzing) Okay! How does the computer know where to find the operating system?

Binary: Ah, Pixel, that's a tale that takes us deep into the heart of the hard disk. Follow me.

(They weave through the digital pathways, arriving at the hard disk.)

Pixel: (curious) Huh? Tell me everything!

Binary: Within this hard disk lies the treasure chest of the operating system. Let's start with the Master Boot Record (MBR).

(They approach the MBR, Binary pointing to its intricate code.)

Binary: The MBR is like the keeper of the keys. It holds crucial information about our partitions and how to find the operating system.

Pixel: (wide-eyed) What's inside?

Binary: (pointing) Take a look. This is the primary boot loader, the first spark that ignites the OS journey.

(They travel into the MBR, where lines of code reveal the primary boot loader.)

Pixel: (in awe) This tiny thing sets the whole show in motion?

Binary: (explaining) Indeed. It knows how to find the kernel of the operating system, which is the core of its existence.

(They proceed to the first partition, where the Linux kernel resides.)

Pixel: (peering into the files) This is where the OS lives, right?

Binary: (nodding) Correct, Pixel. Here lies the Linux kernel. Notice those configuration files? They're like the OS's guidebook, all written in text.

(They venture to another partition, finding it empty.)

Pixel: (confused) What's the story with this empty space?

Binary: (smirking) Sometimes, Pixel, there are barren lands on the hard disk, waiting for a purpose. It's a canvas yet to be painted.

Pixel: (reflecting) Wow! It's like a whole universe in here. I had no idea the operating system had its roots in the hard disk.

(They continue their microventure, navigating the binary landscapes of the computer's inner world.Pixel gazes at the screen where choices appear.)

Pixel: What's happening here?

Binary: (revealing) This is where the user picks the operating system. The computer patiently waits for a decision. If none comes, it follows the default path.

(They delve deeper into the digital code, where applications start blooming.)

Pixel: (amazed) It's like a digital garden of applications! What's the enchantment behind this?

Binary: (sharing) Here, Pixel, is where the applications sprout to life. The operating system nurtures them, and they blossom into the programs you see on the screen.

Pixel: (excited) But how does the machine know when the human clicks "start"?

Binary: It's the BIOS that senses this initiation. When the human triggers "start," the BIOS awakens, and we embark on this mesmerizing journey.

[wojenka]

i need more mutuals who are into coding and engineering!! more info under the cut!!

I planned to become an electrical engineer like my stepdad but then I decided to change my path to programming. I'm currently studying at technikum (<- wikipedia link so I don't have to explain the whole polish learning system), programmer major.

this year I have exams from web development (10th Jan - theory, 16th Jan - practical exams) and next year I have exams from App development (both mobile and desktop).

I know C family languages, Java, Python and those ones I am currently using. I also know a bit of Kotlin and I think I will continue learning it.

For web dev I know HTML and CSS ofc but also PHP and JS.

Planning on learning more languages I can use for App and operating system development as well as just to know them cause I want to after this year's exams!

my learning list:

Lua (I heard it's easy but I can't really get myself to read anything about this atm idk why)

Ruby

Assembly

Rust

As for electrical engineering I don't know much tbh but I would like to learn! I just used CAD programs for technical drawings (dad taught me some basic things when I was still thinking about going his path) helped my dad fix things on his Solar farm, houses of our neighbors and I made a few very simple circuits for fun a few years ago. Now I'm mostly focused on programming but since I learned most of the things I need for exams I have more time to do whatever I want now!

I'd like to get to know more people so I can share and mostly learn new things since even though I'm coding for years I consider myself a beginner and I am a total beginner when it comes to electrical engineering.

I'm willing to be friends or at least mutuals with anyone who codes or makes websites or is in STEM! no matter what your specialty/interest is exactly and no matter if you are a total beginner or a professional ^__^

I'd also like to have some mutuals who are into old web development and retro computing!!!!!!!!

edit: I forgot but I'm also interested in physics and quantum physics

[commedessgarcons]

begging game developers to make more games native to Linux

[pafurijaz]

Father of modern computing. Dennis Ritchie was born Today in the 1941 was father of C and Co-Developer of Unix.

[nixcraft]

[heart-ghost-studyblr]

"He is back and he is seeking revenge!!" That’s what one of my teammates said after we wrapped up a big performance upgrade on a server that was… let’s say, not performing its best. Highs and lows, right? Complex, data-heavy, fast, reliable, and done for the best 'top dogs' in the game (me included).

And then another kind of thing... I was talking with a friend who’s been struggling to find a job in his field (he's studying management, which is a solid and common path). So, why not help a little bit? (That is what is in the image, do not call me a click baiter*)

I strongly believe that if you're struggling to get into any area, a nice way to present yourself is by having a page—it can be pure HTML/CSS or a cloned repo with some kind of "personal website template" using all the NodeJS you want.

Then, turn it into a DNS like "yourname-myprofession.com" so you can show a clean, well-designed QR Code with your avatar during interviews. It’s a cleanest way possible to present your résumé and experience. Tech skills are like magic, especially for those who haven't seen it before.

[0-p01ssum]

Look at the mug they gave me today (つ╥﹏╥)つ 💚🖤💚

Also felt like sharing something dumb I did for the web development classes I'm taking 👻

[linuxtldr]

Can't bots just trust we're human without the robot dance-off? 😄

[packetpixie]

pro tip for programmers - how to alias

hey, so you know that annoying thing that happens when you're coding, and you need to run/test the same program 100 times in a row, so you end up typing "python3 testScriptWithASuperLongName.py" into the terminal about 80,000 times?

well, there's a better way! it's called aliasing :D

in your bash shell (or zsh, or whatever shell you use, but bash is the default on VSCode and most people on tumblr use VSCode, so I'm using bash as the default to explain this concept) you can set an alias, essentially a shortcut command, that runs longer commands.

(yes you can just use the up arrow key to re-run the same command, but sometimes you're typing other things into the terminal too and you don't feel like hitting the up arrow key four times in a row, and also this is just a cool and useful tip to get comfortable with aliasing so shhhh)

so, in your terminal shell, just type this:

alias run="python3 testScriptWithASuperLongName.py"

now, you can run that entire super long command, just by typing the word "run" into your terminal. Here's a screenshot of an example on my computer to make it make more sense:

in this example, i just created a simple python file that contains one line of code: print("it works!")

then, as you can see, by setting the alias to run, i can now run that file, runningatestscript.py, simply with the command 'run'.

the best part is, this alias is temporary - it only lasts as long as your shell session is open. so once you close the terminal, the run alias is cleared and you can set it again next time to any file or task you're currently working on, to save yourself a lot of typing, typos, and time.

so if you want to, you can get in the habit of always setting a run alias in the VSCode terminal for whichever file you're working with as soon as you get everything open. that way, when you need to run the same file 50 million times, you have a super easy way of doing it! you can even set it to a single letter if you want to go for maximum speed, but i prefer to use whole short words, because they're easy for me to remember.

note: if you do want to set an alias to work for all sessions, you can simply add it to your ./bashrc file. this is a common way to automate repeatable tasks, and simply to set easier-to-remember commands for terminal commands that are really complicated/confusing/hard to remember.

for example, i saved the alias checkboot="[ -d /sys/firmware/efi ] && echo 'UEFI mode' || 'BIOS mode'" into my zshrc file (zsh equivalent of bashrc file). this way, no matter how many times i rebooted my machine, i would always be able to quickly check which boot mode was running by simply typing 'checkboot'.

yesterday i was updating my boot mode from BIOS to UEFI on my very old machine that is technically compatible with UEFI, but not configured for it by default. So it was extremely helpful and saved me the time and headache of having to remember and type that long-ass command a thousand times in between many different reboots and new shells.

if you have any tasks like that, or terminal commands that you know would be useful to you, but you can never remember them when you need them, i highly recommend getting comfortable with aliasing! it can be super useful to simply set custom aliases for all the commands you don't want to remember, so that you can automate things away and not have to worry about so much linux syntax all the time when you're tring to focus on programming.

i know this may seem like a simple tip to some, but i only learned about it recently and it's been extremely helpful to integrate into my workflow and customize my OS with! so i thought it might be worthwhile to some people if i share :) hope it helps!