News for hackers. Stuff that matters.
Re:The Early History Of Smalltalk (1993) by protomyth on Tuesday September 04, 2018 @09:41PM (#17914466)
Considering a whole Smalltalk VM is smaller than a lot of hero images on websites, I get the feeling that Kay is correct. I would imagine a containerized / sandboxed environment would have developed. I cannot see how it could be worse than today.
Re:The Early History Of Smalltalk (1993) by TeMPOraL on Wednesday September 05, 2018 @01:41AM (#17915293)
> I cannot see how it could be worse than today.

I fear it would turn out equivalent. The starting stack might have been better, but the promise of money to be made and competitive pressures would be the same. We would "worse-is-better" ourselves to roughly the same spot we're in today. Bloat, tracking and clickbait.

Whenever I implore people to cut down on software bloat, I know what I'm really asking is, "fight against the market, slow the decay down just a little bit".

Re:The Early History Of Smalltalk (1993) by woadwarrior01 on Wednesday September 05, 2018 @05:30AM (#17916373)
> I fear it would turn out equivalent.

Only some 30 or so years earlier, and who knows what we'd have come up with, given such an early head start?

I work in the space of dynamic language runtimes, and it hurts me to see how ideas pioneered by SmallTalk and subsequently the Self language[1] runtimes haven't yet been adopted by some of the more popular dynamic languages today.

[1]: http://bibliography.selflanguage.org/_static/implementation....

Re:The Early History Of Smalltalk (1993) by pjmlp on Wednesday September 05, 2018 @07:19AM (#17916876)
The worse part is the insistence of Ruby and Python to keep JITs away from their canonical implementations.

Sure there is PyPy and the "C JIT" on upcoming Ruby, but they don't seem to be widely deployed.

Maybe with Graal and J9 focus on increasing support for dynamic languages, that will eventually change.

Re:The Early History Of Smalltalk (1993) by scroot on Wednesday September 05, 2018 @08:27AM (#17917280)
> I fear it would turn out equivalent.

One argument against this is that the web today is not set up for easy authoring by end users (in fact, it's gotten more difficult to "make websites" as the web has progressed). But there was a hypermedia system around two decades ago that had authoring in mind from the start — hypercard — that could have been a good prototype for a "real web".

If you have authoring as a primary consideration than perhaps one-directional, consumer oriented cultures of technology would not be so prominent. But who knows.

Re:The Early History Of Smalltalk (1993) by romaniv on Wednesday September 05, 2018 @09:13AM (#17917572)
>I fear it would turn out equivalent.

I doubt it. Smalltalk had coherent design that anticipated many needs that the web faces today (and computers in general). What we get in ad-hoc piecemeal additions would be an organic part of the overall infrastructure.

Re:The Early History Of Smalltalk (1993) by gambler on Tuesday September 04, 2018 @09:48PM (#17914501)
I recently started experimenting with Squeak. It's a bit dated, but holy crap, that thing is amazing. So many good ideas packed in so few megabytes. The startup time alone blows my mind. It's pretty much a virtual machine with a sort-of-operating-system that runs an IDE for all of its own source code, and it loads faster than 95% of all vanilla desktop apps I use today.
Re:The Early History Of Smalltalk (1993) by protomyth on Tuesday September 04, 2018 @10:02PM (#17914546)
I could see having the same setup as a browser except every url downloads a vm. I do wish Squeak would update its look and feel though.
Re:The Early History Of Smalltalk (1993) by scroot on Tuesday September 04, 2018 @10:18PM (#17914592)
They are still using bitmapped graphics under the hood, which explains some of the limitation. The community has shrunk, which means there's no one to take them to the world of vector. However, Pharo people are implementing a new vector engine called Bloc.
Re:The Early History Of Smalltalk (1993) by protomyth on Tuesday September 04, 2018 @11:07PM (#17914755)
Pharo is pretty much the future. I wonder if WebAssembly and it’s upcoming ecosystem will be useful to take some load on a future Smalltalk?

[edit: since I’m getting the posting too fast crap here is another language mentioned in the article KRL by Danny Bobrow and Terry Winograd https://pdfs.semanticscholar.org/033e/cd544c4e71b14a7d3ee061... ]

Re:The Early History Of Smalltalk (1993) by scroot on Tuesday September 04, 2018 @11:16PM (#17914778)
I think about that all the time. Imagine a Smalltalk VM written in WASM. It could load with every site and every site could just be live Smalltalk.
Re:The Early History Of Smalltalk (1993) by sumim on Wednesday September 05, 2018 @12:03AM (#17914949)
Although it's not WASM, perhaps you will prefer http://squeak.js.org/ , a Squeak VM written in JavaScript.
Re:The Early History Of Smalltalk (1993) by 3rdAccount on Wednesday September 05, 2018 @06:30AM (#17916624)
There's a guy that's written a nice looking Smalltalk in Ruby that works perfectly well in the browser with rails I think.
Re:The Early History Of Smalltalk (1993) by coldtea on Wednesday September 05, 2018 @01:57AM (#17915363)
>They are still using bitmapped graphics under the hood, which explains some of the limitation. The community has shrunk, which means there's no one to take them to the world of vector.

Most (all?) commercial OSes don't use vectors for their GUIs either.

Re:The Early History Of Smalltalk (1993) by pjmlp on Wednesday September 05, 2018 @07:21AM (#17916884)
Android and Windows (UWP) do use quite a lot of vector based graphics.
Re:The Early History Of Smalltalk (1993) by coldtea on Wednesday September 05, 2018 @07:55AM (#17917073)
Yeah, Apple has some APIs for rendering widgets from vectors too, and Gnome (for icons) but most widgets, ui elements and apps are still bitmap based.