I used and liked it for a few years, but now they started filling it with bloat ware again… switched to Firefox last month.

The language itself is great, but Microsoft the docs are sometimes horrible or outdated.

And most things feel like magic that you can’t or don’t need to understand. E.g. if you set up a modern asp.net project it’s some huge boilerplate with configuration files and what not…

Also standards often change… E.g. try figuring out what the best GUI framework is to create a full-fledged Desktop app in C#. There’s like a few different ones, and most are for basic mobile-style apps or not really mature. The best I found so far is WPF, which is kinda old though and everyone thinks it’s dead.

Unions only make sense when you are easily replaceable as a worker so you don’t have any barganing power on your own. As an individual IT worker you can usually tell your boss to fuck off if things get bad and just look for a new better job…

provider maybe?

Linux is a usable daily driver if you’re tech savvy enough.

So it’s not…?

The mobile app sometimes gets stuck while updating new photos, or just doesn’t run the upload in background even though it’s activated. The web app looks and feels great though.

In fact I managed to ditch Google for everything but I can’t find a good replacement for Google photos which I’m not using anymore.

Immich is trying to be that, but it’s still in heavy development.

Also here a comparison of multiple ones: https://docs.librephotos.com/docs/user-guide/features/

https://owncloud.com/getting-started/

or

https://www.onlyoffice.com/download-docspace.aspx#docspace-community

or

https://nextcloud.com/install/#instructions-server

I think we are actually saying the same thing though…? Tests should really only ensure functionality. It should be the language’s job to help you with obvious implementation errors (such as using a wrong value type).

My point was that without a type system you need an impossible 100% code coverage, to be sure that you didn’t accidentally mess up some variable assignment or parameter somewhere, since you have nothings to easily and automatically catch those errors.

A quick check everytime when you build / package the code is surely more effective than a human code review.

Also the difficulty of coding in a language where there isn’t any static type analysis still remains. How does it even work, do you have to do a manual text search everytime you change some existing function or class?

The trivial problem here being knowing what kinda of parameter some random function somewhere in your code expects… And your code not randomly breaking in production when someone changes that function after you already used it, unless you wrote unit tests that literally test every single line of code.

I mean, if you are a designer that needs it but doesn’t know how to download and crack stuff, 12$ might be worth that time.

That’s exactly the problem. You need learn how to game the system, instead of actually contributing to the network.

It’s failing because it can’t connect to some crypto web3 bullshit… It’s probably best if it doesn’t load tbh.

And Bountysource is also dead crypto shit. See: https://github.com/bountysource/core/issues/1586

The “open” management of bigger open source problems is a kafkaesque nightmare. If you want to help make something better and change it somehow, you have to go on week-long journeys trying to figure out who is in control of that part of the project, who you can ask for guidance, who knows anything at all…

E.g. once I wanted to help package a new version of a software for a big linux distribution… and literally all the (~10) mantainers apparently wen’t missing a few years ago. I managed to find one of the mantainers private reddit account and contacted them there, and they just made me a mantainer. And I still couldn’t do shit because there is another dependecy which also needs to be updated, but it’s mantainers are also all dead.

The effort of even getting to the point where you could contribute something meaningful, is like 100 times more than the effort of the actual contribution. It’s completely rotten.

But if unit tests that other people wrote unexpectedly break, you know that you changed things that you maybe didn’t mean to change.

Often it’s just a container for a bunch of related functions and common state variables for all those functions.

Rarely are classes actually used in the OOP way, where you then create many instances of that class…

Unless you are implementing some mathematical formula. Then link the paper and stick to its variables.

Code changes that could affect tests happen all the time. It doesn’t need to be a specific refactoring of that unit.