Das geht ja noch viel tiefer als nur das falsch abstellen.

Der Typ regt sich ja auf, dass es Strafen gibt, wenn man Eigentum der Firma (Fahrtenbuch) irgendwo verliert, wenn man drinnen raucht und wenn man den Wagen beschädigt.

Also so ignorant und eingebildet muss man mal sein, dass man so einen Vertrag eingeht, gegen Bedingungen verstößt und dann die Vermieter als die Arschlöcher sieht.

I don't necessarily like a few takes in the comments here.

Vibes wise the Obsidian team seems to be great and they don't seem to have shown any reason why I should distrust them. I love FOSS but gifting others my work doesn't put food on my table, so in that sense they need to have a lucrative business model which they seem to have established.

I could use SyncThing, Git or other solutions to do synchronisation between my devices but I choose to buy their Sync offer, since I want to support them (they also have EU servers, which need to be GDPR compliant by law afaik).

The closest comparison I could make is NextCloud. NextCloud open sources their software, but they sell convenience. Sure, you could self host it, but paying them to do so for you may be more attractive. In comparison Obsidian is not really complicated to set up or maintain. It's literally just a MD-editor. So the only convenient thing to sell is synchronisation if you don't want to put a price tag on the software.

If they open source all their code, some tech wizard will implement a self hosted obsidian sync server with the same convenience as theirs in a day, and the company will lose their revenue stream.

We've all been burned by tech bros in one way or another, but I think it's ok for people to profit off of their IP. And they seem to be doing so with a positive vision. Feel free to let me eat my words if they ever go rogue, but that's my 2 cents.

It's so christians can eat bees during fasting. duh.

I mean yeah, funny greentext, fake and gay and all, but is that an actual thing that happens across the big pond?

If someone did that in Europe they'd be in serious legal trouble if the threatened party sues.

Hamster are much like lobsters, in that they just keep growing forever until they can't molt anymore.

If you don't laser explode hamsters, they would eventually be able to eat humans. Which is quite scary if you think about it.

Meme is funny, but that exception used as flow control hurts.

That's why he's not worried about stuff running out

While I certainly agree with you that discrimination based on sex is unacceptable im most contexts, I believe that gender exclusive spaces, unless they hinder people directly, sometimes are a good thing.

My dad is a mental health professional and founded a weekly 'only-men' self help group. He found that some things they talked about there wouldn't have worked with women involved. That group existed for about 5 years or so and helped quite a few struggling men.

So yeah, unless there's any maliciousness involved, I'd argue that gender exclusiity is not bad in every context.

Recently switched jobs from maintaining a 15 year old Windows Forms .NET Framework legacy codebase.

At the new job we stick to Clean Architecture, use unit and integration tests, have a code generation tool, actually make nice use of generics and use dependency injection. Also agile processes, automatic build tools, whatever. The difference is night and day and I'm so glad my ex boss fired me because I told him he's an asshole and his codebase is shit.

Ha! I'm partially looking at this issue in my bachelor's thesis.

It's not at all necessary to embed a browser, but it's really easy to transfer your web app to a "near native" experience with stuff like electron, ionic, cordova, react native or whatever other web stuff is out there. The issue is mostly that native APIs are complicated and relying on web views or just providing your own "browser" is a relatively easy approach.

Stuff like Flutter, Xamarin or .NET MAUI compile depending on the platform to native or are interpreted by a runtime. There's a study I use that compares Flutter to React Native, native Java and Ionic on Android and finds that unsurprisingly the native implementation is best, but is closely followed by Flutter (with a few hiccups), with the remainder being significantly slower.

The thing is. I don't think these compiled frameworks lag behind in any way. But when you have a dev team, that's competent in web development, you won't make them learn C#, Xaml, Dart or C++, just to get native API access - you'll just let a framework handle that for you because it's cheaper and easier.

Edit: To add some further reading. This paper and this one explore the different approaches out there and suggest which one might be "the best". I don't feel like they're good papers, but there's almost no other write up of cross-platform dev approaches out there.

Edit2: I also believe that the approach "we are web devs that want access to native APIs" may be turned around in the future, since Flutter and now also .NET offer ways to deploy cross-platforn apps as web apps. I'll get back to writing the thesis now and stop editing.

Eh, they can't be honest about wanting you to use the app to be able to collect your data better.