5 ms·

> the direction I'd like to see web development move is having a statically typed language that compiles to VM bytecode. Java… you want Java. And so the cycle

> the direction I'd like to see web development move is having a statically typed language that compiles to VM bytecode. Java… you want Java. And so the cycle continues!

christophilus 5y ago
Or preferably, F#.
naruhodo 5y ago
You could add some kind of security manager to sand box it and have little apps running in the browser. Maybe call them "applets".
- chmod775 5y ago
  That sounds amazing! What if they came with some kind of built-in canvas?
  - pjmlp 5y ago
    https://flutter.dev/ https://flutter.dev/
jrockway 5y ago
That's a really good point. What we wanted all along was the JVM with a DOM API. We started with Java. It didn't gain any traction for browser scripting. They took "Java" out and called it JavaScript. Now we take the "script" out and call it WebAssembly. If someone in 1995 made Java a DOM-editing thing instead of an applet thing, we could have saved 25 years of running around in circles :) (Going back even further, we all connected to a mainframe with a dumb terminal. The desktop revolution happened... and now we're back to dumb terminals attached to a mainframe. But we call it "The Cloud" instead, and the dumb terminal fits in your pocket.) Maybe the past wasn't as dumb as we think it was. We just weren't smart enough to understand it at the time.
- ludamad 5y ago
  Hey applets could manipulate JavaScript data/the DOM. There is a bit of bark to the 'Java script' bite. It was very slow, though, sending through the JVM process and to the browser process each time you read or wrote a value (and the plugin that did this I think was in its own process - memory is hazy there). Overall it's hard to say how Sun could have won here, perhaps acquiring macromedia and using Flash technology to make a browser that ran those cool portals out of the box, and hey scripted first-class in Java too btw ;-)
- fiddlerwoaroof 5y ago
  What I’ve always wanted is scheme in the browser.
  - lioeters 5y ago
    There was a fork in the road of history, where that could have been the future we live in.. > In 1995, Netscape hired Brendan Eich with the promise of letting him implement Scheme (a Lisp dialect) in the browser. How JavaScript Was Created - http://speakingjs.com/es5/ch04.html http://speakingjs.com/es5/ch04.html --- > Whether that language should be Scheme was an open question, but Scheme was the bait I went for in joining Netscape. Previously, at SGI, Nick Thompson had turned me on to SICP. > ..The diktat from upper engineering management was that the language must “look like Java”. That ruled out Perl, Python, and Tcl, along with Scheme. https://brendaneich.com/2008/04/popularity/ https://brendaneich.com/2008/04/popularity/
    - fiddlerwoaroof 5y ago
      Yeah, I know this history well.
  - joekim 5y ago
    Like this? https://github.com/biwascheme/biwascheme https://github.com/biwascheme/biwascheme
    - 5y ago
deleted 5y ago
[deleted]

> the direction I'd like to see web development move is having a statically typed language that compiles to VM bytecode. Java… you want Java. And so the cycle continues!

christophilus 5y ago

Or preferably, F#.

naruhodo 5y ago

You could add some kind of security manager to sand box it and have little apps running in the browser. Maybe call them "applets".

chmod775 5y ago
That sounds amazing! What if they came with some kind of built-in canvas?
- pjmlp 5y ago
  https://flutter.dev/ https://flutter.dev/

jrockway 5y ago

That's a really good point. What we wanted all along was the JVM with a DOM API. We started with Java. It didn't gain any traction for browser scripting. They took "Java" out and called it JavaScript. Now we take the "script" out and call it WebAssembly. If someone in 1995 made Java a DOM-editing thing instead of an applet thing, we could have saved 25 years of running around in circles :) (Going back even further, we all connected to a mainframe with a dumb terminal. The desktop revolution happened... and now we're back to dumb terminals attached to a mainframe. But we call it "The Cloud" instead, and the dumb terminal fits in your pocket.) Maybe the past wasn't as dumb as we think it was. We just weren't smart enough to understand it at the time.

ludamad 5y ago
Hey applets could manipulate JavaScript data/the DOM. There is a bit of bark to the 'Java script' bite. It was very slow, though, sending through the JVM process and to the browser process each time you read or wrote a value (and the plugin that did this I think was in its own process - memory is hazy there). Overall it's hard to say how Sun could have won here, perhaps acquiring macromedia and using Flash technology to make a browser that ran those cool portals out of the box, and hey scripted first-class in Java too btw ;-)
fiddlerwoaroof 5y ago
What I’ve always wanted is scheme in the browser.
- lioeters 5y ago
  There was a fork in the road of history, where that could have been the future we live in.. > In 1995, Netscape hired Brendan Eich with the promise of letting him implement Scheme (a Lisp dialect) in the browser. How JavaScript Was Created - http://speakingjs.com/es5/ch04.html http://speakingjs.com/es5/ch04.html --- > Whether that language should be Scheme was an open question, but Scheme was the bait I went for in joining Netscape. Previously, at SGI, Nick Thompson had turned me on to SICP. > ..The diktat from upper engineering management was that the language must “look like Java”. That ruled out Perl, Python, and Tcl, along with Scheme. https://brendaneich.com/2008/04/popularity/ https://brendaneich.com/2008/04/popularity/
  - fiddlerwoaroof 5y ago
    Yeah, I know this history well.
- joekim 5y ago
  Like this? https://github.com/biwascheme/biwascheme https://github.com/biwascheme/biwascheme
  - 5y ago

deleted 5y ago

[deleted]