@retoor Those eyes make it look like you speak parseltongue

@atheist click handling was the last of my concerns when I thought about it, dealing with different screen requirements was more what I was thinking about, e.g. DPI, dealing with safe zones and those flavours of fun. Browsers have had plenty of performance for years, probably exceeding Unreal Engine's blueprints when that was originally released. Heck Node has comparable speed to Java if you look at stuff like this (but doesn't scale as well): https://benchmarksgame-team.pages.debian.net/...

Was it easy to setup? I have the eternal goal of setting up a NAS and setting everything up on it including, data backup, rendering, git, ml and whatever nonsense that I might find interesting

@wifi you can do it if you want it with Jetbrains by explicitly right-clicking on a folder and looking at the local changes, so it's got the best of both worlds

Did you ensure the body/html fills the page?

100vh and 100vw or 100% on the parent and then depending on needs then either flex, grid, transform, auto margins, position fixed + inset: 0 (I'm sure there are more ways but those work for me ~100% of the time, sometimes have to combine)

Will agree, learning flex makes it pretty simple the css tricks article is pretty good (https://css-tricks.com/snippets/...)

@greendev if it helps It's not types it's contracts, that's why type A with the same properties as type B are interchangeable. Then again, I've never been insane enough to do explicit typing for everything in Vue, also haven't used it in years 😅 (type inference is generally pretty good, and I can see the inferred type in intelij)

While any might get you chewed out, try unknown, or look at some of the meta types like Parameters<typeof annoyingFunction>[0] or using generics?

Hope that helps

@Demolishun that can still get you the "why didn't you add a comment?!??"

@jestdotty The problem is not the detail as far as I can tell, if I don't mention that I didn't do B, then the question comes of “why didn't you do it like this <B>”

@jestdotty I love having conversations about code/tools/methodologies/I think this would be cool, and have had them. The problem comes in when they choose to disagree with a sentence you said in the beginning, even though you address that direct concern in the next sentences.

e.g. This fixes problem X. It does it by doing Y. Considered doing it using A, B and C but problems QWE meant Y was the only feasible solution

"Why didn't you do B"

I do appreciate the conversation, what I don't appreciate when it holds up a PR for 3 days (human testing only happens post-merge 🥲) that sales is champing at the bit to get to customers/demo to CEO

@jiraTicket I agree with the sentiment, but it has only happened once in the ~5 years I have worked with him (the colleague who made the error).

Also the commit message not the PR message

Since you need to select the files to commit manually (mouse) first (or if you right-click on a file and choose to commit, it will focus and highlight the full input field). AFAIK you can't hit commit without manual mouse input (or tab over when you have the input in focus). It would be nice if it showed a warning though if it detected no input

@jiraTicket It's quite easy to disable (intelij's settings are fully searchable) but I imagine they have it as the default because most people don't care too much about the message. You can even get their AI package to write the commit message for you, and if I had to deal with him too often, I'd be tempted. Luckily, he doesn't/stopped touching the (normal) codebase I work on

Oh and squash and merge is enforced, so that commit message is "lost" anyway

This one has complained at a retro about "useless" commit messages because a colleague accidentally re-used the same commit message from a different branch when fixing a typo (intelij defaults to keeping the last message in the commit box)

You had me at React