3 ms·

It have thought for a while now that the web and correspondingly the browser should be bifurcated into a content platform with no client side code and an applic

by e2e8 11y ago

It have thought for a while now that the web and correspondingly the browser should be bifurcated into a content platform with no client side code and an application platform without the burden of the older technologies. The browser would provide all the interactivity and logic for the content platform through implementations of standard html tags. For the application platform, the browser could provide a more convenient set of apis sort of like plugins did before.

HappyTypist 11y ago
Yes, because a blog post should disappear or be unable to be scrolled if my cellular reception drops out for 10 seconds.
TimJYoung 11y ago
I can't agree more. I was just saying something similar in the thread on mobile JS framework loading performance. The browser has reached a critical stage where the Jekyll/Hide impersonation has got to stop. There needs to be separate modes in the browser, application/content, or there needs to be separate browsers. The evolution of JS as a decorative language has reached its ultimate end: it's no longer just decorative and instead is now devouring and devaluing the host content it was supposed to originally enhance. But, at the same time, it's usefulness for zero-install client-side applications cannot be ignored and it needs a platform also.
tommorris 11y ago
In practice: Developer: "Well, we can either build our website in document mode or in application mode." Management: "What's the difference?" Developer: "If we build it in document mode, it loads quickly and cleanly and..." Management: "Does document mode let us put the modal popover window that got 5% of our visitors to join our newsletter last month?" Developer: "Well, nope." Management: "And the third party tracker?" Developer: "Again, no." Management: "So we can't monetize or track how many sticky eyeballs are consuming our content?" Developer: "Nope." Management: "App mode it is." Developer: "But it isn't an app. It's just static pages." Management: "APP APP APP APP APP APP. I hear you can go on a course to build apps in less than a week." Developer: starts checking his LinkedIn for an employer who doesn't make him want to take a pickaxe to his own face

by e2e8 11y ago

HappyTypist 11y ago

Yes, because a blog post should disappear or be unable to be scrolled if my cellular reception drops out for 10 seconds.

TimJYoung 11y ago

I can't agree more. I was just saying something similar in the thread on mobile JS framework loading performance. The browser has reached a critical stage where the Jekyll/Hide impersonation has got to stop. There needs to be separate modes in the browser, application/content, or there needs to be separate browsers. The evolution of JS as a decorative language has reached its ultimate end: it's no longer just decorative and instead is now devouring and devaluing the host content it was supposed to originally enhance. But, at the same time, it's usefulness for zero-install client-side applications cannot be ignored and it needs a platform also.

tommorris 11y ago

In practice: Developer: "Well, we can either build our website in document mode or in application mode." Management: "What's the difference?" Developer: "If we build it in document mode, it loads quickly and cleanly and..." Management: "Does document mode let us put the modal popover window that got 5% of our visitors to join our newsletter last month?" Developer: "Well, nope." Management: "And the third party tracker?" Developer: "Again, no." Management: "So we can't monetize or track how many sticky eyeballs are consuming our content?" Developer: "Nope." Management: "App mode it is." Developer: "But it isn't an app. It's just static pages." Management: "APP APP APP APP APP APP. I hear you can go on a course to build apps in less than a week." Developer: starts checking his LinkedIn for an employer who doesn't make him want to take a pickaxe to his own face