Me

Personal

• Doing courses listed by CIC. After I complete the technical-capacitation phase, I'll get my 1st job!
• Might consider leaving GH, for many reasons.
  • The fact that GL nukes dead accounts is a deal-breaker for me.
  • I've heard of Code-Berg, it seems interesting.
• If I contribute to any of your repos, I hope you do the same for me and/or other people :)

Repos

• I'll delete any fork that has 0 "Yours"(from my POV) branches. Therefore, links to such forks may become broken (not dead, because it's not permanent).
  • I may delete "Yours" branches if their corresponding pull-request is merged/closed.
• I may delete any of my Gists without warning. The most likely reason is due to moving its contents to an actual repo.

Langs

• ❤Faves

  • in practice: This takes into account all the stuff related to the langs (portability, documentation, std+community tools & libraries, ecosystem, etc...):

    0. JS. I'm ashamed of admitting it 🤦.
    1. Bash & POSIX Shell
    2. ����Rs
       • I love its honesty: It has abstractions that are leaky by design.

       Rust [is] both as low-level as C, and as high-level as Lisp, whereas most other popular languages are stuck somewhere in the middle.

    3. Py.
       • My fav argument against Py's colons is:

       The colons are an extra visual clue to scanning the blocks. As such, they improve readability, one of Python's main strengths.

       Then Opening and closing braces should be called an "extra visual clue to scanning the block" in C++ and Java? Because they improved readability. Braces ({) then is C++, Java's main Strength.

    4. TS. It should be top#3 (mostly because of conditional types), but:
       • Py & Rs have better support for iterators
       • TS sits in an "awkward middle" between "type-safe scripting" (JSDoc) and "amazing dev-xp, requires building" (Rs)

  • in theory (idealized): This only takes into account the langs in isolation (type-system, syntax & grammar, stdlib, etc...):

    0. 🦀Rs. For everything.
    1. Any lang written in shapes that intuitively correspond to their semantics (such as BF dialects, and modern APL derivatives)

• 🧠Expertise: This takes into account my knowledge of the lang (and everything directly related to it), and my experience making useful, efficient, and correct/safe software in it. This is subject to D.K., I'll try my best to list in an accurate order:

  0. A.R.T. REs, I'm expert at ⚡optimizing them 🚀; DSV (almost any dialect).
  1. AM
  2. JS
  3. TS
  4. 🦀Rs
  5. POSIX sh
  6. Bash
  7. MKSh
  8. Py
  9. Scratch
  10. HTML5
  11. CSS3
  12. SVG1
  13. BF

• 👀Interested

  0. 💾Assembly
     • UVM
     • RISC-V
  1. Bend & Kind, because of HVM
  2. 🕊Ada
     • It statically-checks ranges at the type-system level! something that Pkl does, but Rs and TS don't:

     -- 32bit target arch
     type Integer is range -(2 ** 31) .. +(2 ** 31 - 1);
     -- I love this so much that
     -- I hate Py and Rs in comparison 😭

  3. (Common Lisp)

Editors

0. ❤Fav & fluent: hx
1. past experience: MS VS-code/Monaco

OS

• Using

  0. Debian 12.5 Testing (Bookworm/Trixie)
  1. Android 12.0 (can't update)
     • AOSP (without Gapps)
     • S One UI
  2. MS Windows 11
     • Despite using it my entire life, this beast is so bloated/complex that I know less than ~1/8 about it

• 👀Interested

  0. Nix
  1. Redox
  2. PM

Browsers

• Main: Moz Firefox
• Windows: MS Edge

Terminals

• Linux: GNOME Terminal
• 👀Interested
  • GNOME Console
  • Alacritty
  • Kitty
• Android: Termux