2,341 karma · joined October 14, 2012
The model "failed" to answer this question, replying with “Unfortunately the essay does not provide a definitive answer about the most fun thing to do in San Francisco.”
It looks right to me... The best thing to do in San Francisco is not necessarily fun
With semver you live in this world where you are promised the versions to follow semantics, but human nature creeps in and we introduce breaking changes (like bugs!) without setting the version correctly.
With pragmatic versioning you give expectations but also convey that to upgrade you need to test that your software still works.
Since it's a wasm runtime capable of many things I find bizarre that they now start describing it with a ultra-specific use case
<user-avatar> content is both a view and an interface, which is not obvious
That's an accessibility gotcha, the title attribute tend to be neglected by screen readers and you should use aria attributes to communicate that information, and display it with other means
US [1]
Percent of adults aged 20 and over with obesity: 41.9% (2017-March 2020) Percent of adults aged 20 and over with overweight, including obesity: 73.6%
EU [2] [3]
Obese: 16% Percent of adults aged 18 and over with overweight, including obesity: 52.7%
[1] https://www.cdc.gov/nchs/fastats/obesity-overweight.htm [2] https://ec.europa.eu/eurostat/statistics-explained/index.php... [3] https://ec.europa.eu/eurostat/databrowser/view/hlth_ehis_bm1...
> can I push this YAML complexity into a script?
- what language is the script written in?
- will developers use the same language for all those scripts?
- does it need dependencies?
- where are we going to host scripts used by multiple github actions?
- if we ended up putting those scripts in repositories, how do we update the actions once we release new version of the scripts?
- how do you track those versions?
- how much does it cost to write a separate script and maintain it versus locking us in with an external github action?
These are just the first questions that pop in my mind, but there is more. And some answers may not be that difficult, yet is still something to think about.
And I agree with the core idea (move logic outside pipeline configuration), but I can understand the tepid reaction you may get. Is not free and you compromise on some things
The fact that scoped elements are not yet part of the standard is quite a turn off. Every web component is global and the first one that uses a name wins. Even if you are not competing with third party libraries you will need to have multiple versions of your same component very soon to handle breaking changes.
The string only passing is an headache when you'd like to pass object/functions to compare later on.
The fact that some CSS properties can bleed in the shadow Dom, while others don't.
To introduce them into an existing codebase you need support, and last time I checked the support from React was clunky
This is the proposal for scoped elements: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
Depends on the scale, and the original comment in this thread mention "serious performance issues" as something they care about, so choosing a faster language is not that far fetched as an idea (algorithms trump but still...)
from the linked article: "Yes, that means an officially supported browser version!"
It moved away from 0.x around 6 years ago