is a service or product receiver only a customer if they are paying money?
and Firefox still does not have proper PWA support
I recently had to learn about that, targeting PWA. :(
When I read "you can install an extension for it" I thought that would be simple enough. But that extension then requires an additional Firefox installation which causes it's own share of problems. (Comparatively complicated setup process despite simple walkthrough wizard with installer integration, program shortcuts being added, Firefox onboarding being triggered in the PWA.)
Using Mitchell's donation we'll be able to to offer Jacob Young a full time schedule. As a reminder, he's the primary author of the C backend, x86 backend, LLDB fork that adds Zig support, and maintains the eZ80 toolchain on the side, all without even having the ability to bill full time yet!
I agree. The split and collective nature makes it hard to assess and fundamentally support though - which is what I was referring to in one point.
It's a statement of support of minorities. I think that's a pretty good, fair reason, and not "just to cause drama".
Not making a statement is letting the original statement stand.
But did it reach test or production environment yet? Or will it die in development environment.
Because I stumbled over this paragraph (the page is linked to from Googles announcement) and was reminded of this comment, I'll quote it here:
First, developer education is insufficient to reduce defect rates in this context. Intuition tells us that to avoid introducing a defect, developers need to practice constant vigilance and awareness of subtle secure-coding guidelines. In many cases, this requires reasoning about complex assumptions and preconditions, often in relation to other, conceptually faraway code in a large, complex codebase. When a program contains hundreds or thousands of coding patterns that could harbor a potential defect, it is difficult to get this right every single time. Even experienced developers who thoroughly understand these classes of defects and their technical underpinnings sometimes make a mistake and accidentally introduce a vulnerability.
I think it's a fair and correct assessment.
The EU passed laws that require companies (under conditions) to ensure base requirements in their supply chain.
I think a digital equivalent could be possible and similar. Requiring reasonable security and sustainability assessment.
It's not very obvious or simple to enforce, but would set requirements, and open up opportunities for fines and prosecution.
Even C# has something that few people use, but it has something.
Huh? Are you claiming few people use NuGet?
Read/Inspect and contribute to FOSS. They'll be bigger and longer lived than small, personal, and experimental projects.
Study computer science.
Work, preferably in an environment with mentors, and long-/continuously-maintained projects.
Look at alternative approaches and ecosystems. Like .NET (very good docs and guidance), a functional programming language, Rust, or Web.
That being said, you ask about "should", but I think if it's useful for personal utilities that's good enough as well. Depends on your interest, goals, wants, and where you want to go in the future.
For me, managing my clan servers and website, reading online, and contributing to FOSS were my biggest contributors to learning and expertise.
When you draw a parallel to social charity both are largely volunteer based and underfunded. And both have direct and indirect gains for society.
Physical charity often serves basic needs. I'm not sure selecting qualifying quality open source projects is as easy. Need and gain assessments are a lot less clear.
If it's about public funding distribution, I would like to see some FOSS funding too, but not at the cost of or equal or more than social projects.
How many FOSS projects actually benefit "millions and billions of people"? That kind of impact feels like it's few and far between.
unfortunately not for the Steam Reviews overall