That way, the page is self-contained as it is, but requires no bundled binary code to serve the site. It is actually safer security-wise.

The vendored script can be as simple as this:

  const site = {
    "path-1": " ... ",
    "path-2": " ... ",
    // More paths
  }

  function attachListeners() {
    for (const [path, html] of Object.entries(site)) {
      document.querySelector(`a[href=${path}]`).onclick = () => {
        document.documentElement.outerHTML = html
        attachListeners()
      }
    }
  }

  document.addEventListeners("DOMContentLoaded", attachListeners)

I think the misunderstanding stems from the browser's "Save As" reference in the description. It is misleading. You use "Save As" to save a single page, not an entire website.

Also, the description lacks a clear explanation of the project's purpose. It would be helpful to include a sentence explaining that the program downloads an entire website, not just a single page.

It strips out all the JavaScript too, but also packs everything into a single HTML file that is easy to transfer. Binary assets (like web fonts and images) are packed as base64 strings.

They also offer a CLI powered by Puppeteer. [1]

[0]: https://github.com/gildas-lormeau/singlefile

[1]: https://github.com/gildas-lormeau/single-file-cli

Comments URL: https://news.ycombinator.com/item?id=48518776

Points: 12

# Comments: 7

Comments URL: https://news.ycombinator.com/item?id=48506159

Points: 2

# Comments: 0

  comm -23 <(apt-mark showmanual | sort -u) <(gzip -dc /var/log/installer/initial-status.gz | sed -n 's/^Package: //p' | sort -u)

Most Linux package managers cannot separate user-installed packages from system packages. This makes cleaning up your workstation nearly impossible and a pain in the ass, since you can't tell what should be removed, or more importantly, what can be removed.

Also, most native package managers update much slower than Homebrew, meaning you often only get outdated packages.

Most Linux package managers cannot separate user-installed packages from system packages. This makes cleaning up your workstation nearly impossible and a pain in the ass, since you can't tell what should be removed, or more importantly, what can be removed.

Also, most native package managers update much slower than Homebrew, meaning you often only get outdated packages.

OwnCloud is written in Go but employs an open-core model. Some features are locked behind a proprietary paywall.

OpenCode started as an independent CLI project. Their desktop app is still in beta, and it was never a fork of VS Code.

I believe they contain no code derived from VS Code.

Comments URL: https://news.ycombinator.com/item?id=48490793

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48488569

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48486380

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48481292

Points: 4

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=48481126

Points: 475

# Comments: 3

Comments URL: https://news.ycombinator.com/item?id=48479379

Points: 3

# Comments: 0

As a counter example, Brave is heavily invested in C++ and Rust, and I believe they could handle that work much better.

With MV2, every request must be filtered with slow, JIT, garbage-collected JavaScript code. In MV3, filtering is handled by native browser code using the list provided by extensions. UserScripts could be used to modify the DOM, but that requires power users to manually enable it.

Their tech stack is heavily JavaScript-focused, as their entire UI is written in JavaScript.