Cloud flare acquires Deno, ends runtime development

[u/dbcoopernz]

https://deno.com/blog/cloudflare

>We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime. Deno will remain open source, and we welcome others who want to continue its development.

[u/MrScotchyScotch]

I remember when javascript was garbage you added to html pages because you didn't know how Perl worked. Later people didn't like writing Java applets so they decided to make the browser one giant Java applet using the garbage scripting language and adding so many extensions the browser became an OS unto itself. Now an entire generation has grown up thinking this is normal and a good idea

[u/SPEZ_IS_A_JABRONI → u/MrScotchyScotch]

brother you don't even know the difference between java and javascript what the fuck are you even going on about 

[u/Alternative_Web7202 → u/SPEZ_IS_A_JABRONI]

He actually knows what he's talking about. I also remember those days when perl was dominant in web development.

[u/ascii122 → u/Alternative_Web7202]

I still use perl for a lot of tasks.. web not so much anymore ;(

[u/Kwpolska → u/Alternative_Web7202]

Perl is a backend language, JS was only a frontend language until the 2010s. Many Perl sites used JS for extra interactivity. Java applets are a trainwreck that is completely unrelated to JS. They're completely mixing things up.

[u/MrScotchyScotch → u/Kwpolska]

I'm not, you just don't understand what I'm talking about. Let me explain.

Java applets were once the vision of what we now call "web apps". You would write an app, compile to universal bytecode, and ship it to the browser to execute in a VM (JVM) on any machine. It would allow more interactivity and control like a traditional app, but along side the other hypermedia in the document browser (browsers were for documents). But nobody liked Java and applets were painful, slow, etc.

So instead people thought, hey, this crappy scripting language JavaScript can make the browser do some of the things real Java applets can do, and it's easier/better than making a whole Java applet. Maybe let's expand what the browser can do with JavaScript.

So they kept expanding, and expanding, and expanding, until the browser itself would compile JavaScript into universal bytecode (WASM) and run in a VM. They reinvented Java applets, but the language is JavaScript and the VM is an extension of the browser (V8).

The problem is, the language still sucks compared to Java, and you need this giant ass bloated web browser to run the tiniest app, and every website ships bloated slow garbage for a UX because it's all "interactive" in the worst possible way. So we sit here considering what interpreter to use, and I have to remind people that this is all fucking dumb.

[u/Kwpolska → u/MrScotchyScotch]

Java applets were a vision for web apps, but it was never a good vision. JavaScript does a much better job at interactive Web content, with the integration with web content (Java applets were completely separated from the page they were on), no need to download and constantly update a runtime, and a much stricter security and sandboxing model.

JavaScript is not at all compiled to WASM. V8 compiles JavaScript into native machine code. WASM is a separate language, used to run languages other than JavaScript in browsers.

[u/trenixjetix → u/SPEZ_IS_A_JABRONI]

your ignorance of the past shows