@markussen

Yep, not fully on the subject. But yes.

I like to say: "How many of your friends fluently speak on three languages? Yet any programmer is expected to know at least two, sometimes up to 5. So you must not be surprised then you look at produced code.".

So we produce websites as compiled binary?

As byte code. That can download other byte code :-)

Does the browser execute this?

Yes. This is very simple task :-)

or does the server interpret it and deliver via, say Java?

Don't understand that you mean here, as Java is both the language and Java VM. And no server has no business here, but it also executes byte code, just different.

The majority of developers would still use some kind of layout engine?

I see no problems with it, as any code must have ability to load libraries.

Although now that I think about it, it would have the huge advantage of being consistent across platforms.

I see main advantage with being consistent in developers heads. So people could work normally and you could move developers between client and server applications. Or use any language you like for development.

So the innovation now shifts from the browser to "byte-code" libraries.

Not exactly. Browser will still have something like drivers providing access to canvas, sound, video acceleration.

Btw, I can tell you why this things did not happen. Impact on general search engines will be huge, and ability to control information space will be diminished.

This could be implemented today, by making a website out of a single Java Applet?

No, it could not. As Applet still has many restrictions.
Also Java JIT machine is build on different principles, ones similar to NET, as it brings many libraries in distribution (as they try to have them being fast).

How would links work in such a system?

I see no problems with links. Hypertext existed well before web, and exist today in many systems.

Java/C# are becoming more dynamic, but they are not truly dynamic languages. JavaScript is pretty dynamic, and it runs the fastest on the browsers. HTML yeah we need markup language. CSS yeah sophisticated styling was not part of HTML spec fuk. PHP programmers can rewrite a whole new website without reusing any component, and that's great.

Yeah it's complex and that's the way it is, and it will get more complex as web is gonna do more work.

@sam_stickland JVM is the major bottleneck. The thing about Java... you know the bytecode loses all template meta information after compilation. JVM isn't really geared toward a web browser in mind. JVM is taking over the server side, but Applet is dead. Write Once Run Anywhere is dead. Oracle's JVM, IBM's JVM, Google's JVM, etc. JavaScript (JS) isn't just dynamically typed language. It's interpreted on the fly. No compilation required. JS engine has been running on a web browser since JS inception, and it runs darn fast and faster. As Google saying, we need all of JS, C, Java, and Python. Sure add HTML5, CSS3, PHP to the list. That's the way it is, and it will be for very long time. I know it sounds braindead. But it's too late.

@mark_the_harp The programming languages are like human languages. They are not perfect. They adapt. They evolve. They age. Eventually they die as new languages emerge. It's because we the human are behind the languages. As Cobol programmers begin to fade away, of course Cobol language starts dying.

Currently we are entering dark age for programming languages. We won't see new language that becomes super popular like JS, C, Java, and Python in a long time. Also HTML and CSS.

@stonebat

The thing about Java... you know the bytecode loses all template meta information after compilation.

I really do not understand a heck here.

JavaScript (JS) isn't just dynamically typed language. It's interpreted on the fly.

I really suggest to see implementation in any modern browser. Plus you mixed completely unmixable things, one of them is even not true.

@Mark_the_Harp

and if I get Vitaliy right he wants to demolish and rebuild a new house which is efficiently designed and lean 'n' mean.

I really want to remove really dangerous house.

@stonebat

I am not talking about perfection. I am talking about efficiently using resources.

The thing about Java... I meant Java doesn't retain dynamic template typing information unlike C++ template. That was a big bummer to many Java developers who had high hope on Java genetics feature. It's basically compilation type checking.

You mean generics? it is not really related to VM and byte code, but more to language implementation. And if you ask me, generics are way overrated.

I meant it doesn't require prior compilation to native binary or bytecode before loading to the browser. Actual compilation happens in the browser's JS engine on the fly.

It makes no difference.

I don't know. I stopped thinking about why the things are the way they are. Nothing but adapting.

It is bad habit :-)

I think it makes a big difference... but let's agree to disagree.

Looking at any real applications I know it makes zero practical difference.
Except you won't need people with only expertise being JS.

See what happens to Java Applet. Gotta sign the bytecode.

Signing have no relation to the problem.
If you are so afraid, any decent IDE could automatically sign package during build.

Then how are you going to debug on the browser side?

Very easy.

Some details about most popular VM.