Hi Tildes community,
I'm seeking your suggestions for spinning up Windows virtual desktop.
Allow me to set the context...
My offspring is in second semester of their first year of university, and needs to use Adobe Photoshop for one of their classes this semester. They don't use a regular laptop, and have been doing quite well at uni. with their beefy Ipad. While they have used photoshop so far on their ipad, there are some growing pains. Of course, they have access to super beefy desktop Apple Macs at their school's computer lab, but its a pain to get usage of them for a few reasons. At home, all my machines are linux except for my partner's which is an old clunker Windows laptop - which i am in progress of migrating themn away from that Windows machine towards linux laptop...Hence, I don't really have a solid, modern enough machine for my offspring to load Photoshop onto.

Then, I thought, hey, maybe i can spin up some Windows virtual desktop somewhere for my offspring to use photoshop on...Its only needed for about 10 or 12 weeks remaining this semester...and they only need to use it once per week for each week's assignments. I feel like as long as the virtual windows machine is beefy enough to suppoort photoshop workloads, it can get them through the semester...and then in summer i can decide if I need to buy them an actual laptop (like an Apple laptop, etc.).

So, may i ask of you dear Tildes community members...Does my approach make sense (of trying to use a windows virt. desktop)? And, if so, are there any recommendations for which provider to use, and how to spin these up? Like, should i try something via AWS or Google Cloud or Azure? Or, should i not even consider this virtual windows approach? I'm open to hearing any/a ll recommendations. If you have links to share for me to research, or if you actually wrote your own blog post on similar topic for example, i'd love to hear it! Thanks in advance!!

Today's problem description: https://adventofcode.com/2024/day/15

Please post your solutions in your own top-level comment. Here's a template you can copy-paste into your comment to format it nicely, with the code collapsed by default inside an expandable section with syntax highlighting (you can replace python with any of the "short names" listed in this page of supported languages):

<details>
<summary>Part 1</summary>

```python
Your code here.
```

</details>

I usually have a decently thick and protective case on my iPhone 15 Pro. But occasionally I use it without the case to see how it’s “intended” to be used. To be honest it doesn’t seem very usable. I constantly find my palm or fingers activate the screen on the lower right edge - which is surprising as MacBook touch pads have excellent palm rejection. I would have expected the same attention to detail and quality on the company’s flagship product.

Maybe I’m just not used to it and I’m “holding it wrong”.

What was your first programming language, what other languages (if any) do you know now, and what tips do you have for those trying to learn any of those? Whether those tips are for beginners or even advanced, to do with APIs, or if you've got a good library to share.

This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?

Previous topic - https://tildes.net/~comp/1jsx/my_even_smaller_keyboard_upgrade

I'm making this a new topic because this keyboard once again got me to think about a couple of interesting things in regards to both having a smaller keyboard and how to actually make that work. Plus while niche as hell I'd like to contribute some sort of topic to tildes every now and then. For this one i'll be rambling about some of the reasons I've stuck with these things, and the sorts of design concepts it's forced me to think about and problems I ran into (like where the hell the shift key is).

1. Power users and the Nav cluster -

The nav cluster is the Home/End/PgUp/PgDwn/Delete/Insert section and maybe the arrow keys below it on a standard fullsize keyboard. These keys are SUPER useful for text and other sorts of navigation, to the point that it seems most "power user" systems(IDE's or even things like vim, or vimum for browsers) just remap the functionality to somewhere that can be easily reached.

In fact moving the nav cluster and numpad to be somewhere easier to access, so i wasn't constantly moving my hand back and forth, was one of the main reasons I started looking into custom keymaps and eventually smaller keyboards. Being able to trivially hit Home/End without lifting my hands is just so much nicer.

I mention all this to show you the kind of thinking that originally went into me going down this rabbit hole.
In essence:
I wanted to type/navigate faster, oh you can use these keys to be faster, but wait, i'm only a little bit faster and it's MUCH more annoying because I constantly have to move my right hand back and forth, how do I stop that?

Thus i'm always somewhat surprised at how vehemently people can get about remapping keys. Having Up/Down/Left/Right on I/K/J/L with Home/End/PgUp/PgDwn on U/O/Y/H is super intuitive(right handed WASD, with home/end/pgup/pgdwn in line with their corresponding movement) and makes flying around the screen so much easier, and can also open up keybindings that were otherwise used with just porting all this functionality to keys you can easily hit.

2. Chords, and the first major problem -

I'm sure there's a more technical definition but for the purposes of this topic chords are anytime you're hitting one or more keys at once. Shift + a is a chord for A. Ctrl+Shift+Esc is a chord for opening the task manager on windows.

One of the things you don't instantly think about when you get into smaller boards is what chords are popular, and how adding layers to your workflow will affect them. You really want your modifier keys to be accessible at all times, and in a way that makes sense. I don't have a problem that since my Esc key is not on the base layer, the Ctrl+Shift+Esc becomes Ctrl+Shift+Space+Tab for me. To break that down, Ctrl+Shift are on all layers, Space, when held, is the modifier to go to one of my other layers, and on that layer tab becomes esc.

In short, I've added one extra key to the chord, and it doesn't bug me.

What DID bug me, was that with this smaller keyboard, I no longer had room on the left side to put all of those modifier keys. You'll notice that the chord can be easily hit with your left hand alone, and with my previous map, I had shift on the right side. So now I need two hands to hit this chord instead of one. Oh well, right? It's just one chord and I need to use both hands...., whatever?

3. Oh yeah, the mouse......oh shit -
While I do think that more software should be written to allow mostly keyboard interaction, the mouse still serves a useful purpose in my ideal world. Being right handed, I use my right hand for the mouse. Sure I have some mouse functionality bound on one of my layers, but that's not going to replace the speed and precision of the mouse.

And that brings me to Win+Shift+S on windows for taking screenshots. Or more precisely, for selecting an area to take this screenshot....using the mouse.

First off, if you didn't know about this chord and you're on windows, please use it, it's fantastic for those quick "no i mean this" moments where you're trying to send someone a picture of a problem.

Second, this chord SUCKED on my new keyboard layout. On any of my previous keyboards including a normal one, I could hit this chord with just my left hand alone, while I moved my right hand to the mouse to quickly select the area I wanted and then edit it (often drawing red lines around the buttons I needed someone to click on...again....as mentioned in the documentation......).

My new layout had shift on my right hand, and oh dear god did I quickly realize how many other little workflows suck when you need to use both hands to hit the chord and THEN lift up and move it over to the mouse. Most importantly, multiple line/file selection, now required me to move my right hand to the mouse, and my left hand to the right keyboard, so I could hold shift and select things.

Or in overly dramatic terms, lo i had flown too close to the sun and was falling!

4. Wandering in the dark -

For those that for some reason don't have the 5x3 Chiri CE physical layout memorized, here it is (bottom one).

First try:
Move shift to the top button of the left thumb cluster. This was currently tab, but clearly I needed shift on my left hand more. Tab cold go on the right middle, where shift had been, and shift can go where tab was. Problem solved.

No good. That key is often hit with my index finger instead of my thumb, making something like shift+t/g/b super annoying. Hitting that key with your thumb actually requires a shifting of your hands position, and thus feels unnatural.

Worse, the key below it is my space/layer button, so something like shift+ctrl+left, to select previous words(left in this case being space + j), was super uncomfortable to hit. Just moving my thumb up to hit both keys at once did not feel good as I couldn't properly apply pressure and it just felt weird, but I wouldn't be shocked if some people out there are comfortable with that.

Second try:
Ok, we'll just move one of the other 3 thumb keys on the left to the right and put shift there, probably the win key.

No good. Ctrl and Win (or gui/super/meta/whatever) are just as important as shift. That small cluster being close to each other on normal keyboards, so they're left hand control only, means that almost ALL programs assume as much and have built their default hotkeys around it.

Windows window movement and terminal navigation being two of the bigger ones that affected me. Further this still wouldn't solve my win+shift+S screenshot issue, as now i'm just moving the windows key over there. There's no way in hell i'm putting ctrl on the right side because that's also constantly used in assuming its on the left side for various hotkeys, shortcuts, and other behaviors.

Third try:
It was at this point I was entertaining finally looking into homerow modifiers and setting up tap/double tap modifiers instead of hold. I'm still skeptical of how useful any of that is (but being open minded because of course I was skeptical of all of this and now I preach it), and realllly didn't want to go down that road for all sorts of little workflow reasons I was worried it'd collide with.

5. The solution. Pinkies and two shifts -

This stumped for for about two days after I'd decided I just couldn't live with right shift (there were plenty of other awkward workflow things due to having the number layer key be the leftmost thumb on the right pad). I'd really been trying to practice getting used to hitting both thumb keys with my thumb, as I assumed that might be the solution, and unlike basically every other adjustment I've ever had to make for a keyboard, this just felt rough.

So I took a break and just thought about my previous and normal keyboards. Well, again, in those cases, all these chords assume you're using your thumb for one modifier, and your pinky for the other. Sooooo why not just do that?

Thus the solution was born:
MT(MOD_LSFT, KC_X)
MT(MOD_RSFT, KC_SLSH)

For the few of you who don't have your Via/QMK mappings memorized, this just says that if I tap the key in question, type z (or / for the second one), and if I hold the key in question, treat it as if I'm holding the shift key.

So my shift keys are now used by my pinky, just like normally. I have them on Z and /, so I can easily hold either for whatever chord. If I need something like ctrl+shift+z I can just use the right shift, and ditto for ctrl+shift+/.

Even better, this was already my natural inclination. It only took a bit for me to find out just how much faster and easier this was making things, as I already was used to the idea of moving my left pinky downwards to hit shift. In fact, it was even easier than normal. Every now and then I'll get zi instead of I because I didn't hold the key long enough for it to trigger the "shift" function, and I could get really messy and start screwing with how long the keyboard takes to recognize the difference between a press and a tap, but I'm super happy with it.

6. Conclusion -
My wife is right to judge me and I don't care from my superior position in typing valhalla.

I am a scientist who has semi-frequently written code in C (and other compiled languages like Fortran). When it comes time to compile, I typically tape together a Makefile from past projects and hope for the best, but even then I spend more time than I'd like to admit trying to figure out why my project is not being compiled or linked correctly. I've had a hard time finding any resources that aren't extremely surface level, or else are not behind some type of paywall. Can anyone recommend me some reading so that I can confidently write Makefiles and compile programs and actually understand what the different flags and commands are doing? I don't need extreme "under the hood" information as I don't intend to do things like write my own compiler, I just want to understand the process a little better. Help a scientist out!

This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?

This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?

This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?

We have this big project at work...an "all hands on deck" kinda thing that has us rank-and-file frontend devs working alongside our manager more closely than I'm used to. And it was fine, because I like the guy and he's been a decent manager. But this project is killing me.

On multiple occasions now I've written code, had it pass code review (often with his approval after a round of changes/guidance), and then every few days we get these massive re-write PRs from him where he completely rewrites large chunks of what we've done. It's leaving me feeling a few different ways:

1. Angry because how quickly your code gets replaced is a (imo, bullshit) metric used as a part of our annual reviews and promotion discussions
2. Doubting myself because in my head a good developer doesn't have their code rewritten that quickly.
3. Confused because features I thought I understood are constantly being rewritten leaving me wasting time trying to relearn how things work
4. Wondering what the point of writing code is if it's just going to be thrown in the garbage later in the week?

And like I'll be the first to admit I'm not the most proficient developer on our team. React and Typescript are relatively new concepts to me, despite a long career in web development. But I've been writing with it for about a year now and I had thought I was finally getting a good grasp on things. But now I'm wondering if I'm just an idiot? Is it imposter syndrome or have I actually somehow coasted through a 15 year career across various stacks and it's just now catching up to me?

Or is this just the nature of massive projects like this? We had a half-baked product scope to begin with and its getting daily changes with entire chunks of it not very well thought out by our PM. I can see how it would make sense that the more senior developer might see the need to refactor things when things are constantly changing and we're left writing code based on assumptions and half-written requirements. I'm also getting are comments on my PRs that request changes, but mid-comment he's like "I'll just take care of this because it's blocking me".

It's just really taking a toll on my mental health and how I feel about my job. I've been trying to find another job for a few months now, but I'm not having any luck. Job hunting sucks and when you're already demoralized as hell, it's hard to sell yourself to prospective employers.

Could really use some insight from other experienced devs, please!

This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?

This is a recurring post to discuss programming or other technical projects that we've been working on. Tell us about one of your recent projects, either at work or personal projects. What's interesting about it? Are you having trouble with anything?

I've been the sole developer for my company's website for over a decade now. It's gone through a bunch of evolutions throughout the years, but I've been sidetracked lately and have let things stagnate as far as maintenance goes. Now, I'm looking to do some upgrades for security purposes and I'm trying to wrap my head around everything.

Some facts:

• PHP 8.0.12
• MySQL 5.7
• Symfony 5.4
• Web server is currently Apache only because that's what I've always used. I'm open to nginx or other options.
• Running on a Google Cloud VPS with Ubuntu 20.04
• I also use Google Cloud Storage to host thousands of images

My first thought was to take baby steps and start by upgrading Symfony as much as possible. However, the next major version (6.0) requires PHP 8.0.2. Symfony 6.1 requires PHP 8.1. Symfony 7.2 (the current release) requires PHP 8.2. So, then it just makes sense to upgrade PHP to the latest version.

However, I am terrified of upgrading PHP in the current (outdated) Ubuntu environment. So I might as well upgrade the distro while I'm at it.

And then, MySQL 5.7 is no longer supported, so I might as well bring that up to date too (8.0, I believe).

There will be no baby steps. I'm gonna have to just upgrade everything all at once. Which then leads me to my next question: should I stick with the self-managed VPS, or is it time to look at something like Google App Engine or Fly.io that is a little bit more managed and "locked down" than what I'm doing right now? Should I look into just going with Docker instead?

Put another way, if I'm going to start from ~scratch, what's the modern best practice to host all of this, given that I'm going to have to upgrade a bunch of different things all at once? (Turns out the "baby step" of upgrading Symfony will actually have to come last since I need to hit these prerequisites first).

Please let me know if I've left anything out. PS, security is a pretty big concern for us because we manage user auth, so I'm all for anything the cloud providers can do to take some of that responsibility away from me.

I’m working on an “advice” blog post for tech people at companies that plan to abandon VMWare. The idea is to give the reader an idea of what to expect and to help them plan their migration. The article will be on a vendor site, but I’m writing it with editorial purity. The only promotional component is at the end, where we say, “We can help with that!” and link to a white paper or whatnot.

So, what should I include in this listicle? What advice is important to impart – and why is that important?

References and examples are welcome. Horror stories are good, too. I’m not planning to quote anybody by name so don’t be shy. (I don’t need to explain why they plan to drop VMWare. Nor will there be a discussion about possible replacements. This is a process story that happens before you choose a replacement product/vendor.)