blocks|key|214086|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|214087|我真的不喜欢页面中的代码被写在一行中，当我浪费大量时间试图理解其中的内容时，在页面中编写的压缩代码真的值得吗？|blockquote|214088|214089|214090|它可以是|214091|214092|根据编程原则，代码应该是可读的，其他程序员也会来维护它。|214093|214094|214095|这就是为什么缩减是作为构建过程的一部分来完成的。从事这项工作的开发人员会得到合理格式化的代码。|214096|顺便说一句，|214097|注释可以减少页面加载时间吗？但是java注释呢？其他人看不到它们|214098|214099|214100|如果它被传送到客户端，那么它会占用一些带宽。这可能是也可能不是大量的带宽，这取决于上下文。|214101|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|Z|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|10|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|11|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|12|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|13|7|@]|8|@]|9|$]]|$1|I|3|J|4|C|6|14|7|@]|8|@]|9|$]]|$1|K|3|-4|4|5|6|15|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|16|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|17|7|@]|8|@]|9|$]]|$1|O|3|P|4|5|6|18|7|@]|8|@]|9|$]]|$1|Q|3|R|4|C|6|19|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|1B|7|@]|8|@]|9|$]]|$1|U|3|V|4|5|6|1C|7|@]|8|@]|9|$]]|$1|W|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]]|X|$]]

<blockquote>
 I don't really love when the code in the page is written in one line, when I wasting a lot of time to try to understand something in there, really the compressed code written in a page worth it? 
</blockquote>

It can be

<blockquote>
 By the principles of programming, code should be readable for others programmers who will come to maintain it too.
</blockquote>

That is why minification is done as part of the build process. Developers working on it get sensibly formatted code.

<blockquote>
 and by the way, HTML comments could decrease page load time? but java comments? they is not visible to others
</blockquote>

If it is delivered to the client, then it takes up some bandwidth. That may or may not be a significant amount of bandwidth depending on the context.

blocks|key|3863367|text|在生产环境中使用HTML时，它不会被其他人读取。通常情况下，原始代码将是可读的，并且像HTML和JavaScript这样的东西通常会被缩小以减少加载时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3863368|是的，你的浏览器必须下载的任何评论都会增加页面加载时间。|3863369|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

HTML isn't meant to be read by others when it's being used in production. Generally the original code is going to be readable and things like HTML and JavaScript are commonly minified to decrease load time.

And yes, any comment that your browser has to download is going to increase page load time.

blocks|key|213729|text|有些人故意这样做是为了不鼓励检查他们的代码，尽管经过一些努力，它可以被很好地格式化并再次可读。这有点像Java中的代码混淆。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|213730|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Some do it intentionally to discourage examination of their code, although with some effort it can be well formatted and be readable again. This is a bit like code obfuscation seen in Java.

blocks|key|1963639|text|我认为你在这里混淆了很多概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1963640|页面压缩可以在不同级别上完成。您可以在web或web应用程序服务器上使用mod_gzip和mod_deflate或类似的模块来压缩web/应用程序服务器提供的原始字节。这通常会节省很多带宽，而且通常不会给web开发人员带来问题，因为浏览器会在呈现页面内容之前对其进行解压缩(或者在“查看源代码”上下文中显示源代码)。|offset|length|style|CODE|1963641|“写在一行中的页面”不是压缩。技术术语是最小化或混淆。这通常是针对JavaScript完成的，目的是减小所提供的JavaScript文件的大小；这可以极大地减小文件的大小，另外的好处是很难被人类阅读器解析。使用JavaScript微型器的Web开发人员通常足够聪明，可以获得源代码的非最小化版本，因此调试不是问题。|1963642|我曾经工作过的一个客户站点显示，在网络上使用GZIP压缩时，性能提高了40%25，使用缩小的JavaScript文件(有数千个这样的文件)部署时，性能提高了5-10%25。但是，在使用这些技术时，您的里程可能会有所不同。|1963643|最后，超文本标记语言注释()确实会影响性能，因为提供带有注释的页面要比没有注释的页面花费更多的时间。对呈现的影响可能可以忽略不计，因为注释通常会被词法分析器去掉。这不适用于内联脚本标记中的JavaScript注释，这些标记首先由HTML解析器解析。第二种类型的注释(<%25--+comment+goes+here+-->)从不由应用服务器提供，因为它是JSP样式的注释，并且JSP编译器通常会忽略这些注释，因此不会在生成的HTML内容中生成任何注释。|1963644|entityMap^0|0|10|8|19|B|0|0|0|D|Q|4F|Q|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|O|$]]

I think you are confusing many concepts here.

Page compression can be done at various levels. You can employ <code>mod_gzip</code> and <code>mod_deflate</code> or similar modules on your web or web-application servers, to compress the raw bytes served by the web/application server. This often saves a lot of bandwidth and is usually not a cause of problems for web-developers, because the browser will decompress the page content before rendering it (or displaying the source back in the "View Source" context).

The "page written in one line" is not compression. The technical term is minification or obfuscation. It is typically done for JavaScript, to reduce the size of the JavaScript file being served; this can reduce the filesize drastically, with the added benefit of being difficult to parse by human-readers. Web-developers who employ JavaScript minifiers are often clever enough to have the non-minified version of the source code available, so that debugging is not an issue.

One of the former customer sites that I've worked on, demonstrated a performance increase of upto 40% when employing GZIP compression on the wire, and between 5-10% when deployed with minified JavaScript files (there were thousands of such files). But again, your mileage might vary when using these techniques.

Finally, HTML comments (<code>&lt;!-- comment goes here --&gt;</code>) do have a performance hit, as it takes more time to serve pages with comments, than pages without them. The impact on rendering might be negligible, as comments are often stripped out by the lexical analyzer. This is not true of JavaScript comments in inline script tags that are first parsed by the HTML parser. The second type of comments (<code>&lt;%-- comment goes here --&gt;</code>) is never served by the application server, as it is a JSP-style comment, and the JSP compiler usually ignores these comments, thus not generating any comments in the resulting HTML content.

I don't really love when the code in the page is written in one line, when I wasting a lot of time to try to understand something in there, really the compressed code written in a page worth it? By the principles of programming, code should be readable for others programmers who will come to maintain it too.

and by the way, HTML comments could decrease page load time? because they are visible to others.

<pre><code>&lt;!-- comment goes here --&gt;
</code></pre>

but java comments? they is not visible to others

<pre><code>&lt;%-- comment goes here --%&gt;
</code></pre>

Page code compression is really needed?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我真的不喜欢页面中的代码被写在一行中，当我浪费大量时间试图理解其中的内容时，在页面中编写的压缩代码真的值得吗？根据编程原则，代码应该对其他程序员来说是可读的，他们也会来维护它。顺便说一句，HTML注释可以减少页面加载时间吗？因为它们对其他人是可见的。但是java注释呢...

问页面代码压缩真的需要吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问页面代码压缩真的需要吗？EN