SaaSHub helps you find the best software and product alternatives Learn more →
Top 23 Proposal Open-Source Projects
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
DOLIBARR ERP & CRM
Dolibarr ERP CRM is a modern software package to manage your company or foundation's activity (contacts, suppliers, invoices, orders, stocks, agenda, accounting, ...). it's an open source Web application (written in PHP) designed for businesses of any sizes, foundations and freelancers.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
rfcs
This repository contains proposals, standards and documentations related to Nervos Network. (by nervosnetwork)
-
unicode-proposals
Proposals for new characters to encode and canonic character sequences to register
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Emacs' helm is maintained by one maintaner for 11 years long | news.ycombinator.com | 2023-12-22This is surprisingly common. The other example off the top of my head, a single maintainer of a very popular project who had to temporarily abandon it due to lack of funds, is Denis Pushkarev (zloirock) and core.js (https://github.com/zloirock/core-js/blob/master/docs/2023-02...).
The majority of OSS projects have most of their contributions by one person (the project leader), and the vast majority of OSS contributors don't do it for their job. It seems nearly every single popular OSS project is like this (one unpaid, maybe sponsored, volunteer doing most of the work); it's not even worth listing projects and names, because you can just pick a couple projects you know and I bet at least one will be an example. Fortunately, most of these people seem to be well-off (probably in part due to the quality of programming jobs), but every once in a while there's someone who's not so fortunate. It should be more common to sponsor maintainers, especially if they are asking for donations provided they can prove that they really need the money (the world we live in, some people who have plenty fake issues to solicit donations, then others who genuinely need and deserve the money are scolded and left unfunded because of them).
The proposal of "syntactic tail calls" to provide an explicit syntax for tail calls, co-championed by committee members from Mozilla (responsible for SpiderMonkey, the engine of Firefox) and Microsoft, was a response to these concerns. However, this proposal is now listed among the TC39's inactive proposals, possibly due to diminished interest, which may stem from the infrequent use of tail recursive functions in JavaScript.
Current Status: You'd have to check the TC39 proposals repository or the official proposal text for the most recent status. As of my last update, it had not yet reached Stage 4 (final stage) of the TC39 process, which means it wasn't part of the ECMAScript specification yet.
std::ranges is in c++20, but you can pull in the library it was based on if you use 17 (https://github.com/ericniebler/range-v3)
Counter to this post, as soon as I read the title I knew what this was, & I knew it was speaking exactly to something we've wanted for a long time. This is asking for more official & better supported https://github.com/rbuckton/reflect-metadata .
TypeScript is a compiler. It has a lot of type information during compilation. We could write that type information out into a file. Instead what we do is throw that information out when the compile ends. Taking all that typing information & throwing it away at the end of compile time is a bad dumb & silly limitation. Especially for a language like JavaScript, which historically could be semi-proud it had such a strong Everything Is An Object philosophy running through it (such as the malleable prototype-based inheritance system); so much type information should be on that Class object. Reflect-metadata for example defined new methods on Reflect to store this metadata.
I could not be more delighted to see the pennon of this website go up. We needed a rallying point for this. We needed a rallying point for keeping class data around. A rallying point for enriching the runtime with good actionable data is a good rallying point.
It's not what's afoot here, but I think you're a bit off-base about the impossibility of adding even some type-safety. We might not be able to get exact TS type safety. But we can definitely build some safety in. Owing to the malleable prototype-based type system in JS, we can add getters/setters to objects to do a lot of type checking. This doesn't even begin to explore the possibility of what we might do with es2015's proxies, which could allow even more interesting checks to be layered in. I also wish JS had an official AST (and renderer), so had more official options for code-rewriting that might let us weave in type checks.
What we can do as programmers is limited by what we have at our disposal. Not throwing out all the typing information, keeping it around at runtime, opens a lot of interesting doors.
Project mention: Bring garbage collected programming languages efficiently to WebAssembly | news.ycombinator.com | 2023-11-03It may take some time for WasmGC to be usable by .NET. Based on the discussions the first version of WasmGC does not have a good way to handle a few .NET specific scenarios, and said scenarios are "post-post-mvp". [0]
My concern, of course, is that there is not much incentive for those features to be added if .NET is the only platform that needs them... at that point having a form of 'include' (to where a specific GC version can just be cached and loaded by another WASM assembly) would be more useful, despite the pain it would create.
[0] - https://github.com/WebAssembly/gc/issues/77
npm workspaces plus Wireit works far better than Lerna, in my experience.
https://github.com/google/wireit
Wireit's ability to specify actual script dependencies, do caching (and on Github actions), and it's long-running service script support make it much more useful and comprehensive than Lerna.
I agree that this should be built into npm. There's an RRFC for it here: https://github.com/npm/rfcs/issues/706
Project mention: No installation required: how WebAssembly is changing scientific computing | news.ycombinator.com | 2024-03-12Similarly for threads: https://github.com/webassembly/threads
Exploring two approaches to enhance [Cells Commitments](RFC: Cells Commitments rfcs#424) Streamlining historical record storage methods Optimizing Merkle Mountain Range (MMR) storage read and write processes WIP: refactor: implement append-only tree sparse-merkle-tree#47
Project mention: Why could Apple possibly not have the Confederate flag emoji? | /r/facepalm | 2023-05-28Because... not wanting to have to deal with racism? News flash: There's no official ISO 3166 code for a confederate flag, regardless of IOS or Android. You're not typing one.
A completed implementation of memory64 for memory-hungry applications.
Project mention: Proposal: Signals as a Built-In Primitive of JavaScript | news.ycombinator.com | 2024-03-31I have to admit: you're perfectly right here. React of course always relied on mutable state in it's implementation – just so we don't have to. I derailed a lot here to keep this funny thread going ;) I'm still not with you on your definition of "functional", since you treated it synonymously with "purely functional". Functional means just made by applying and composing functions, and react UI is created exactly like that. There is an awesome algebraic effects proposal[1], which will hopefully will be added to JavaScript one day, then react will make use of it to become purely functional.
1: https://github.com/macabeus/js-proposal-algebraic-effects
Project mention: Bring garbage collected programming languages efficiently to WebAssembly | news.ycombinator.com | 2023-11-03Interesting article, thanks!
Notes on the issues mentioned there:
* The need for a manual shadow stack: This is fixed in WasmGC (in the same way it works in JS, as the link mentions).
* Lack of try-catch: This is fixed by the Wasm exception handling proposal, which has already shipped in browsers, https://github.com/WebAssembly/exception-handling/blob/main/...
* Null checks: Mostly fixed by WasmGC. The spec defines non-nullable local types, and VMs can use the techniques the article mentions to optimize them using signals (Wizard does, for example).
* Class initialization: This is a difficult problem, as the article says. J2Wasm and Binaryen are working to optimize it through static analysis at the toolchain level. Here is a recent PR I wrote that makes progress there: https://github.com/WebAssembly/binaryen/pull/6061
* The vtable overhead issue the article mentions may be a problem. I'm not aware of good measurements on it, through. There are some ideas on post-MVP solutions for method dispatch that might help, but nothing concrete yet.
* Checks for null and trapping: There has been discussion of variants on the GC instructions that throw instead of trap. Measurements, however, have not shown it to be a big problem atm, so it is low priority.
The author is right that stack walking, signals, and memory control are important areas that could help here.
Overall with WasmGC and exceptions we are in a pretty good place for Java as emitted by J2Wasm today: it is usually faster than J2CL which compiles Java to JavaScript. But there is definitely room for improvement.
We will soon support WASM imports (`import source foo from "./foo.wasm"`). [1]
[1]: https://github.com/tc39/proposal-source-phase-imports
Support for multi-memory to deal with multiple memories in Wasm.
https://github.com/jupyter/enhancement-proposals/pull/103#is...
Papermill is one tool for running Jupyter notebooks as reports; with the date in the filename. https://papermill.readthedocs.io/en/latest/
Support for tail-calls to perform tail-call optimizations.
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
Proposal related posts
- Time, Space and Complexity
- Old CSS, new CSS (2020)
- Top 8 Recent V8 Updates
- No installation required: how WebAssembly is changing scientific computing
- WebAssembly: Adding atomics waits to the main thread is the right thing to do
- WebAssembly: Adding atomics waits to the main thread is the right thing to do
- At Least Skim The Manual
-
A note from our sponsor - SaaSHub
www.saashub.com | 23 Apr 2024
Index
What are some of the best open-source Proposal projects? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | core-js | 23,817 |
| 2 | proposals | 17,811 |
| 3 | proposal-pipeline-operator | 7,359 |
| 4 | DOLIBARR ERP & CRM | 4,889 |
| 5 | range-v3 | 4,011 |
| 6 | reflect-metadata | 3,125 |
| 7 | gc | 924 |
| 8 | rfcs | 716 |
| 9 | stduuid | 699 |
| 10 | threads | 667 |
| 11 | fos-proposals | 466 |
| 12 | proposal-cancellation | 262 |
| 13 | rfcs | 257 |
| 14 | unicode-proposals | 181 |
| 15 | memory64 | 176 |
| 16 | js-proposal-algebraic-effects | 167 |
| 17 | exception-handling | 142 |
| 18 | proposal-array-unique | 132 |
| 19 | proposal-source-phase-imports | 121 |
| 20 | multi-memory | 115 |
| 21 | enhancement-proposals | 113 |
| 22 | tail-call | 106 |
| 23 | function-references | 93 |
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com