Skip to content

Conversation

@Yemaneberhan-Lemma
Copy link
Contributor

No description provided.

@netlify
Copy link

netlify bot commented Aug 21, 2024

Deploy Preview for axelerant-engg-handbook ready!

Name Link
🔨 Latest commit d2585b6
🔍 Latest deploy log https://app.netlify.com/sites/axelerant-engg-handbook/deploys/66c6e8e8d695500008b0399d
😎 Deploy Preview https://deploy-preview-209--axelerant-engg-handbook.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Compressed CSS/JS refers to the technique of reducing the size and optimizing the performance of CSS/JavaScript files. A website can load more quickly, use less bandwidth, and put less strain on the server by compressing its CSS and JS. By minimizing the size of the CSS/JS files and the amount of HTTP requests, compressed CSS/JS helps make a website faster and more effective.

Furthermore, Compressed CSS/JS can make the CSS/JS code more challenging for others to interpret and edit, which can be helpful for defending intellectual property. It is advised to preserve a copy of the original CSS/JS files for development since compressed CSS/JS might also make debugging more difficult.
Compressed CSS and JavaScript refer to techniques that reduce the size of these files, optimizing website performance. Compression leads to faster load times, reduced bandwidth usage, and less server strain by minimizing file size and HTTP requests. Additionally, compressed code can be more challenging to interpret, which may protect intellectual property. However, it’s advisable to keep original files for development, as compressed versions can complicate debugging.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally, compressed code can be more challenging to interpret, which may protect intellectual property.

This is not really a benefit because these can be easily reversed. Let's drop this.

However, it’s advisable to keep original files for development, as compressed versions can complicate debugging.

Let's talk about source maps. Just a mention; no need to go in-depth.

Compressed CSS/JavaScript refer to techniques that reduce the size of CSS and JavaScript files, optimizing website performance. Compression leads to faster load times, reduced bandwidth usage, and less server strain by minimizing file size and HTTP requests.

Furthermore, Compressed CSS/JS can make the CSS/JS code more challenging for others to interpret and edit, which can be helpful for defending intellectual property. It is advised to preserve a copy of the original CSS/JS files for development since compressed CSS/JS might also make debugging more difficult.
Additionally, using source maps allows developers to retain original, uncompressed code during development, making debugging more manageable even when deploying compressed versions to production.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using source maps allows developers to retain original, uncompressed code during development

this is for debugging, not development. Developers have access to the actual source code during development in any case. Please read up on source maps and then rephrase this entire sentence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants