domenicd

20 ms·

151.
by domenicd 9y ago
Here is my reply the last time this concern came up: https://news.ycombinator.com/item?id=15927069
152.
by domenicd 9y ago
Here is my reply to a similar concern last time this came up: https://news.ycombinator.com/item?id=15927130 .
153.
by domenicd 9y ago
The W3C fork's versions are arbitrary too though (yearly). You could organize a yearly update on what's new in the HTML Standard if you thought that would be valuable to people. It wouldn't change the fact that browsers relea
154.
by domenicd 9y ago
Given that the browsers with respect to which you implement the code change under your feet every 6 weeks, I think it's better the standard keeps pace with them than having it give a misleading impression of what you're developing
155.
by domenicd 9y ago
Those are fair counterexamples. Perhaps I should be distinguishing between the Blink team and the rest of the Chrome team. I realize that distinction isn't very important to an outsider, but at least realize that that there's a la
156.
by domenicd 9y ago
> And yet, we don't get things like that changes page from the WHATWG version. (Unless you want to dig through the whole commit history) So far we've done our best to keep a really readable, tidy Git commit log, which should he
157.
by domenicd 9y ago
I work for Chrome, as an editor of the HTML Standard. So let me give you my perspective on this. In Chrome we ensure that all features we ship to the web go through a public standards process. This allows them to be developed by a collabora
158.
by domenicd 9y ago
This change to requiring attribution is actually fairly recent, and was made with some reluctance on the part of us editors, despite eventually agreeing it was the best path forward. See https://blog.whatwg.org/copyright-lic
159.
by domenicd 9y ago
I don't really know what process the W3C fork of our work uses for removal, if any, but you can learn more about how features get removed in the (WHATWG) HTML Standard per our working mode: - https://whatwg.org/working-
160.
by domenicd 9y ago
The biggest weirdness about it was that it was essentially a parser macro, not an element. That is, at parse time, it expanded into a form/label/hr/input set of elements into the token stream. Super-bizzare. See the removal p
161.
by domenicd 9y ago
I haven't looked at the W3C fork of our work, but in the actual HTML Standard (maintained at the WHATWG), menu was not completely removed---just the mostly-unimplemented context menu feature. We left menu as a semantic alternative to o
162.
by domenicd 9y ago
The historical claim, that default exports we're introduced for compatibility with CommonJS/Node, is not accurate. Default exports were introduced because often a module wants to export a single value or piece of functionality. In
163.
by domenicd 9y ago
Serious question: how many people in that demographic group do you think have ever seen the movie/read the book that it's based on? I'm approaching 30 myself and never heard of the source material before all the news articles
164.
by domenicd 9y ago
I eat Soylent whenever I would otherwise have to buy or prepare food alone. I eat a lot in general, as I'm trying to "bulk", so I end up eating a lot of Soylent. Concretely, working at Google, this means a weekday eating sche
165.
by domenicd 10y ago
This is the same kind of confusing stuff as in the article. Give it to me straight: when I upgrade stable Firefox to version N, how many more weeks will I wait for a stable update to version N+1?
166.
by domenicd 10y ago
Apart from the (fairly valid IMO) political reasons, Firefox is still the king of UI customizability and good add-ons. Even without the old XUL system, there are add-ons like those at https://testpilot.firefox.com/ which mo
167.
by domenicd 10y ago
This seems like a good change. For Chrome, I only use Canary + stable. And having beta as a period for a wider audience with relatively lower bug tolerance to catch things before they hit stable makes sense. But Chrome's Dev channel&#x
168.
by domenicd 10y ago
Hey there, I'm both the author of the browser streams spec [1] and the current champion of the async iteration spec [2] that this article discusses. We have, in fact, thought through the interaction here :). johnsonjo got things basica
169.
Timers and time travel in the HTML Standard(html.spec.whatwg.org)
1 points by domenicd 10y ago|0 comments
170.
Using SSH securely(annevankesteren.nl)
4 points by domenicd 10y ago|0 comments
171.
by domenicd 10y ago
You just buy a key for each and leave them permanently plugged in. Works best with the nano. (This assumes that you're OK allowing physical access to the device to count as one of the factors in 2FA, instead of e.g. physical access to
172.
by domenicd 10y ago
Right, everything is relevant to someone. But the grandparent was talking about what is relevant to browser vendors (and thus web developers), in which case it's pretty clear.
173.
by domenicd 10y ago
I tried to leave some details here on the situation downthread: https://news.ycombinator.com/item?id=12849375 As for actual technical differences, the vast majority of them are bugs introduced during the copying process, or
174.
by domenicd 10y ago
Hi there, one of the WHATWG HTML editors here. > Meanwhile, W3C HTML5 has defined releases that are thoroughly scrutinized, reviewed, and debated in endless committee meetings. While this was true in the past, these days it's not re
175.
DRM and Web security(blog.whatwg.org)
4 points by domenicd 10y ago|0 comments
176.
by domenicd 10y ago
Because await import() can be used inside if statements or similar.
177.
by domenicd 10y ago
Similarly to the `<div hidden>` example above, it's a tradeoff. A speculative fetch is just that: speculative. It might not always be correct, but on balance, it's likely to improve the user's experience. I think it&#x2
178.
by domenicd 10y ago
But your entire app wouldn't be held up! Only that subgraph.
179.
by domenicd 10y ago
It is a problem in HTML, actually, e.g. `<div hidden><img src="foo.png"></div>`. Per spec that fetch should not happen until the div becomes un-hidden. (Which is only determinable at runtime, since you can o
180.
by domenicd 10y ago
Yes, indeed. If your app actually depends on dynamically-loaded information before it can continue, then of course your app needs to block further evaluation. Top-level await simply allows you to express that without placing the rest of you

More ›