is a service or product receiver only a customer if they are paying money?
Kissaki
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!
If Firefox was a better funded and more competent alternative to Chrome we wouldn’t even have this whole Manifest v3 mess since Chrome would just lose all their users.
I don't think that's an issue of competency - which I understand as functionality/feature parity in this wording.
Chrome gained and became this popular likely entirely due to Marketing and big-corp ecosystem network effect through pushing it - through Google, Google Docs, and related Alphabet services.
I don't think Firefox was every really inferior. I've always preferred the dev tools and a few other things over Chrome. There was merely a time where performance was worse, but that likely only mattered in benchmarks - and marketing.
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.
oh, that's a cool website
adds it to bookmarks and search bookmarks
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?
unfortunately not for the Steam Reviews overall