Skip to main content
I believe it improves the tone and the succinctness of the question
Source Link

My problem is that you'dYou'd often see that JavaScript is actually being transported over the web with all the useless stuff that doesn't need to be there -- Comments, particularly those containing licenses, indentations ('\t', '\n'), etc. that, givenGiven enough time, wouldit could end up wasting terabytes of data worldwide.! Does doing soWould a JavaScript bytecode cause another bigger problem, or has nobody thought of this yet?

My problem is that you'd often see that JavaScript is actually being transported over the web with all the useless stuff that doesn't need to be there -- Comments, particularly those containing licenses, indentations ('\t', '\n'), etc. that, given enough time, would end up wasting terabytes of data worldwide. Does doing so cause another bigger problem, has nobody thought of this yet?

You'd often see that JavaScript is actually being transported over the web with all the useless stuff that doesn't need to be there -- Comments, particularly those containing licenses, indentations ('\t', '\n'), etc. Given enough time, it could end up wasting terabytes of data worldwide! Would a JavaScript bytecode cause another bigger problem, or has nobody thought of this yet?

Tweeted twitter.com/StackSoftEng/status/1207178800964014080
Question Protected by gnat
Became Hot Network Question
Source Link
zombiesauce
  • 1.4k
  • 2
  • 8
  • 8

Why is JavaScript not compiled to bytecode before sending over the network?

My problem is that you'd often see that JavaScript is actually being transported over the web with all the useless stuff that doesn't need to be there -- Comments, particularly those containing licenses, indentations ('\t', '\n'), etc. that, given enough time, would end up wasting terabytes of data worldwide. Does doing so cause another bigger problem, has nobody thought of this yet?