4 ms·
I agree with what appears to be your general goal, but various points: 1. You need to refine your argument. I suspect your main point is philosophical and poli
by mindslight 15y ago
I agree with what appears to be your general goal, but various points:
1. You need to refine your argument. I suspect your main point is philosophical and political, but you detract from it by setting up a nebulous security argument. The security concerns you describe are non-issues. Turing completeness says nothing of the available IO primitives, hence why people counter with sandboxing. Solving XSS is as conceptually simple as having any js-initiated request include the identity of what initiated it (in the case of XSS, the other site), and server frameworks having a whitelist of such initiators. But in general, a user shouldn't be even worried about cross site scripting as they're not meant to have control over it - their only input is whether to rely on the total security of a specific site.
2. Executable blobs are the lowest common denominator (any concept can be realized in them) so new concepts tend to be implemented in them rather than engineering a more declarative format. Furthermore, users are lazy and auto-updating of software (in this case, on every page load) is a net win. However, apt-get also gives me these very nice properties.
3. This is where the philosophy comes in - users should be in control of the software they use! Web 2.0 is actually proprietary software 2.0! Browser extensions can modify the applications to some extent, but are fighting an uphill battle due to the difficulty in analyzing Turing-complete blobs. I presume this is your real motivating factor in wanting to change the expressive power of scripts, but as long as the code has more expressiveness than a simple declarative format, you can never actually tame it. (Imagine a server framework that re-obfuscates the client-side code every hour).
4. One fundamental issue to address is naming the code so that end users may gain control over administering it. One doesn't install a new version of CAD software in the middle of a project, as their goal is to finish the project and not get bogged down figuring out how to use a new version. I only dist-upgrade when I'm willing to accept a few days of shaking out changes. Contrast with the current web, where a site will make unilateral changes and the only recourse of users is to complain. One should be able to locally 'roll back to the previous version of this site', and the site should support that by decoupling their code and data model.
5. Another major issue is data store and "network" independence. If one doesn't like the changes site A is making to the software, they should be able to switch to a competing site B, and have their data and connections intact - akin to several programs using the same file format. This of course requires fundamental site openness, with is directly counter to the standard web-hollywood business model of becoming the middleman in an n^2 network, so I expect eventual disruption rather than gradual change.