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?

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.

Is your suggestion that people should? Isn’t Rust the more realistic, effective solution because it forces people to do better? Evidently, “correct memory safety in C/C++” didn’t work out.

Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave.

What is Tails?

and Tails, a portable operating system that uses Tor

Formatted, so I can read it

Exception in thread "main" java.lang.NullPointerException: 
 Cannot invoke "String.toLowerCase()" because the return value of 
"com.baeldung.java14.npe.HelpfulNullPointerException$PersonalDetails.getEmailAddress()" is null
 at com.baeldung.java14.npe.HelpfulNullPointerException.main(HelpfulNullPointerException.java:10)

Damn, that’s a long list. Looks like a lot of work to collect and prepare.

I was looking for more of an overview of it and selected them from the headlines:

1. 2014: Completely broken IndexedDB implementation
2. 2015: 100vh (100% viewport height) means a different thing in mobile Safari to everywhere else
3. 2016: <body /> with overflow:hidden CSS is scrollable on iOS
4. 2017: Safari incorrectly blocks localhost as mixed content when accessed from an HTTPS page
5. 2018: OS 11.2.2 broke WebAssembly
6. 2018: Safari 11.1 broke MessageChannels
7. 2019: Audio stops playing when standalone web app is no longer in foreground
8. 2019: PWA in iOS uses old assets after publishing new servicerWorker/assets
9. 2020: Add Fullscreen API to iOS (& display fullscreen)
10. 2021: Safari shipped blob.stream(), crashes with a NULL pointer exception
11. 2021: Appending an element to the shadow DOM in many cases hard crashes the browser process
12. 2021: LocalStorage is broken when a page is open in more than one tab
13. 2021: IndexedDB APIs hangs indefinitely on initial page load
14. 2021: Fetch request streaming is implemented just enough to pass feature detection, but it doesn’t actually work
15. 2021: IndexedDB API information leaks
16. 2023: Notifications API: support for the badge, icon, image and tag options
17. 2024: On-screen keyboard does not show up for installed web apps (PWAs) when focusing a text input of any kind
18. 2008: Focus events for non-input elements behave differently in Safari to every other browser
19. 2012: Using border-image with border-style: none is rendered completely wrong
20. 2014: WebKit doesn’t calculate padding-top/-bottom: n% correctly
21. 2014: Pointer events should allow for device-pixel accuracy
22. 2017: Support for 120Hz requestAnimationFrame
23. 2018: Some Fetch requests incorrectly completely skip the service worker
24. 2020: Safari 14 shipped a broken replaceChildren() method, which caused glitches in Construct.
25. 2020: When leaving current scope of PWA, back button incorrectly reads “Untitled”
26. 2020: Safe-area-inset-bottom still set when keyboard appears
27. 2020: Support for background-attachment: local has suddenly completely disappeared
28. 2021: IntersectionObserver and ResizeObserver fire in incorrect order
29. 2021: Mousemove events fire when modifier keys are pressed, even if the mouse isn’t moved
30. 2021: Scrolling in home screen apps incorrectly latches to document
31. 2022: WebM Opus support is inconsistent in Safari
32. 2022: Installed web app with viewport-fit cover causes overscroll issues, breaks position fixed and -webkit-fill-available
33. 2023: iPadOS: Viewport doesn’t correctly restore after dismissing software keyboard for installed web apps
34. 2023: iPadOS: window loses focus when dismissing the keyboard, breaks Page Lifecycle API
35. 2024: Svh and lvh are incorrect on iOS in third party browsers

let a = ''
for (let x of document.querySelectorAll('h3 a[title]')) a += x.title + "\n"
a

Now that you say so, I feel like I’ve read about this before. In comments about Diatraxis/one of them years ago. :)

I’m using the website / native website interface. It’s at least possible there to edit the post and url. May be different for “Lemmy clients”.

I like that even here on Lemmy, with inline code format, colors.ini is not being colored but color.ini is. Great symbolism for your issue.

deleted by creator

Maybe something to add to the side-bar?

The linked post doesn’t seem like that good of a reference that I would put it in the sidebar. IMO it could be done better. But if you mean to say, something like it; yeah, the .NET environment is vast and can be confusing, especially when new to it. An overview or reference to one makes sense.

I suppose the term “.NET” encompasses both, but most of us that write and speak in this space tend to use “.NET Framework” for legacy, and “.NET” for modern .NET.

there’s the whole “.NET Core” thing

Before around net7, the open source cross platform non-framework dotnet was called Core. net6/7/8 is the .NET Core technology, but Core was dropped from the naming.

Now, .NET may refer to that modern dotnet tech, or .NET Framework. Presumably, the latter is referred to only in contexts where it’s obvious that .NET Framework is meant.

and .NET Standard (2 versions). […] Are those relevant in the world right now, today? Hopefully not really!

.NET Standard is still relevant for libraries that target/publish for both .NET Framework and net6+. .NET Standard is the cross-platform baseline.