3 ms·

> "It doesn't help that he was so focused on web development as opposed to other types of programming- more than any other programming specialty, web developmen

> "It doesn't help that he was so focused on web development as opposed to other types of programming- more than any other programming specialty, web development involves grab bags of seemingly random and unrelated technologies, some vastly overengineered, some comically underengineered, and none of which were really designed to be used together in the ways that people want to use them." Doesn't this lead to the simple fact that the way things are built in the browser is in 1 simple word: fucked? A lot of the passion-based fanboys have justified the existence of at least 5 different mindsets needed to flesh out a single application (eg. some web app using: Ruby with Rails, JavaScript, HTML + CSS and lets throw in the need to write a couple of bash scripts just for petes sake). I've long been contemplating having a single-language situation or at max 2 languages to flesh out web applications (why the fuck does CSS need to exist?). If a browser itself could be built on a core of using just one language (like C++) then I don't see why stuff that works in a browser can't be done with that same philosophy. So now I'll have to find myself a bomb shelter and spend the next 20 years writing a web-only language to solve the pain points of some dumb shit called JavaScript that is great because Node.js is great...

zem 13y ago
you might like opa; at the very least it's worth a look. it bills itself as a "framework for javascript" but it's actually a language that lets you write frontend and back end code that mixes seamlessly http://opalang.org http://opalang.org
GregBuchholz 13y ago
>So now I'll have to find myself a bomb shelter and spend the next 20 years writing a web-only language Eliminate the entire browser and just start distributing x64 "apps" to raw hardware sandboxed virtual machines in Bochs or another emulator. That way people could have as much pixel level control for display purposes as they wanted. Ideally you'd also have some client side OCR so that we could copy and store text from these new websites. Some sites would want to have you download megabytes of "operating systems" before. But there'd be nothing stopping you from making a raw hardware Forth website 1000 times smaller than the next guy if you so desired http://www.ultratechnology.com/forth.htm http://www.ultratechnology.com/forth.htm You could bootstrap the whole thing by having bochs run in a asm.js setup, with the graphics frame buffer being spit out to a HTML5 canvas. http://bellard.org/jslinux/ http://bellard.org/jslinux/

zem 13y ago

you might like opa; at the very least it's worth a look. it bills itself as a "framework for javascript" but it's actually a language that lets you write frontend and back end code that mixes seamlessly http://opalang.org http://opalang.org

GregBuchholz 13y ago

>So now I'll have to find myself a bomb shelter and spend the next 20 years writing a web-only language Eliminate the entire browser and just start distributing x64 "apps" to raw hardware sandboxed virtual machines in Bochs or another emulator. That way people could have as much pixel level control for display purposes as they wanted. Ideally you'd also have some client side OCR so that we could copy and store text from these new websites. Some sites would want to have you download megabytes of "operating systems" before. But there'd be nothing stopping you from making a raw hardware Forth website 1000 times smaller than the next guy if you so desired http://www.ultratechnology.com/forth.htm http://www.ultratechnology.com/forth.htm You could bootstrap the whole thing by having bochs run in a asm.js setup, with the graphics frame buffer being spit out to a HTML5 canvas. http://bellard.org/jslinux/ http://bellard.org/jslinux/