News for hackers. Stuff that matters.
Re:Cello: Higher level programming in C by williamcotton on Monday July 15, 2013 @07:22PM (#6049155)
Thank you for mentioning Smalltalk! My comment was heavily inspired by that "computing environment".

If you look at JavaScript and the web browser... well, it's more like a Smalltalk system than a UNIX system! There are no files! It has a weird little dynamic multi-paradigm language! The web browser become the spiritual offspring of Smalltalk as soon as Brendan tacked on JS. :)

Look how WEIRD package management gets for JS when you try and make it supported by UNIX and the filesystem!

As for tools becoming language dependent... what about sourceMaps? Look at how CoffeeScript integrates with our workflow tools these days!

The biggest problem with Smalltalk was that it was made for Personal Computing, and ALWAYS had issues running other people's code or integrating well with collaborators.

The web browser and JavaScript solve a lot of these issues with the whole sandboxed code environment...

The web has NOTHING to do with files, so it seems like the perfect place to just forget about them and move forward...

Relays and switches only got us so far... Machine code only got us so far... UNIX only got us so far...

Why have we lost the courage to continue looking for better solutions and being brave enough to throw away certain concepts?

I mean, look at mobile and touch computing! iOS and Android are completely abandoning the concept of files!

Why? Because they don't really have to be there... Again, look at Smalltalk... and I know, it "failed", but do you really think it failed because it didn't have files? Is that the one reason? Is it even a reason at all??

Re:Cello: Higher level programming in C by kyllo on Tuesday July 16, 2013 @12:39AM (#6050062)
The web has NOTHING to do with files, so it seems like the perfect place to just forget about them and move forward...

What? I really don't understand this comment. The web is almost totally file-based. Visiting any website is just downloading and executing files. Including Javascript and CSS files is really just like a copy-paste operation--it just spews everything into the global namespace, which is that of the HTML file that you're currently viewing.

Re:Cello: Higher level programming in C by icebraining on Tuesday July 16, 2013 @03:04AM (#6050371)
They're representations of resources, not files. Some of them are stored as files on the server, but that's purely incidental and irrelevant to the browser; it treats them just the same as it treats the runtime generated representations, such as this HTML we're viewing.
Re:Cello: Higher level programming in C by boomlinde on Tuesday July 16, 2013 @05:10AM (#6050698)
Files are representations of resources as well. Some of these are mapped to data stored on disk blocks, but others aren't. Some file systems are not disk abstractions at all. While I agree that calling HTTP resources "files" is not entirely correct, they're presented in a very file system-like hierarchy, and in most cases I'd say that they are not meaningfully distinct from files in a file system.

I definitely find "The web has NOTHING to do with files" less agreeable than what kyllo is saying.

Re:Cello: Higher level programming in C by williamcotton on Tuesday July 16, 2013 @10:33AM (#6052092)
Think about files in the context of a filesystem and an operating system. You can move them around, read to them, write to them, execute them...

Now think about what the browser runtime can do with "files". Well, next to nothing, because the browser doesn't have access to a filesystem.

For a browser to communicate with a filesystem it has to do so through HTTP and only in a very limited way.

Re:Cello: Higher level programming in C by boomlinde on Tuesday July 16, 2013 @11:45AM (#6052625)
> You can move them around, read to them, write to them, execute them...

That functionality depends entirely on the file system and the file in question, as much as the operations available on an HTTP resource depends on the verbs that the resource implements and how it implements them.

Also, a file system will typically not execute your files. Nothing stops you from executing an HTTP resource in the same manner. Say,

    <script type="text/javascript.js" src="bla/bla.js">
or

    curl http://bla.com/bla.sh | bash
> Now think about what the browser runtime can do with "files"

Using the standard HTTP verbs, you can read, write, create and delete resources.

Re:Cello: Higher level programming in C by kyllo on Tuesday July 16, 2013 @09:18AM (#6051637)
This HTML we're viewing may be runtime-generated on the server, but it's still saved on my machine as one or more files in a temporary folder and then opened by my browser application, is it not? A web browser is really just a fancy, scriptable file viewer.

And that's for HTTP--not to mention the other major protocol FTP, the name of which is self-explanatory: File Transfer Protocol.

Re:Cello: Higher level programming in C by jerf on Tuesday July 16, 2013 @10:23AM (#6052033)
Define "file". Read off from the definition of file whether the WWW is just a set of "files".

If you use the UNIX-like definition of file (to say nothing of the Plan 9 definition), which can include dynamically-generated streams such as /dev/random, then sure, the whole web is a set of files. I assume Plan 9 will even serve web sites out of its "filesystem" with the correct poking.

If you use the DOS-like definition of a static file (ignoring CON and a couple of other special cases), then, no, the web is not merely a set of fancy static files on disk. Many, many, many things never have a rest representation on disk as a simple file, even if one could theoretically be manifested at a point in time for some particular web page.

I sort of feel you're trying to conflate these two distinct definitions, and using the fact that the web is a set of stream-files to assert that the web is nothing but a set of disk-files, but that's equivocation.

Re:Cello: Higher level programming in C by icebraining on Tuesday July 16, 2013 @10:00AM (#6051876)
This HTML we're viewing may be runtime-generated on the server, but it's still saved on my machine as one or more files in a temporary folder and then opened by my browser application, is it not?

No, it's kept as an in-memory structure. Certain representations are serialized and cached to files, yes, but that's just a optimization to reduce network requests; you can disable it without affecting the browser.

In particular, "grep -r kyllo ~/.cache/mozilla/firefox/" returns zero results, despite having this post open on my browser.

A web browser is really just a fancy, scriptable file viewer.

I disagree; it's an hypertext engine, with renderers for multiple media types. That hypertext can be loaded and/or cached from files, but that's an implementation detail that does not define the application.

And that's for HTTP--not to mention the other major protocol FTP, the name of which is self-explanatory: File Transfer Protocol.

That's not part of the web.

Re:Cello: Higher level programming in C by pjmlp on Tuesday July 16, 2013 @03:07AM (#6050380)
One of the reasons Smalltalk failed is called Java.

Smalltalk was actually getting a foothold in the enterprise when Java happened and everyone switched to it.

Eclipse was originally a Smalltalk environment (Visual Age for Smalltalk).

Yes, files also played big a role, because it was not possible to use source control systems with Smalltalk that worked across implementations. So you were bound to a specific vendor.

Re:Cello: Higher level programming in C by flyinRyan on Tuesday July 16, 2013 @07:37AM (#6051168)
And actually Sun approached Viacom to license Smalltalk at much less than what they were currently charging. Viacom wouldn't budge so Sun invested in "Oak" that they were already playing with in house.
Re:Cello: Higher level programming in C by pjmlp on Tuesday July 16, 2013 @08:14AM (#6051313)
Thanks for sharing the information.
Re:Cello: Higher level programming in C by flyinRyan on Tuesday July 16, 2013 @01:12PM (#6053185)
np, sorry I was too lazy to post any links but I think I gave enough info to find it on the internet.
Re:Cello: Higher level programming in C by t1m on Tuesday July 16, 2013 @10:07AM (#6051919)
I made the switch from Smalltalk to Java. I remember how disappointing it was to return to such a primitive language. I also used the VisualAge for Java products, which I recognized immediately as Smalltalk tools. I wasn't at all surprised to find out they were actually written in Smalltalk
Re:Cello: Higher level programming in C by hboon on Wednesday July 17, 2013 @04:40AM (#6056740)
It was an engineering feat. VAJ was a Smalltalk engine that ran both Smalltalk and Java.
Re:Cello: Higher level programming in C by ExpiredLink on Tuesday July 16, 2013 @10:48AM (#6052213)
> Smalltalk was actually getting a foothold in the enterprise when Java happened and everyone switched to it.

Actually, Smalltalk projects failed hard in the enterprise during the 90-ies which lead to Smalltalk's demise. 'Java killed Smalltalk' is a myth.

Re:Cello: Higher level programming in C by kyllo on Tuesday July 16, 2013 @09:57AM (#6051863)
Yeah, Java killed Smalltalk in the enterprise.

My employer's official application development language has changed just twice in the last 30 years, from COBOL -> Smalltalk -> Java.