just take fedora kde and swap the start icon with ms icon and call it a day. jk

i use git. got a tree alias a tree-like log. and an amend alias to add changes to the prev comit to keep the message

composition can help with all of that. factories, strategies, injections are all composition patterns that work fine.

business logic that repeats? extract it to it's own thing (class, function, etc) and pass it as a param to the supposed childs.

mvc? controllers don't need to extend anything, just have them accept the framework through the constructor and request and response as args. views? same. models? perhaps only if doing an active record, but a repo pattern with plain objects is a good pattern too.

I never seen a clean inheritance implementation for a decently sized problem. it mostly works for tiny ones.

I'm not reviewint that butload of code. Just today I had to rollback some shit I "reviewed" a month ago. Huge ass refactor. I reviewed for 1 hour and then I just yolo'd it.

I'm not reviewing anymore.

hopefully it doesn't have the full kde ecosystem as deps and can be used standalone.

i wish a more performing language would have this type system. the only other ones I know are Rust which is a bit strict and slow to dev on, and Haskell which is too much.

hahaha. just don't --continue at the last commit

DI without a tool/injector is just composition. just saying

if you use some php forum software, you can find hosting in the $5 range with cPanel. I remember hosting one 10 years ago with $3. good start, scale or migrate as needed if stuff picks up.

versioning and version dependencies are more manageable.

idk why aren't they using git clone --filter to clone a part of the repo and/or git sparse-checkout or at least git status . while in the subdir you are doing your work. what's the point of doing git status on the whole thing if you're working in a dir?

edge is chrome

idk my vim uses u U in visual.