3 ms·

The web browser has been trending this way ever since JS was added to it. It's an active environment controlled by a dynamic language, it simply isn't done as w

by msla 7y ago

The web browser has been trending this way ever since JS was added to it. It's an active environment controlled by a dynamic language, it simply isn't done as well, and it isn't done entirely consistently across web browser implementations. The shortcomings and flaws don't negate the fact it is the same kind of thing. The Original Java Utopia, the world dreamed up by Sun where Java Applets would abolish the Windows desktop and the JVM would obsolete platform dependence, was a shadow of this idea with a fundamentally more static language, and one more like Smalltalk than Lisp. But with Java we've already lost the thread of an active environment, one which is responsive to on-the-fly reprogrammability and deep inspection. Maybe it could be done in terms of the JVM, but Java never seems to be used that way.

somesortofsystm 7y ago
There were Java environments in the very early days which attempted to make the dream of Smalltalk-like execution/programming environments feasible .. there was one called "Visix Vibe" which used Java to make fantastic GUI's for easy deployment, and had the ability to ship source with all products, meaning the components could be edited in-environment. Dunno what happened to Visix, but there were a few other similar style IDE's in the works in the 90's ..
scroot 7y ago
> It's an active environment controlled by a dynamic language, it simply isn't done as well, and it isn't done entirely consistently across web browser implementations One of the worst parts is that you don't do web development in the web browser itself.
flavio81 7y ago
>The web browser has been trending this way ever since JS was added to it. It's an active environment controlled by a dynamic language, It lacks lots of features to get there: - you can't dwell into the browser internals (or modify them), and the internals aren't written in Js. - you can't save the running state of the system to disk - as a language, JavaScript even in its current spec is still behind Common Lisp in power and features... For example, even decades later, lisp s-expressions are still superior to JSON! etc etc

by msla 7y ago

somesortofsystm 7y ago

There were Java environments in the very early days which attempted to make the dream of Smalltalk-like execution/programming environments feasible .. there was one called "Visix Vibe" which used Java to make fantastic GUI's for easy deployment, and had the ability to ship source with all products, meaning the components could be edited in-environment. Dunno what happened to Visix, but there were a few other similar style IDE's in the works in the 90's ..

scroot 7y ago

> It's an active environment controlled by a dynamic language, it simply isn't done as well, and it isn't done entirely consistently across web browser implementations One of the worst parts is that you don't do web development in the web browser itself.

flavio81 7y ago

>The web browser has been trending this way ever since JS was added to it. It's an active environment controlled by a dynamic language, It lacks lots of features to get there: - you can't dwell into the browser internals (or modify them), and the internals aren't written in Js. - you can't save the running state of the system to disk - as a language, JavaScript even in its current spec is still behind Common Lisp in power and features... For example, even decades later, lisp s-expressions are still superior to JSON! etc etc