Live data from Hacker News

Netscape and Sun Announce JavaScript (1995)

web.archive.org

311–320 of 476 posts

Re: Netscape and Sun Announce JavaScript (1995)

#311
post #157

Such a sad day for an industry! In a slightly different turn of events, web software ecosystem perhaps could be different from the pile of hacks on top of hacks it is now.

Java applets? Flash?

I'm thinking mostly on a scenario where browsers could have a competition of existing languages (C, C++, Java, Lua, etc).

Re: Netscape and Sun Announce JavaScript (1995)

#313

What stands out to me is how much more foresight they had than I'd thought about the ways JS would be used: > With JavaScript, an HTML page might contain an intelligent form that performs loan payment or currency exchange calculations right on the client in response to user input. A multimedia weather forecast applet written in Java can be scripted by JavaScript to display appropriate images and sounds based on the c…

The industry is cyclical and to be forward thinking all you have to do is describe what's already happened and assume it will happen again. ;-) The things being done with JavaScript today are not new, nor is the idea that a server and client would coordinate to run interactive apps. That fundamental concept has been reimplemented in many different ways until we've landed on the current rube goldbergian monstrosity th…

I agree with your basic premise. However, in this particular instance, what would have been the historical equivalent ("already happened") of scripts sent by the server to the client during the request response cycle, which could perform layout and logic in the client?

If you're simply referring to code that could run on both client and server, your point is clearer to me.

Re: Netscape and Sun Announce JavaScript (1995)

#314
post #81

Earlier quoted context omitted.

It's very odd, if someone nowadays called their language CSharpScript, they'd get slapped with a C&D

Remember, Sun needed Netscape to make Java successful. Today Java is a server-side technology, but that's not how it started its life. Java started its life as a technology to build more powerful web pages (using embedded applets). Sun needed Netscape to bundle Java into its browser. So if Netscape wanted to leverage the hype that existed around Java at that time then Sun had to let them.

>Java started its life as a technology to build more powerful web pages

I'm pretty sure Java came from the work James Gosling did on Oak, which was mostly used for embedded systems. I remember a lot of the early documentation being OO designs for devices like microwaves and CD players.

Re: Netscape and Sun Announce JavaScript (1995)

#315

What stands out to me is how much more foresight they had than I'd thought about the ways JS would be used: > With JavaScript, an HTML page might contain an intelligent form that performs loan payment or currency exchange calculations right on the client in response to user input. A multimedia weather forecast applet written in Java can be scripted by JavaScript to display appropriate images and sounds based on the c…

Running the same logic and the same technology in the server and the client was mandatory for realtime multiplayer games since the 1990s. See this article from Valve [1] for a briew overview of how client side prediction works. You should also have the server process the data to avoid cheating by modificating the client app.

[1] https://developer.valvesoftware.com/wiki/Latency_Compensatin...

Re: Netscape and Sun Announce JavaScript (1995)

#316
post #296

Earlier quoted context omitted.

Android Java is not Java, and yes when I take someone's product and don't pay what the license specifies, while introducing an incomplete implementation, that is 100% ripping off. Thankfully we are going to have that settled in the near future, and then Android folks can party all night long with their Kotlin implementation and rename ART into KVM.

Despite dalvic and co. it still pushed the Java ecosystem, right? Not what I would call a tornado in the meaning pf destruction. And about the license, well, it is disputed, right? I only read about it tangential, but the case seemed far from crystal clear to me.

As much as Microsoft did with J++.

No one needs Android Java slowing down the Java ecosystem by imposing additional burdens on Java library authors that also want to target Android.

Besides Google that is.

Re: Netscape and Sun Announce JavaScript (1995)

#317
post #301
post #293

Earlier quoted context omitted.

How could one consider Java a scripting language? It's compiled to .class files, has no reasonable interactivity, strict structure enforced upon the code, etc. E.g. the antithesis of what makes us call something a scripting language in basically every category.

Sorry I am not an expert in Java, but doesn’t the jvm execute the .class files like bash would execute the .sh scripts.

A scripting language is generally thought as a language suitable for quick easy project, less so for large scale software engineering. Verbosity of syntax, compilation, presence of boilerplate code, static typing are all things that make java unattractive as a scripting language.

Java is great at what it does, which is not scripting.

Re: Netscape and Sun Announce JavaScript (1995)

#318
post #293

Earlier quoted context omitted.

How could one consider Java a scripting language? It's compiled to .class files, has no reasonable interactivity, strict structure enforced upon the code, etc. E.g. the antithesis of what makes us call something a scripting language in basically every category.

So Java Script meant "complement to Java, but converted to machine language in the browser, instead of compiled?" (Thank you, genuine question)

> So JavaScript meant "complement to Java

The whole JavaScript thing was just marketing. In 1995, Java was THE hottest thing so associating it with Java might fuel adoption/acception.

There is an old saying; Java is to JavaScript what Car is to to Carpet.

Re. your compiled question. It's up to the browser on how to execute JavaScript. E.g. Chrome has the V8 engine. This is the VM that compiles and executes JavaScript within Chrome. Other browsers might have different engines.

https://en.wikipedia.org/wiki/V8_(JavaScript_engine)

Re: Netscape and Sun Announce JavaScript (1995)

#319

Earlier quoted context omitted.

It still bothers me when people talk about dynamic HTML these days. Just two weeks ago some team lead said it and I thought 'dude, that is so 90s'.

It's also probably incorrect; DHTML didn't involve loading data via AJAX after the page loaded, but instead configuring the webpage on the client side after loading it. That said, ask them if they'd prefer the backend in PHP or Coldfusion.

1999 saw the release of XMLHttpRequest as an ActiveX control for IE 5. There certainly were IE-focused developers still referring to most of what they were doing as DHTML and yet doing the earliest AJAX stuff, back when the X still made sense that it stood for XML and XMLHttpRequest was the first and at the time only AJAX tool available in a web developer's toolbelt.

Re: Netscape and Sun Announce JavaScript (1995)

#320

I still don't know why they stuck the "Java" name on JavaScript. Very confusing when the two languages are completely unrelated. > Java programs and JavaScript scripts are designed to run on both clients and servers, with JavaScript scripts used to modify the properties and behavior of Java objects, so the range of live online applications that dynamically present information to and interact with users over enterpris…

There is a JavaScript interpreter built in to Java (or more than one, in that you could choose at least one older one at the time I tried it). I used this for a fairly complex app and found it surprisingly easy to let it parse JavaScript and affect the Java program, moving data back and forth.

> There is a JavaScript interpreter built in to Java

Are you referring to Nashorn? If so, wouldn't "was" be the correct verb, not "is"?

https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)

Post reply on HN