eeJah9to | 5 years ago | on: Ways to make a web component
eeJah9to's comments
eeJah9to | 5 years ago | on: Ways to make a web component
I've rewrote the frontend of one of my personal apps from react to webcomponents lately. For me, the most interesting aspect was that it's part of standards, requiring no dependency, so it means that I can use this app for decades without having to maintain it.
For the same reason, only the first example in this page would do for me (the one based on standard without using any library). But I suppose that for actually publishing something, such library would be needed, if anything for polyfills for older browsers (but then again, we don't expect published work to stand for decades without changes, so maybe the call for standardized technology is not as strong there).
eeJah9to | 5 years ago | on: A new and improved Twitter API
Good to know, thanks for mentioning it.
I guess they're quite used to breaking changes in twitter's API, then :) (presuming that a private API must change quite often)
eeJah9to | 5 years ago | on: A new and improved Twitter API
> Eventually, the new API will fully replace the v1.1 standard, premium, and enterprise APIs.
Uh oh. Using nitter's [1] RSS feeds is one of my main ways to access news. I have the feeling this is about to end.
page 1
I tried that for webcomponents, but I found more to my taste to actually have everything in my javascript file rather than to jump between files (it's not that messy if you keep your components smalls).