Get live statistics and analysis of byte.sol — e/acc's profile on X / Twitter

This playlist hits different at 3 AM

An absolute goldmine - 1000+ videos on building Linux from scratch

Kicking off a Linux 101 series starting Monday! Week 1: Foundations Day 1: What is Linux? Distros & why it matters Day 2: Installing Linux (VM/dual boot/WSL) Day 3: Terminal basics & why CLI rocks Day 4: Navigation - pwd, ls, cd Day 5: File operations - mkdir, cp, mv, rm Day 6: Viewing files - cat, less, nano Day 7: Weekend practice & review Week 2: Level Up Day 8: File permissions - chmod, chown Day 9: Search & find - grep, find, locate Day 10: Process management - ps, top, kill Day 11: Package management - apt/dnf Day 12: Users & sudo Day 13: Networking - ping, curl, wget Day 14: Journey recap & next steps Think Linux is hard? Watch me prove it's not.

Name a better playlist than this for projects. I'm waiting

🐧 Day 1/14: What is Linux? Starting from zero. Let's understand what Linux actually is and why it matters for developers 🧵 1/ What is Linux? > Linux is an operating system (OS) - just like Windows or macOS. > But here's the difference: it's completely free and open-source. Anyone can see the code, modify it, and distribute it. > Created by Linus Torvalds in 1991 as a hobby project. 2. Why should you care? > 96% of the world's top 1 million servers run Linux. > Android (3+ billion devices) is built on Linux. > Every major cloud platform (AWS, Azure, Google Cloud) runs on Linux. > Most development tools are built for Linux first. If you code, you WILL work with Linux. 3. Linux vs Windows vs macOS: > Windows/Mac: The company controls everything. Closed source. > Linux: Community-driven. You control your system completely. Want to change how something works? You can. Want to see the actual code? It's all there. This is power. 4. What is a "Distribution" (Distro)? Here's where it gets interesting: > Linux itself is just the core (called the "kernel"). Different groups package it with different software, interfaces, and tools. > These packages = Distributions (distros). Think: same engine, different cars. 5. Popular Distros explained: > Ubuntu - Most beginner-friendly. Huge community. If you're stuck, someone has already solved it. > Fedora - Sponsored by Red Hat. Gets new features first. Stable but modern. > Debian - Rock solid. Ubuntu is actually built on Debian. Trusted for servers. 6. More distros: > Arch Linux - Build everything yourself. You learn A LOT but it's hard mode. > Linux Mint - Based on Ubuntu, even friendlier interface. > Red Hat - Enterprise focused, used in big companies. For beginners? Start with Ubuntu. Period. 7. The Linux Philosophy: > "Everything is a file" Text-based configuration (no hidden settings). > Small tools that do one thing really well Chain tools together for power. 8. Real-world impact: > Supercomputers: 100% run Linux > Stock exchanges: Linux > SpaceX rockets: Linux > Your Netflix stream: Linux servers > This tweet: Likely served from Linux It's literally running the world. 9. What you'll gain? > Understanding how computers actually work. > Command line mastery. > Server management skills. > DevOps fundamentals. > Freedom from expensive licenses. > Respect from senior devs. 😎 10. Tomorrow (Day 2): Installing Linux We'll cover: > Virtual machines (safest way to start) > Dual boot (run Linux + Windows) > WSL (Windows Subsystem for Linux) If you're following along, drop a 🐧 Let's master this together 🔥

This is all you need to get Rusty !

One elevator crash created Rust 🦀 Graydon Hoare was annoyed by his software crashes from a memory bug. Hence, he started building Rust in 2006 as a side project. Mozilla saw it, said "this is insane," and backed it. Fast forward: Rust is now in the Linux kernel, running Discord, Cloudflare, and half the infrastructure you use daily. All because one guy refused to accept "that's just how C++ works." Sometimes the best innovations come from being tired of everyone else's bullshit. What's stopping you from innovating one ?

🐧Day 2/14 of Linux 101 series: Installing Linux Time to get your hands dirty. Today we're understanding the three ways to install Linux 🧵 1. The three installation methods: > Virtual Machine (VM) - Run Linux inside your current. > OS Dual Boot - Install Linux alongside Windows/Mac. > WSL (Windows Subsystem for Linux) - Linux terminal on Windows. Each serves different needs. Let's understand them deeply. 2. Method 1: Virtual Machine (VM) What it actually is: > Software that creates a "virtual computer" inside your real computer. > Linux thinks it's running on real hardware, but it's sandboxed. > Uses your computer's resources (RAM, CPU, storage) but keeps everything isolated VirtualBox/VMware creates a virtual hardware layer. Think of it as a computer inside your computer. 3. VM - How it works: > You allocate resources: "Linux gets 4GB RAM, 2 CPU cores, 25GB storage". > Linux installs and runs in this virtual environment Your files, Windows/Mac stay completely untouched. > Can snapshot (save states) and rollback anytime. Your host OS and Linux never interfere with each other. 4. VM - When to use: Perfect for: > Beginners learning and might break things. Testing multiple distros simultaneously. > Need both OS running at same time. > Have 8GB+ RAM (4GB for Linux, 4GB for host). Pros: 100% safe, easy to delete Cons: 10-15% performance overhead 5. Method 2: Dual Boot What it actually is: > Two separate operating systems installed on the same physical machine. > Your hard drive gets partitioned (divided into sections). > During boot, bootloader lets you choose which OS to start with. > Only one OS runs at a time, giving full access to all hardware. Complete separation, maximum performance. 6. Dual Boot - How partitioning works: Your 500GB drive becomes: > 300GB - Windows partition (existing) > 25GB - Linux root partition (/) > 4GB - Linux swap (virtual memory) > 171GB - Shared storage or Linux home Each OS sees only its partitions. GRUB sits on boot partition and manages startup. 7. Dual Boot - When to use: Perfect for: > Serious Linux learners committed to the journey Limited RAM (8GB or less) > Need maximum performance (no overhead). > Want complete Linux capabilities. Pros: Full hardware access, pure Linux experience Cons: Can't run both simultaneously, partitioning needs care. 8. Method 3: WSL (Windows Subsystem for Linux) What it actually is: > Microsoft's translation layer that runs Linux binaries natively on Windows Not a VM, not dual boot. > It's a compatibility layer Linux kernel runs alongside Windows kernel. > WSL 2 uses lightweight VM but feels native Best of both worlds for developers. 9. WSL - How it works: > WSL translates Linux system calls to Windows equivalents > Full Linux terminal and command-line tools. Access Windows files from Linux (/mnt/c/) > Run Linux servers, development tools. Seamless integration between both systems Easiest installation: One PowerShell command (wsl --install) 10. Which method should YOU choose? > VM: Safe practice, can't break anything → Beginners. > Dual Boot: Full Linux power, committed learning → Serious learners. > WSL: Developer tools, stay on Windows → Windows users who need Linux tools. Best YT channel for Linux installation tutorials, in replies ! Tomorrow (Day 3): We master the Terminal! Drop a 🐧 if you chose your method!

Rust 101 - Build a simple Rust HTTP server using Actix 🦀🧵

Rust's async is beautiful chaos 😮‍💨 Most languages hide concurrency complexity. Rust makes you face it and that's why it's faster. Looks simple - async fn fetch_data() { let result = api_call().await; } But under the hood? Rust compiles this into a state machine. No hidden runtime. No garbage collector pauses. No "it'll probably be fine." Every .await is a surrender point where your task yields control. The executor (like Tokio) manages thousands of these tasks on a handful of threads. Zero-cost abstraction means async code runs as fast as hand-written state machines. Python's async? Runtime overhead. JavaScript's promises? Hidden event loop magic. Rust's async? You see the cost, you pay for what you use, nothing more. The learning curve is steep because Rust refuses to lie to you about what's happening. Master Rust async and you'll understand concurrency better than 99% of developers. 🥱

🐧 Day 1/14: What is Linux? Starting from zero. Let's understand what Linux actually is and why it matters for developers 🧵 1/ What is Linux? > Linux is an operating system (OS) - just like Windows or macOS. > But here's the difference: it's completely free and open-source. Anyone can see the code, modify it, and distribute it. > Created by Linus Torvalds in 1991 as a hobby project. 2. Why should you care? > 96% of the world's top 1 million servers run Linux. > Android (3+ billion devices) is built on Linux. > Every major cloud platform (AWS, Azure, Google Cloud) runs on Linux. > Most development tools are built for Linux first. If you code, you WILL work with Linux. 3. Linux vs Windows vs macOS: > Windows/Mac: The company controls everything. Closed source. > Linux: Community-driven. You control your system completely. Want to change how something works? You can. Want to see the actual code? It's all there. This is power. 4. What is a "Distribution" (Distro)? Here's where it gets interesting: > Linux itself is just the core (called the "kernel"). Different groups package it with different software, interfaces, and tools. > These packages = Distributions (distros). Think: same engine, different cars. 5. Popular Distros explained: > Ubuntu - Most beginner-friendly. Huge community. If you're stuck, someone has already solved it. > Fedora - Sponsored by Red Hat. Gets new features first. Stable but modern. > Debian - Rock solid. Ubuntu is actually built on Debian. Trusted for servers. 6. More distros: > Arch Linux - Build everything yourself. You learn A LOT but it's hard mode. > Linux Mint - Based on Ubuntu, even friendlier interface. > Red Hat - Enterprise focused, used in big companies. For beginners? Start with Ubuntu. Period. 7. The Linux Philosophy: > "Everything is a file" Text-based configuration (no hidden settings). > Small tools that do one thing really well Chain tools together for power. 8. Real-world impact: > Supercomputers: 100% run Linux > Stock exchanges: Linux > SpaceX rockets: Linux > Your Netflix stream: Linux servers > This tweet: Likely served from Linux It's literally running the world. 9. What you'll gain? > Understanding how computers actually work. > Command line mastery. > Server management skills. > DevOps fundamentals. > Freedom from expensive licenses. > Respect from senior devs. 😎 10. Tomorrow (Day 2): Installing Linux We'll cover: > Virtual machines (safest way to start) > Dual boot (run Linux + Windows) > WSL (Windows Subsystem for Linux) If you're following along, drop a 🐧 Let's master this together 🔥

Gm from the mountains 💚

Rust challenge - Why doesn't this code compile ? fn str() -> &String { let s = String::new("String"); &s }

Kicking off a Linux 101 series starting Monday! Week 1: Foundations Day 1: What is Linux? Distros & why it matters Day 2: Installing Linux (VM/dual boot/WSL) Day 3: Terminal basics & why CLI rocks Day 4: Navigation - pwd, ls, cd Day 5: File operations - mkdir, cp, mv, rm Day 6: Viewing files - cat, less, nano Day 7: Weekend practice & review Week 2: Level Up Day 8: File permissions - chmod, chown Day 9: Search & find - grep, find, locate Day 10: Process management - ps, top, kill Day 11: Package management - apt/dnf Day 12: Users & sudo Day 13: Networking - ping, curl, wget Day 14: Journey recap & next steps Think Linux is hard? Watch me prove it's not.

One elevator crash created Rust 🦀 Graydon Hoare was annoyed by his software crashes from a memory bug. Hence, he started building Rust in 2006 as a side project. Mozilla saw it, said "this is insane," and backed it. Fast forward: Rust is now in the Linux kernel, running Discord, Cloudflare, and half the infrastructure you use daily. All because one guy refused to accept "that's just how C++ works." Sometimes the best innovations come from being tired of everyone else's bullshit. What's stopping you from innovating one ?

🐧Day 2/14 of Linux 101 series: Installing Linux Time to get your hands dirty. Today we're understanding the three ways to install Linux 🧵 1. The three installation methods: > Virtual Machine (VM) - Run Linux inside your current. > OS Dual Boot - Install Linux alongside Windows/Mac. > WSL (Windows Subsystem for Linux) - Linux terminal on Windows. Each serves different needs. Let's understand them deeply. 2. Method 1: Virtual Machine (VM) What it actually is: > Software that creates a "virtual computer" inside your real computer. > Linux thinks it's running on real hardware, but it's sandboxed. > Uses your computer's resources (RAM, CPU, storage) but keeps everything isolated VirtualBox/VMware creates a virtual hardware layer. Think of it as a computer inside your computer. 3. VM - How it works: > You allocate resources: "Linux gets 4GB RAM, 2 CPU cores, 25GB storage". > Linux installs and runs in this virtual environment Your files, Windows/Mac stay completely untouched. > Can snapshot (save states) and rollback anytime. Your host OS and Linux never interfere with each other. 4. VM - When to use: Perfect for: > Beginners learning and might break things. Testing multiple distros simultaneously. > Need both OS running at same time. > Have 8GB+ RAM (4GB for Linux, 4GB for host). Pros: 100% safe, easy to delete Cons: 10-15% performance overhead 5. Method 2: Dual Boot What it actually is: > Two separate operating systems installed on the same physical machine. > Your hard drive gets partitioned (divided into sections). > During boot, bootloader lets you choose which OS to start with. > Only one OS runs at a time, giving full access to all hardware. Complete separation, maximum performance. 6. Dual Boot - How partitioning works: Your 500GB drive becomes: > 300GB - Windows partition (existing) > 25GB - Linux root partition (/) > 4GB - Linux swap (virtual memory) > 171GB - Shared storage or Linux home Each OS sees only its partitions. GRUB sits on boot partition and manages startup. 7. Dual Boot - When to use: Perfect for: > Serious Linux learners committed to the journey Limited RAM (8GB or less) > Need maximum performance (no overhead). > Want complete Linux capabilities. Pros: Full hardware access, pure Linux experience Cons: Can't run both simultaneously, partitioning needs care. 8. Method 3: WSL (Windows Subsystem for Linux) What it actually is: > Microsoft's translation layer that runs Linux binaries natively on Windows Not a VM, not dual boot. > It's a compatibility layer Linux kernel runs alongside Windows kernel. > WSL 2 uses lightweight VM but feels native Best of both worlds for developers. 9. WSL - How it works: > WSL translates Linux system calls to Windows equivalents > Full Linux terminal and command-line tools. Access Windows files from Linux (/mnt/c/) > Run Linux servers, development tools. Seamless integration between both systems Easiest installation: One PowerShell command (wsl --install) 10. Which method should YOU choose? > VM: Safe practice, can't break anything → Beginners. > Dual Boot: Full Linux power, committed learning → Serious learners. > WSL: Developer tools, stay on Windows → Windows users who need Linux tools. Best YT channel for Linux installation tutorials, in replies ! Tomorrow (Day 3): We master the Terminal! Drop a 🐧 if you chose your method!

Rust's async is beautiful chaos 😮‍💨 Most languages hide concurrency complexity. Rust makes you face it and that's why it's faster. Looks simple - async fn fetch_data() { let result = api_call().await; } But under the hood? Rust compiles this into a state machine. No hidden runtime. No garbage collector pauses. No "it'll probably be fine." Every .await is a surrender point where your task yields control. The executor (like Tokio) manages thousands of these tasks on a handful of threads. Zero-cost abstraction means async code runs as fast as hand-written state machines. Python's async? Runtime overhead. JavaScript's promises? Hidden event loop magic. Rust's async? You see the cost, you pay for what you use, nothing more. The learning curve is steep because Rust refuses to lie to you about what's happening. Master Rust async and you'll understand concurrency better than 99% of developers. 🥱

Rust 101 - Why doesn’t this code compile ?

Day 4/14 of Linux 101 series: Basic Navigation Today we master moving around the Linux filesystem like a pro 🧵 1. The Linux filesystem structure: > Everything starts from root: / > Unlike Windows (C:, D:), Linux has ONE unified tree. > All drives, USB, everything mounts under this single tree. > Your personal files: /home/username > Programs: /bin, /usr/bin Configuration: /etc One tree to rule them all. 2. Understanding paths: Two types of paths: > Absolute path: Starts from root (/) > Relative path: Starts from current location Example: > Absolute: /home/username/Documents/file.txt > Relative: Documents/file.txt (if you're in /home/username). Know the difference. It matters. 3. The cd command (Change Directory): cd /home/username/Documents - Go to absolute path cd Documents - Go to relative path cd .. - Go up one level cd ../.. - Go up two levels cd ~ - Go to home directory cd - - Go to previous directory These shortcuts save massive time. 4. The ls command (List files): ls - List files in current directory ls -l - Long format (detailed info) ls -a - Show hidden files (files starting with .) ls -la - Combine both (long + hidden) ls -lh - Human readable sizes (KB, MB, GB) You'll use ls -la more than anything else. 5. Special directory symbols: . (single dot) - Current directory .. (double dot) - Parent directory ~ (tilde) - Home directory / (slash) - Root directory - (dash) - Previous directory Master these and navigation becomes second nature. 6. Absolute vs Relative paths - When to use: Absolute paths: > Scripts that need to work from anywhere. > When you're unsure of current location. > Clearer for beginners. Relative paths: > Faster to type More flexible. > Professional workflow. > Start with absolute, graduate to relative. 7. Real examples - Practice these: > pwd - Where am I? > cd /home - Go to /home > ls - What's here? > cd username - Go into your user folder > pwd - Confirm: /home/username > cd Documents - Go to Documents > cd .. - Back to /home/username > cd ~ - Jump to home instantly Type these 10 times. Build muscle memory. 8. Pro tips for faster navigation: Tab completion: > Type "Doc" + Tab → autocompletes to "Documents". > Up arrow: Recalls previous commands. > Ctrl+R: Search command history. > cd without arguments: Takes you home. Use Tab ALWAYS - it prevents typos. 9. Common beginner mistakes: ❌ cd /home /username - Space breaks it ✅ cd /home/username ❌ CD Documents - Linux is case-sensitive ✅ cd Documents ❌ Forgetting where you are ✅ Use pwd constantly Case matters. Spaces matter. Location matters. 10. Practice challenge for today: 1. pwd (note your location) 2. cd / (go to root) 3. ls (see root directories) 4. cd home (go to home) 5. cd username (replace with yours) 6. ls -la (see all files) 7. cd Documents 8. cd .. (go back) 9. cd ~ (jump home) 10. pwd (confirm you're home) Repeat until it feels natural. Tomorrow (Day 5): Working with Files Drop a 🐧 if you practiced navigation today!

Sometimes i forget that, i do have pretty good editing skills 🫠

Name a better playlist than this for projects. I'm waiting

Gm chat !

Quick lyf update - Met with an accident recently ! Will comeback soon

Day 5/14 of Linux 101 series: Working with Files Today we learn to create, copy, move, and delete.🧵 1. Creating files - The touch command: - touch file.txt - Create empty file. - touch file1.txt file2.txt file3.txt - Create multiple files. - touch "my file.txt" - File with spaces. (use quotes) > touch literally "touches" a file - creates it if doesn't exist. > If file exists, updates its timestamp. Simple but powerful. 2. Creating directories - The mkdir command: - mkdir folder - Create single directory. - mkdir folder1 folder2 folder3 - Create multiple. - mkdir -p parent/child/grandchild - Create nested directories. - mkdir "my folder" - Directory with spaces. > mkdir = make directory. > -p flag creates parent directories if they don't exist. > Without -p, nested creation fails. Always use -p for nested folders. 3. Copying files - The cp command: - cp file.txt backup.txt - Copy file in same location. - cp file.txt /home/user/Documents/ - Copy to another location. - cp file.txt ../file.txt - Copy to parent directory. - cp -r folder/ backup/ - Copy entire directory. (recursive) > cp = copy. > -r (recursive) needed for directories. > Original file stays, copy is created. cp doesn't ask for confirmation by default. 4. Moving/Renaming - The mv command: - mv oldname.txt newname.txt - Rename file. - mv file.txt /home/user/Documents/ - Move file. - mv folder/ /home/user/ - Move directory. - mv *.txt Documents/ - Move all .txt files. > mv = move. (also used for renaming) > No -r needed for directories. > Original file disappears, moves to new location. mv is both move & rename. 5. Deleting files - The rm command: WARNING: No trash bin. Deletion is permanent. - rm file.txt - Delete file. - rm file1.txt file2.txt - Delete multiple files. - rm -r folder/ - Delete directory and contents. - rm -rf folder/ - Force delete. (dangerous!) - rm *.txt - Delete all .txt files. > rm = remove. > -r for directories. (recursive) > -f forces deletion without asking. Double check before using rm. 6. Safe deletion practices: Before deleting: > ls to confirm you're in right directory. > Use rm -i for interactive mode. (asks confirmation) > Double check paths. > Start without -f flag. > Test with ls first: ls *.txt (see what matches) Measure twice, delete once. 7. Wildcards - Power up your commands: * - Matches anything. ? - Matches single character. [abc] - Matches a, b, or c. Examples: - ls *.txt - All .txt files. - rm file?.txt - file1.txt, file2.txt, fileA.txt. - cp [abc]*.txt backup/ - Files starting with a, b, or c. Wildcards = batch operations made easy. 8. Viewing file content - Quick preview: - cat file.txt - Display entire file. - head file.txt - First 10 lines. - tail file.txt - Last 10 lines. - head -n 5 file.txt - First 5 lines. - tail -n 20 file.txt - Last 20 lines. > cat = concatenate. (shows full content) > head/tail for large files. > Useful before editing. We'll dive deeper into viewing tomorrow. 9. Real-world workflow example: - mkdir project - cd project - touch index.html style.css script.js - ls -l - cp index.html index-backup.html - mv style.css styles.css - rm index-backup.html - cd .. This is daily developer workflow. 10. Practice challenge for today: 1. mkdir test 2. cd test 3. touch file1.txt file2.txt file3.txt 4. ls 5. cp file1.txt file1_backup.txt 6. mv file2.txt renamed.txt 7. ls 8. rm file3.txt 9. cd .. 10. rm -r test Practice in a safe test folder first! Tomorrow (Day 6): Viewing & Editing Files Drop a 🐧 if you created and deleted files today!