News for hackers. Stuff that matters.
Re:Deno 1.6 supports compiling TypeScript to a single execut... by momokoko on Wednesday December 09, 2020 @09:47PM (#25369022)
It’s funny you say that because when PHP / Python / Ruby were all the rage, most people considered needing to compile everything into a single binary gross.

What’s old is new is old again!

Re:Deno 1.6 supports compiling TypeScript to a single execut... by Cthulhu_ on Thursday December 10, 2020 @04:07AM (#25371502)
It's a circular argument and a false dichotomy tbh, they both have their place.

Ex: I maintain an 'old' PHP / JS application while building a new Go / TS one. With the old one, I change a file, it gets automatically ssh'd to my dev server, and my changes work instantly. I'm sure that if the PHP and JS had to be comp/transpiled, it would take a minute or so (it's just under 100K LOC, some files 13K LOC).

For the new application, I get the same fast feedback because Go does incremental compiles and create-react-app with TS also does incremental compiles with live reload (without requiring a full page reload).

For production builds, the old is pulled through tools like ioncube and uglify, the new one churns out an optimized binary and webpack-flavored .js files.

I mean if you zoom out enough there's no noticeable difference.

Re:Deno 1.6 supports compiling TypeScript to a single execut... by zeroc8 on Thursday December 10, 2020 @07:14AM (#25372852)
Because compilers - apart from Pascal dialects - were quite slow. With Go, you aren't wasting time waiting for the compiler. So it feels like a script language, but gives you that extra security of a compiler.