functional programmers when they look at their code 2 years later

There’s lots of valid reasons for this.

Imo the biggest one people don’t account for is this: Dev salaries are incredibly high. if you want fast performance the most optimal way would be to target the platform and use low level native code, so C++ or Swift.

It would cost you like 20x more than just using electron and it will cost you bigly if you have multiple platforms to maintain.

So it turns out having 1 team crunching out an app on electron with hundreds of dependencies is cheaper, naturally that’s what most companies will do.

Don’t want to use electron ? Then it’s kind of the same issue except this time you’re using Java and C# and you have to handle platform specific things on your own (think audio libraries for example). It’s definitely doable but will be more costly than using a cross platform chromium app.

they could have just called gims or gim

naming stuff is important

using threads to reduce cpu usage ? in what world ? if you can parallelize tasks you will always increase the workload done.

WSL, if not then msys2/git bash at bare minimum

Poweshell 7 is okay if you have access to it but regular day to day shell scripting is like as 10x more verbose with powershell than bash

I just use WSL at work, extremely fortunate to be able to despite IT locking down everything as much as possible

I will say. if you have no idea at least clone your branch so you can experiment on it.

I started with nano and I hated it, I didn’t understand what anything meant in the bottom bar, like what is ^X. Unironically vim was easier to understand. I know what it is now but as a new user I didn’t like using it.

I’m sure emacs is great but I learned about vim and neovim first so it’s kind of a done deal already, not a lot of us Linux users are open source enthusiasts with so much time that we can noodle in all different flavors of text editors.

vim works great for me shrug, if emacs works great for you then awesome

I love C and C++ and I talk to someone else who does (comp sci grad) but he’s hugely biased against rust and says shit like “rust is cringe it has training wheels, just be good at C”

it’s like a weird tech anti-intellectualism

that’s IIS as well, I think it’s because we had our severs configured in a reverse proxy and hitting IIS and failing before the http serverhad returned a response caused the 502 error, completely useless error.

(not very experienced with server configs so forgive me if the language isn’t 100%)

that’s everyday with the legacy web app at work, it crunches up code in a templating process and all the errors become either completely meaningless or just “error 500”

well, no. everything is a god damn web app because everything runs browsers.

so why write native (device) applications if the device can run a browser ? just write code for the browser, which also runs on desktop. now you have a cross platform app without needing 5 different teams

Yep, I was shocked to see that there is no defacto 1st party framework and during my time searching online I found lots of “use x, use y, no y is dead and none uses it, no x is terrible” which is how I found Avalonia.

I still don’t think there’s a solid Windows gui framework, but I haven’t looked in years.

pretty much every windows GUI framework is trash or a pain in the ass to deal with except for Avalonia (my beloved), but it’s more cross platform.

I’m not sure if this is 100% real but it very well could be. although imo makes me think of skill issue (not because the system makes sense, but these problems don’t really seem like problems to me, just minor set backs)

every time I see this it always follows with comment that reopens the issue. inactive != resolved.

that’s why I’m so on the fence about spamming my tech skills in resume. on one hand it’s completely factual and is probably favoured by whatever AI garbage is processing the resume.

on the other hand to the human that reads it. it’s probably just dumb and hard to prove, they’re not going to test me on 20 competency skills for the things I have listed

that’s modern dev for you. least optimal solution but the most hyped. call it hype driven development

> someone nitpicks word you used in a variable declaration

> you change it

> someone more senior says the former made more sense

> this goes on for far longer than it should

> eventually you get a real review from someone in your team that identified something actually needs to change

> you change it and re request reviews

rinse and repeat

that’s exactly why I’m saying this. I know from experience helping other devs with git issues it’s always because they’re using a GUI alternative to the CLI and they’re clicking on things they don’t understand

let’s turn this into a constructive angle for future devs and current juniors: just learn git cli, I promise you it is much simpler than it seems.

all those memes about git having like a thousand commands are true, but you really will only use like 7 at most per month.

learn push, pull, merge, squash, stash, reset, im probably missing like one or two

I promise you again: it is much simpler than it seems. and you won’t have to use these stupid git GUI things, and it will save you a hassle because you will know what commands you are running and what they do

short disclaimer: using git GUI is totally fine but low-key you are missing out on so much