Presuming poor intent gets us nowhere and I don't know who it helps. Maybe folks who don't want the platform to encroach "their" space? Having been a library author, I find that hard to imagine either. The whole system, when it works, is enabled by the presumption of goodwill.
-
-
Replying to @slightlylate @graynorton and
I'm not ascribing poor intent. More like impatience and over-confidence. And not towards individuals, but to the system in which they operate
1 reply 0 retweets 3 likes -
Replying to @Rich_Harris @graynorton and
Let's flip the question around: how long is too long to hold a feature?
1 reply 0 retweets 1 like -
Replying to @slightlylate @graynorton and
depends whether its absence is preventing developers from doing their jobs
1 reply 0 retweets 4 likes -
Replying to @Rich_Harris @slightlylate and
I appreciate the passion, but that's a pretty bad definition. I've actually heard a similar one by browser vendors as they point to the fact that webdevs can do it but those solutions at times have unfortunate end user implications (not saying that is true for SD specifically)...
1 reply 0 retweets 4 likes -
Replying to @gregwhitworth @Rich_Harris and
...to take both arguments to the extreme; JavaScript and the <canvas> element exist so we can all pack up and go home. I've said that numerous times to colleagues when talking about CSS color functions, CSS Grid, custom properties, new HTML elements & styling, etc.
2 replies 0 retweets 3 likes -
Replying to @gregwhitworth @Rich_Harris and
Ultimately, it's a fine line and I think as long as the folks are creating solutions, getting feedback and ensuring that they're building something people want to use - then I say carry on. IF that isn't happening then we're just creating bloat not only to the binaries but...
1 reply 0 retweets 3 likes -
Replying to @gregwhitworth @Rich_Harris and
...also to webdev ramp up, our own engineers having to maintain the code for patches, etc. So it's in everyone's best interest to continue to collaborate :)
1 reply 0 retweets 3 likes -
Replying to @gregwhitworth @slightlylate and
I get what you're saying, but whereas 'these features could be designed differently' is considered valid collaboration, 'these features are unnecessary' doesn't seem to be
3 replies 0 retweets 5 likes -
Replying to @Rich_Harris @gregwhitworth and
There are use-cases that require hard encapsulation. For Salesforce they are saying that the current APIs are not quite hard enough! So jumping in and telling people that their uses-cases aren't valid is a bit like me opening an issue in Svelte saying to use React instead.
3 replies 0 retweets 4 likes
FWIW, I am skeptical about the hard isolation within a single process. Drilling into the details matters! It might be the case that the motivation isn't something that can be solved with this API (although I know of other compelling motivators for this, e.g. memory & speed).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.