|
Peter Burns
@
rictic
94612
|
|
Googler on the Polymer team.
Web Components true believer.
|
|
|
1.256
Tweetovi
|
246
Pratim
|
363
Osobe koje vas prate
|
| Tweetovi |
|
Peter Burns
@rictic
|
3. velj |
|
Yeah, waiting to give any feedback at all until the data is loaded for the next page is a huge mistake. Feels great with a fast dev server, feels terrible in the real world where things can take time.
It's not a necessary part of client-side routing, but it is a common mistake.
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Becca
@onelittlebecca
|
3. velj |
|
We have started to implement web components at NARA and the stoke level is high! twitter.com/btopro/status/…
|
||
|
|
||
|
Peter Burns
@rictic
|
3. velj |
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Deepak Gupta
@deepakguptalaw
|
1. velj |
|
On Monday, I’ll be arguing before the U.S. Court of Appeals for the Federal Circuit, challenging the federal judiciary’s paywall for public court filings (aka PACER fees). This column by @adamliptak gives a good overview. nytimes.com/2019/02/04/us/…
|
||
|
|
||
|
Peter Burns
@rictic
|
2. velj |
|
(seriously though, the Idris book is really great: manning.com/books/type-dri…)
|
||
|
|
||
|
Peter Burns
@rictic
|
2. velj |
|
Ah, but with dependent types you could have the compiler prove that x = 7! And all it costs is five to six times longer to make or change anything!
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Sam Saccone
@samccone
|
28. sij |
|
With flash.android.com launching to the world today I would love to pull back the covers and tell you a little of how we made it possible to update your Android Phone's operation system through the browser! 📲
twitter.com/AndroidDev/sta…
|
||
|
|
||
|
Peter Burns
@rictic
|
28. sij |
|
One way of thinking about it:
If you vend a framework's component model, someone using your component needs to know about that framework.
If you vend a web component (written with a library or framework), someone using your component doesn't need to know how it was written.
|
||
|
|
||
|
Peter Burns
@rictic
|
24. sij |
|
Wild guess: string valued enums were added later, so if you'd realized strict was better here but you hadn't changed numeric enums because it wasn't worth the disruption...
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Zach Klein
@zachklein
|
15. sij |
|
My 5yo asked, “How big is a wolf?”
So I Google it... Google’s first result is the option (in browser!) to place a realistic wolf in the room with us so we can walk around it and see for ourselves.
Magical. The closest I have felt to a Young Lady’s Illustrated Primer. pic.twitter.com/ZPDpAAUCOW
|
||
|
|
||
|
Peter Burns
@rictic
|
23. sij |
|
It is not at all hard to change the API without breaking existing users. At the limit, just rename the api. LitElement at least does not rely on its existence, just uses it as a performance enhancement if available.
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Robin Ricard
@r_ricard
|
21. sij |
|
My colleague @rickbutton is being awesome, again: rickbutton.github.io/record-tuple-p… is a playground letting you toy with our stage 1 proposal: Record and Tuple. Please try it and give us a lot of feedback but keep in mind it's a stage 1 proposal: it will change!
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Polymer Project
@polymer
|
15. sij |
|
An effort 9 years in the making, but we’ve finally made it.
WebComponents are supported natively in every major browser pic.twitter.com/6yPoTXno27
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Stencil
@stenciljs
|
15. sij |
|
Microsoft Edge now supports Custom Elements natively!! twitter.com/adamdbradley/s…
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Sergio Contreras
@sergicontre
|
15. sij |
|
Web Components are supported in all modern browsers:
✅ Chrome
✅ Firefox
✅ Safari
✅ Edge
Use a standards-based approach is the natural progression of the web platform 🌐
|
||
|
|
||
| Peter Burns proslijedio/la je tweet | ||
|
Anders Hejlsberg
@ahejlsberg
|
15. sij |
|
Proud to be one of them too! twitter.com/joshbloch/stat…
|
||
|
|
||
|
Peter Burns
@rictic
|
14. sij |
|
Seems like that would be better covered by a build-time transform. You'd want configuration params (e.g. only run-time type check a subset of the code, for performance), and you'd want to match the semantics up with your build-time type checker, which means versioning.
|
||
|
|
||
|
Peter Burns
@rictic
|
14. sij |
|
Dart can make breaking changes, the web can't.
Leave type semantics to userland.
|
||
|
|
||
|
Peter Burns
@rictic
|
14. sij |
|
This gives the type system(s) time to grow and mature (there's still so much really great type system space to explore!), and there just isn't much value in the browser doing type checking.
This would mean that types would be advisory, and people would ship bad types. That's ok.
|
||
|
|
||
|
Peter Burns
@rictic
|
14. sij |
|
If TS-in-browser happens (and it has merit), the browser should parse the syntax and completely ignore all type information, semantics should be identical to compiling TypeScript to esnext today (with type errors ignored).
Advantages: zero build step; debugger can surface types
|
||
|
|
||