SaaSHub helps you find the best software and product alternatives Learn more β
Top 12 HTML Standard 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.
-
vc-data-model
W3C Verifiable Credentials Working Group β VC Data Model and Representations specification
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: JavaScript fetch does not support GET request with body | news.ycombinator.com | 2023-11-21
Project mention: Ask HN: I found a security issue on a (known) website, should I report it? How? | news.ycombinator.com | 2024-04-08
What I said in my previous comment is observably true. Try making a demo where it isn't.
> A DOM node is a living mutable thing, but the JavaScript object representing that node is not.
The JavaScript object is mutable. The first example in the article shows this.
> That is also why a node list is not an array.
Modern APIs on the web return platform arrays (eg JavaScript arrays). https://webidl.spec.whatwg.org/#js-sequence - here's where the WebIDL spec specifies how to convert a sequence to a JavaScript array.
I'm fully aware of NodeList. There's a reason the spec calls them "old-style" https://dom.spec.whatwg.org/#old-style-collections
> I can understand how this is confusing if you have never operated without a framework, but otherwise itβs really straightforward
Sighhhhhh. I've been a web developer for over 20 years, and spent a decade on the Chrome team working on web platform features. Most of my career has been on the low-level parts of the platform.
Could it be possible that people are disagreeing with you, not because they're stupid, but because you're in the wrong? Please try to be open minded. Try creating some demos that test your opinions.
Project mention: Backpressure explained β the resisted flow of data through software | news.ycombinator.com | 2024-03-27Yup, this is what WHATWG's Streams spec[0] (linked in the article) says. It defines backpressure as a "process of normalizing flow from the original source according to how fast the chain can process chunks" where the reader "propagates a signal backwards through the pipe chain".
Mozilla's documentation[1] similarly defines backpressure as "the process by which a single stream or a pipe chain regulates the speed of reading/writing".
The article confuses backpressure (the signal used for regulation of the flow) with the reason backpressure is needed (producers and consumers working at different speeds). It should be fairly clear from the metaphor, I would have thought: With a pipe of unbounded size there is no pressure. The pressure builds up when consumer is slower than producer, which in turn slows down the producer. (Or the pipe explodes, or springs a leak and has to drop data on the ground.)
[0] https://streams.spec.whatwg.org/#pipe-chains
[1] https://developer.mozilla.org/en-US/docs/Web/API/Streams_API...
Semicolon (;) has no special meaning in a URL. You can ascribe it a meaning in your particular routing, but the spec has nothing to say about it.
https://url.spec.whatwg.org/
Project mention: Transcoding Latin 1 strings to UTF-8 strings at 12 GB/s using AVX-512 | news.ycombinator.com | 2023-08-21Be aware that with the WHATWG Encoding specification [1], that says that latin1, ISO-8859-1, etc. are aliases of the windows-1252 encoding, not the proper latin1 encoding. As a result, browsers and operating systems will display those files differently! It also aliases the ASCII encoding to windows-1252.
[1] https://encoding.spec.whatwg.org/#names-and-labels
console is not part of the JavaScript programming language. WHATWG has published Console Standard https://console.spec.whatwg.org/ though console is not defined in ECMA-262.
Project mention: persistent storage API on Firefox temporary extension | /r/learnjavascript | 2023-07-24You can use File System Standard https://fs.spec.whatwg.org/ to write data for that origin (Firefox doesn't implement File System Access API, nonetheless a File object can still be written to local disk using File API).
It's so frustrating how the chromium team is ending up as a gatekeeper of the Internet by pick and choosing what gets developed or not.
I recently come across another issue pertaining to the chromium team being not budging on their decisions, despite pressure from the community and an RFC backing it up - in my case custom headers in WebSocket handshakes, that are supported by other Javascript runtimes like node and bun, but the chromium maintainer just disagrees with it - https://github.com/whatwg/websockets/issues/16#issuecomment-...
HTML Standard related posts
-
Popover API
-
A Response to "Have Single-Page Apps Ruined the Web?"
-
HTML Attributes vs. DOM Properties
-
Ask HN: I found a security issue on a (known) website, should I report it? How?
-
Add Writingsuggestions="" Attribute
-
Streaming HTML out of order without JavaScript
-
YouTube video embedding harm reduction
-
A note from our sponsor - SaaSHub
www.saashub.com | 22 May 2024
Index
What are some of the best open-source Standard projects in HTML? This list will help you:
Project | Stars | |
---|---|---|
1 | WHATWG HTML Standard | 7,736 |
2 | fetch | 2,084 |
3 | security-txt | 1,738 |
4 | dom | 1,533 |
5 | streams | 1,331 |
6 | url | 505 |
7 | vc-data-model | 277 |
8 | encoding | 266 |
9 | console | 268 |
10 | fs | 208 |
11 | notifications | 132 |
12 | websockets | 41 |
Sponsored