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. Learn more →
Top 23 W3c Open-Source Projects
-
graphql-yoga
🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
csstree
A tool set for CSS including fast detailed parser, walker, generator and lexer based on W3C specs and browser implementations
-
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.
-
papanasi
🥯Papanasi is the Frontend UI library to use cross Frameworks. A set of components to use in Angular, Preact, Qwik, React, Solid, Svelte, Vue and Web Components
-
vc-data-model
W3C Verifiable Credentials Working Group — VC Data Model and Representations specification
-
rdf-validate-shacl
Validate RDF data purely in JavaScript. An implementation of the W3C SHACL specification on top of the RDFJS stack.
-
contact-picker-api-demo
An API to give one-off access to a user’s contact information with full control over the shared data.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Show HN: Dropflow, a CSS layout engine for node or <canvas> | news.ycombinator.com | 2024-03-21To reply mostly with my WPT Core Team hat off, mostly summarising the history of how we've ended up here:
A build script used by significant swaths of the test suite is almost certainly out; it turns out people like being able to edit the tests they're actually running. (We _do_ have some build scripts — but they're mostly just mechanically generating lots of similar tests.
A lot of the goal of WPT (and the HTML Test Suite, which it effectively grew out of) has been to have a test suite that browsers are actually running in CI: historically, most standards test suites haven't been particularly amenable to automation (often a lot of, or exclusively, manual tests, little concern for flakiness, etc.), and with a lot of policy choices that effectively made browser vendors choose to write tests for themselves and not add new tests to the shared test suite: if you make it notably harder to write tests for the shared test suite, most engineers at a given vendor are simply going to not bother.
As such, there's a lot of hesitancy towards anything that regresses the developer experience for browser engineers (and realistically, browser engineers, by virtue of sheer number, are the ones who are writing the most tests for web technologies).
That said, there are probably ways we could make things better: a decent number of tests for things like Grid use check-layout-th.js (e.g., https://github.com/web-platform-tests/wpt/blob/f763dd7d7b7ed...).
One could definitely imagine a world in which these are a test type of their own, and the test logic (in check-layout-th.js) can be rewritten in a custom test harness to do the same comparisons in an implementation without any JS support.
The other challenge for things like Taffy only targeting flexbox and grid is we're unlikely to add any easy way to distinguish tests which are testing interactions with other layout features (`position: absolute` comes to mind!).
My suggestion would probably be to start with an issue at https://github.com/web-platform-tests/rfcs/issues, describing the rough constraints, and potentially with one or two possible solutions.
Project mention: Show HN: I built a free in-browser Llama 3 chatbot powered by WebGPU | news.ycombinator.com | 2024-05-03Works for me.
WebGPU support is behind a couple flags on Linux: https://github.com/gpuweb/gpuweb/wiki/Implementation-Status
After thinking about the problem for a while I realised that I could enlist the help of CSSTree to do some of the work. The CSS Analyzer is based on CSSTree's AST, so I know how the thing works and the dependency is already on the page, so no need to download more dependencies. Prettier + Postcss cost almost 340kB to download, which isn't huge, but it would be nice if we could reduce that amount.
You can check why Mozilla and Apple have opted to not support this.
https://github.com/mozilla/standards-positions/issues/154
https://github.com/WebKit/standards-positions/issues/28
Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.
Project mention: Show HN: Standard-HTML – Check if your HTML is compliant with W3C standards | news.ycombinator.com | 2023-09-17
Project mention: Implementing OTel Trace Context Propagation Through Message Brokers with Go | dev.to | 2024-04-04The answer is Context Propagation. The HTTP example is a classic and W3C even covers it. The propagation is adding the important fields from the context into the HTTP headers and having the other application extract those values and inject them into its trace context. This concept applies to any other way of communication. Here, we will focus on message brokers and how you can achieve context propagation for those.
W3c related posts
-
Implementing OTel Trace Context Propagation Through Message Brokers with Go
-
WGSL Is Terrible
-
Why aren't we using highly efficient int8 calcualtions in quants? (maybe eli14?)
-
How to get Chromium working with the Vulkan driver on a RPi4?
-
Anyone has Chromium WebGPU working?
-
[Rust_Gamedev] WGSL est-il un bon choix?
-
gpuweb: Where the GPU for the Web work happens!
-
A note from our sponsor - InfluxDB
www.influxdata.com | 5 May 2024
Index
What are some of the best open-source W3c projects? This list will help you:
Project | Stars | |
---|---|---|
1 | graphql-yoga | 8,029 |
2 | wpt | 4,632 |
3 | gpuweb | 4,589 |
4 | open-ui | 3,201 |
5 | csstree | 1,836 |
6 | validator | 1,635 |
7 | awesome-webgpu | 1,349 |
8 | shifu | 1,204 |
9 | WeIdentity | 1,108 |
10 | ditto | 611 |
11 | papanasi | 577 |
12 | xgen | 292 |
13 | vc-data-model | 277 |
14 | EasierRDF | 258 |
15 | standards-positions | 232 |
16 | spatial-navigation | 199 |
17 | apca-w3 | 140 |
18 | Dom | 112 |
19 | rdf-validate-shacl | 90 |
20 | w3c-keys | 55 |
21 | contact-picker-api-demo | 5 |
22 | standard-html | 4 |
23 | trace-context-w3c | 4 |
Sponsored