|
|
|
|
|
|
by NeoVeles
1883 days ago
|
|
|
This is something I had been pondering. Rather than making a new 'standard' based on a new technology and thus expanding the standards base with complexity, we can go the other way. Make a specification based on old tried and tested tech. Thinking something like a set HTML/CSS specs that can be implemented fairly easily. It is a spec that is essentially something a website can be built to knowing that end browsers/users can anticipate being able to render. It doesn't need anything new to be added into current browsers but it is simply enough that others can built their browser too. A vague standard I figured would be that a single person should be able to implement the full spec from the ground up in about one years full time work. If done in a group in a free/open manner it could theoretically be done quicker. That said there is the old joke. Two programmers can do in two months what one programmer can do in one month. |
|
|
That could then be heavily optimized and used for cross-platform apps instead of the bloated, kitchen sink approach of Electron.