5 ms·
It's not a website, it's a single-page app built with Xel, which in turn is an experimental project built with bleeding edge Web Platform technologies such as C
by jarek-foksa 10y ago
It's not a website, it's a single-page app built with Xel, which in turn is an experimental project built with bleeding edge Web Platform technologies such as Custom Elements v1, Shadow DOM v1 or ES2017.
I will implement a proper project website for all browsers when the project matures.
- hartator 10y agoKudos on the effort, I don't want to diminish it in any way, but I think you kind of prove this approach is the wrong way to build things: You are losing performance and interoperability at the same time.
- penagwin 10y agoHe doesn't care about interoperability.... It's only made for electron.... Although I do question why his website would use the same framework since it's chromium only. It's fine to make it only for chromium, as he is targeting Electron which is chromium, but his website shouldn't depend on it too.
- Sir_Cmpwn 10y agoDon't do a UA check. Just let it be broken. At the absolute worst put up a page warning users it might not work, then let them try anyway.
- jarek-foksa 10y agoThis approach works with mostly static or server-side generated websites, but with JS-heavy SPA unsupported browsers would be just showing a blank page. Currently I'm checking whether the browser supports Custom Elements v1, Shadow DOM v1 and HTML imports. If it does not, I'm showing the fallback page.