I’m not sure that’s a hot take outside early uni programmers.

Never attribute to malice what can be attributed to ignorance. They probably really do care but have little formal education and also the algorithms have decided to send them to a particular bubble of the internet.

What are those?

Backing in with a backup camera is easier, and pulling out forward is much safer. Once in a parking lot I nearly started backing out when a child dashed in front of my camera/rear bumper and I was disturbed by the possibility of what could have happened in another timeline.

As someone who wants to use Kotlin or Scala, is there another way to get around these two? Coming from .NET or NPM I found both of these to be terrible.

I am unsure just how revolutionary this feature is, though I am definitely interested in trying it and can see it’s value. I’ve somewhat gotten away from Jetbrains, but I do still use and promote Rider for C# development so this is potentially a nice addition for my professional life.

Is this something you want to run manually or automatically? If you want to run automatically either look into dotnet service workers, or run the console app with a crontab.

You can use https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish to create an executable. Then you would just transfer the resultant files, or file if you publish as a single executable file.

Firstly, consider spending some time with your phone camera. There are apps that should allow you to manually adjust ISO and shutter speed. Most phones aren’t going to have good RAW support or allow aperture adjustments, so you will need to focus on a specific set of things. Read or watch videos on artistic ideas like composition and color. When I was first getting interested in photography I did this for about 6 months just to be sure it actually held my interest long enough to justify spending money.

I would recommend reading this:

https://www.rtings.com/camera/reviews/best/by-type/mirrorless-beginners

Personally I would pay attention to the Sony and Fujifilm lineups. If you need a bit more portability then also consider Lumix and Olympus/OM.

I would recommend avoiding the RF(Canon) line for beginners due to the limited and expensive lens selection. I say that as a Canon R6 owner.

Do you think the people who built these platforms are teens? I’m a 27 yo engineer and Marxist through and through. Just because workers unions of the past were overturned by tyrants and capitalists alike, doesn’t mean the basic ideas weren’t sound. The system in which I am forced to participate in is fundamentally flawed.

All of those things are by design

And this makes sane programmers sad.

I have a R6 body with some lenses. First and foremost you should confirm the lens lineup is what you want. There really aren’t any practical third party lenses for the RF mount, so what you see on Canon’s site is what you should plan for. For me the lenses are fine, though I would be lying if I didn’t mention my jealousy towards the X, E and L mount lense collections. The R6 body does two things well in my eyes: low grain high iso and superb IBIS. Personally, coming from an EOS-M system, these were the primary reasons I was wanting to upgrade in the first place. That being said, the R8 is now out and for the price I think I would go with that if I were buying today. As for other cameras, I find Canon cameras to be infinitely more comfortable than most others. Judging by pictures I’ve seen, perhaps Nikon or Lumix cameras might be fine these days, but the Sony and Fujifilm cameras I’ve tried were designed for either aliens or small hands. Neither of what apply to me.

Also regarding price differences, NOTHING in these price categories are going to be 1:1. This applies to literally any kind of non-essential good. After a certain point the value/dollar exponentially decreases.