![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/028151d2-3692-416d-a8eb-9d3d4cc18b41.png)
I’m not up to speed on this issue, but it seems like the solution is to push forward with making the readers work in Wayland? Is there a technical issue with Wayland’s design that prevents readers from working properly?
I’m not up to speed on this issue, but it seems like the solution is to push forward with making the readers work in Wayland? Is there a technical issue with Wayland’s design that prevents readers from working properly?
That sounds awful. We shouldn’t support that kind of invasive tech for any reason.
That’s perfectly fine for some things, but for most people letting their browser choice dictate what sites they use is backwards
Did you forget the ./s or something? Lemmy itself is developed on GitHub, as are plenty of other “valuable” open source projects. To pretend nothing of value is built there is putting your head in the sand.
If you’re developing software on GitHub you have a chance at getting some useful feedback, bug reports and maybe even PRs. Like it or not, the network effect is real.
You can easily migrate custom domain that to proton for email, calendar, and drive. What you’ll struggle with is docs and sheets.
Future Idiots.
Patent Pending.
Options and competition are good things for consumers. Not sure why you would be against that.
Proton drive has windows and Android clients that work well. I’d love a Linux client for drive and for them to fix the photo upload issue on android, but eventually those things will come.
Or maybe the 512kb.club a more reasonable balance between 250 club and the 1mb club.
Also with a view: jankfree.org for a similar focus on performance.
Yes. You can. I have a personal site that is using nuxt static site mode and it renders extremely fast and clean output.
Check out https://250kb.club all performance sites focused on speed and small size.
We need caldev through the bridge app for use in thunderbird and other apps.
Check out Avalonia. It’s like cross platform WPF. Not winforms, but still pretty good and easy to start with.
I mean, I can fix them, but not because I’m a programmer. Makes it hard for normies to understand the difference.
I don’t understand the question. Mozilla, or Firefox rather supports pwa on android, they dropped it from desktop Firefox for reasons that aren’t clear to me. I’m not sure how it would play out on iOS. I guess we’ll find out here soon enough.
Money. They don’t get a cut of a pwa app.
Seems the second group is a vocal minority. This feature helps the first group, but doesn’t help the second group.
According to Signal, the first group is the larger group and this helps the most users of Signal.
Could it be better? Sure. This is still a good step in terms of privacy, even though it doesn’t really improve anonymity.
I think if you look at your average “package” from GitHub, that is published to npm, nuget, or the associated language rep, by and large they’re not making any money.
Sure big projects are making money and have paid development teams, but that’s not true at the individual library level in many cases.
Wait, are you seriously overlooking ASP.NET and suggesting c# tes learn typescript and node to build web apps?
I get that it’s a hypothetical, but typescript and node shouldn’t be the first stop on the we need to build a web page train for folks already in the c# wagon.
That sounds awful. And a major loss to accessibility. Here’s hoping one of the standards gains traction as the one path everyone can agree on.