All hail the fork!

Once governments stop or reduce funding for the meat and dairy industries, prices will continue to go up and more people will be like you. At the end of the day, animal products (especially those from bovines) aren’t super sustainable and cost a lot more than we pay at the supermarket.

Generally, yes. I like MacOS more than windows because it’s at least *nix.

But to be honest I have no strong opinions on OS when it comes to work. I’ve used windows*/Linux/MacOS and none have stood out as far superior to get my work done faster or more efficiently.

I use MacOS with my Mac because that’s what’s installed out of the box.

The main things that seem to hold me back from working efficiently are programs that are required by the company to maintain their ISO accreditation like Microsoft “intune” or what ever it’s called.

*Only when required.

There are plenty of developers who use macs for work, me included. I mainly go with Mac for the build quality/battery life/performance though and also because my work pays for it so I don’t need to worry about the exorbitant price. I would agree that MacOS is pretty janky at times and it requires a few third party apps to be reasonable usable.

But I’m not really sure what you mean by useful bits? I don’t feel like I’m really restricted in MacOS. If there isn’t a UI element for something, you can probably adjust it in a terminal.

Yes! Love it!

You can even compile to a native executable these days I believe so you don’t have to have the .net runtime installed or bundled.

Check out fork - I believe it’s a one time fee but still has a nice UI and does most things I need without having to break out the command line. https://github.com/fork-dev

*Edit: Here is their website, rather than git hub page: https://git-fork.com/

I’m running a 3 pi cluster with k3s at the moment. The main benefit I’ve found is that all my pis run exactly the same software setup as a base so it’s easy to add new ones or replace/update one. I use a deployment management application to push my deployments too which means it’s super easy to redeploy everything if something goes funky.

A k8s cluster can run on a single host if that’s what you want. I’m not sure if it would be worth the virtualisation cost to run it on VMs in the middle as well. If you were only ever going to run on a single host I probably wouldn’t use k8s though, I would just run containers. 🤷‍♂️

This is exactly what happened to me. I was a team lead at my old job and I interviewed as a senior dev but got offered a standard dev position. In the end they offered me the same money as what I was making as a team lead so I took it and have never looked back! The reduced pressure and better work-life balance are so good. I now earn much more than I did at my old gig so 🤷‍♂️

Plenty more bugs to fix, don’t give up being a contributor!

My process is:

1. Check for an issue that describes the bug you’re seeing.
2. If there isn’t one, create one.
3. If you feel like it’ll be snapped up because it’s a relatively easy fix, comment on the issue saying you’ll give it a go.
4. Fix it!

There is still a chance someone might swoop in and fix it but this lowers the chances and it’s good to get into the habit of creating and linking Issues to your PRs.

Yep this is me. I love learning languages and I’m a software dev for my job.

I can see how you could think of the setter like Current?.Response.set_ContentType("text/json") and then if Current is null you just skip the assignment like you would any other method call.

It’s not currently possible because the null conditional operator returns a value not a variable. Looks like there was some discussion on stack overflow and a GitHub issue was created a while ago but it hasn’t had much activity recently.

I don’t agree with this one. The meaning of words change and that’s true of ‘Less’.

I generally don’t agree with these prescriptivist positions though.

When a GitHub issue is closed as complete it means someone has fixed the bug in the source code (or the developers have decided it’s not a bug). It doesn’t necessarily mean the fix has been shipped in a new version or that the server you’re connecting through has been updated to a version with the fix. In this case, they haven’t shipped a new version with this fix in it. I’m not sure what the delivery cadence will be but I assume a new version will go out in the next week or so and then once your server admin upgrades their server the problem will be fixed for you.

This is a known issue on the web ui - we’re looking into it.

Speaking of which, is there a r/fuckcars equivalent over here?