What? You shared the link.

Do you really use it or are you just adding an alternative to the conversation? It is an interesting concept (commutation) but not likely to supplant git.

I feel like I’m reading a different article than everyone else. The comments made me think the article would be adding advertisements, but it seems to be trying to find a way forward to facilitate advertisements while maintaining privacy.

Without technical details I’m not sure that’s a bad thing. I know lemmy is largely “Mozilla bad”, but I’m just not sure the comments are in line with the proposal.

It does mean something. It may not have enforcement teeth, as it is a strictly diplomatic body. However, it still illustrates the state of things and has an impact on international relations.

obsidian.nvim

It runs in browsers. It… isn’t poop? I don’t know. I’m all out of ideas.

I guess I’m just lucky, but I’ve gotten nothing but thoughtful support on Arch forums and Stackoverflow. If you read the article How do I ask a good question?, it works very well. It seems harsh but coming with poorly thought out questions without debugging details makes it impossible to help.

PascalCase

I don’t disagree. I’m just saying the distribution of workload has an impact on what looks a good idea or too hard.

Because it changes the risk benefit profile of the choice. Imagine that your backend is 70k hours of work and your interface is 1k hours. Managing two interfaces isn’t going to seem like nearly as big an ask so other variables may get a higher weight. Of course those numbers are contrived for the sake of explanation, but if you still don’t think there are any circumstances in which others may value the benefits of native applications over cross platform applications, that’s fine. My point is simply that it may not seem like the trouble of managing two frontends is as insurmountable as you may think.

But I have a hard time believing you don’t think it is possible that there are any situations where one might reasonably believe it worth it.

Sure. Bitwarden provides its own backend. So that backend represents some portion of their code base. In the case of Voyager, Lemmy provides the backend. So that backend isn’t a portion of your code. So Voyager is 100% frontend. Bitwarden is < 100% frontend.

Recognizing you as a PWA developer; and a damn fine one, I get your take. But surely you are aware there are limitations to using PWA’s or other cross platform libraries. Sometimes maintaining multiple UI’s is the right choice. Especially if very little of your code is actually the front end. For you, Voyager is pretty much 100% front end, so that’s 100% of your code. But for Bitwarden, the interface is a much smaller proportion.

Well… it’s a correct phone number. So that kind of undercuts your message.

The overlap between people that write C and people that write JavaScript is negligible.

It’s worth going hungry in the dark. Lawyer up and hit the gym. JS doesn’t deserve you.