But did it reach test or production environment yet? Or will it die in development environment.

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.

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.

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: 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

git has 17 million options

proof needed /s

I wonder how many it actually is.

I've not seen those kinds of issues. Apart from some dedicated pseudo-/farm-projects.

But still, it has entirely lost its appeal or even viability to me.

I participated many years, until - I presume - it got too big. I was not able to find good projects, the contributions I made most of the time were not reviewed nor labeled hacktoberfest-accepted. An an extrinsic motivator, it became more frustrating than motivating.

I was tempted to disagree, but the Patreon subscription paywalls is a very good point. Are we doing less free work for the public good (or at least accessible to the public), or is it a prevalent niche that's very visible, without influence on those that volunteer work like before?

The thought I had before that was that maybe the creative output changed. People build in Minecraft and VRChat, in hosted platforms. This may be different to before, where mods were separate things and communities.

I still see a lot of voluntary open work. But I'm not confident in assessing it's prevalence or shift.

Can you search for the search?

extending the list

• You don't need JavaScript to build web pages
• You don't need JavaScript to publish web pages

For a desktop app I would go with none of those.

If cross platform is the goal, the more important question, and independent of the programming language, is which GUI framework you will use.

Your best bet, at least if you are looking for a stable GUI framework, the best candidate may be C++ and Qt. But that's a hassle in its own right - both C++ and Qt.

TypeScript will have some solutions for you, with web rendering as a desktop app. Golang will have Qt bindings or other more experimental/not thoroughly established+popular GUI frameworks.

My personal favorite ecosystem is .NET. It has an official cross-platform UI project MAUI, but without an official Linux target. Community extensions probably exist. Personally, I dislike the way the UI is declared and bound though (XAML).

My current interest, which I have not explored or validate yet, is using .NET but then host a web or Blazor app in it with Webview2. .NET supports cross-boundary programming, crossing web+managed/native development, and crossing web(HTML+JS)+managed.

Most of the time GUI and the framework technology is a hassle. Your question is too broad and unspecific, so there's not a good answer.

If it's not a "serious" project that you depend on [for your livelihood], pick and start with whatever [looks good or interesting] and go from there. If it is a "serious project" do a bit more GUI framework exploration and assessment, and pick and commit to something. If it's a big commitment or risk, do prototyping with your candidates for verification and assessment - beyond the most simple examples, and for your specific usage.

We are beginning a staged dissolution process that will allow our over 600 collectives the time to close or transition their work. Dissolving OCF will take many months, and involves settling all liabilities while spending down all funds in a legally compliant manner.

600. And it's not sustainable?

Open collective always looked successful, popular, sustainable, professional.

Really unfortunate for those 600. March 15 is very short term.

March 15 is the last day to accept donations. You will have until September 30 to work with us to develop and implement a plan to spend down the money in your fund.

One time passwords

Forgotten after one use