Dekok: but. ‘tree shaking’.

Dzurilla: Dunno if this is the right place to ask this but anyone knows how to fix breakpoints in chrome? sometimes they come up when removed and sometimes don’t work at all ? :

Marlo: Dekok: because sometimes you do not want to import the entire module, e.g.

Nolfe: When making browser builds

Stweart: The point of delivering binaries but not source code is so that customers wont read your code. the point of being able to compile into a lower language is to write it in the first place in a more readable manner

Migliore: Gajus: those problems don’t exist in ES6.

Datil: You know you can just import what you want, right?

Berenson: Https://

Spuler: Except for having everything wrong, you’ve pretty much got it!

Hoogendoorn: Higuchi: Thats getting deprecated you can thank me later

Archdale: I have described in detail why lodash.* is bad idea here,

Trider: Gajus: ES6 modules are second cl***, and BECAUSE OF THAT because of this limitation, a good module tool can just remove the code you don’t use automagically for you. No more having to split things in different files to avoid size overhead. You only get what you use.

Waymer: Some companies who used to feel protected by only delivering binaries which they beleived almost no one would have the time to decipher can now feel protected by obfuscaing javascript

Widner: Gajus: so, you really should be pushing for your tools to fix that for you

Rams: Though I think that practice is silly in interprited environment

Klock: What does “interpreted” mean

Pomposo: Dekok: You are right.

Staplins: Well, lets go to webpack then.

Rudh: Why do you need more than one map function lol

Chanoine: Added break on attribute modifications and it doesn’t break

Linz: Do i need to restart chrome or something?

Bacha: Means a program like a browser reads the lines of code and runs a program to execute them.rather than the code running natively in hardware on your cpu

Raval: Twirl: make sure breakpoints are enabled

Daudt: Gajus: the formal name for this is Dead Code Elimination. And can be done easily by a technique called Tree Shaking, in ES6

Mugnolo: Stevessss: that isn’t what happens

Servi: You can turn them on and off without removing and adding them

Persch: Javascript is compiled by the browser

Slomkowski: Stevessss: JS isn’t interpreted in the browser.

Holler: Tree shaking sounds like fun

Boddeker: Higuchi: well, i restarted chrome and now they work

Scudieri: In no modern browser, at the very least

Blackwall: Stevessss: in fact, JS running in the browser can very easily beat your “compiled C program,” performance-wise.

Salvadge: Because it is not interpreted

Hands: Stevessss: anyway, I still don’t know what your point is. Do you have a particular question about JavaScript? Perhaps about how it’s executed? Or the best way of distributing JS programs?

Yamasaki: Dekok: The big problem with chrome, performace-wise, is it’s written in c++, and not javascript. if it was written in javascript, it would be much faster

Yamasaki: Tcsc: I think java is now also mostly written in java itself. used to be c++

Sundermeyer: Only the compiler is in java

Croston: Sounds like the grown ups are arguing again

Roughton: Yeah, it’s very hard to write an optimising JIT in anything but C++. Unfortunately.

Yamasaki: Tcsc: I haven’t studied recent jvms. only the ones in C++. but they also always claimed that the jvm is much faster than c++ but never really used it in the vm. so now they do at least a bit

Forsey: Dekok: but. ‘tree shaking’ is not possible in JavaScript, is it not?