zlacker

>>iBelie+(OP)
This reminds me of the idea of "wouldn't it be great if we could use the same programming language for frontend, backend, and database queries". Well, maybe, but in practice not really. They are doing different kinds of things, you will have to use them differently, it doesn't really help all that much to have the same language. It SOUNDS like this would be really helpful, until you get it, and then discover that it doesn't really help all that much, because what matters most is not the language syntax, but the problem space.

Laptops and smartphones are made for doing different kinds of things. The real-estate requirements are different, as are the typical use cases, and even in the case where you solve them both with, for example, dynamic web pages, you still end up coding for both use cases separately, you just now have it all stuffed into the same codebase, which is harder in many cases instead of easier.

I believe Microsoft has been trying to make all OS usecases the same for decades. I believe they have not succeeded, not because Microsoft is deficient somehow, but rather because it's not, fundamentally, a good idea.

>>rossda+jf
You can live that dream in clojure land! Clojurescript on the front end, Clojure on the backend, and datalog/honeysql for the database if you'd like. And it is awesome! After using a stack like this I'm spoiled for the slog that is developing in separate languages for each of those things.

I think that dream is possible with OS usecases as well, it's just that nobody has made it work yet. And I can't think of a better way to eventually get there than to build it slowly out of free and open source software. It might take a while, but since people have the ability to adapt the software to their needs when it is free, I'm confident with time that it will serve those needs.