Skip to content

Why is the entire JS VM implemented in a single file? How do you maintain such a large codebase? #60

@fripSide

Description

@fripSide

In both QuickJS and MicroQuickJS, the entire JS engine implementation is contained within a single source file, e.g., mquickjs.c.

I'm interested in understanding the reasons behind this design choice. How do you efficiently maintain such a large file in practice? Are there specific tools or workflows you rely on to navigate and manage all the functions and code sections?

Some developers speculate that large files like this are generated by merging multiple source files via scripts, while others suggest that editors like Emacs make working with big files easier.

Could you share your recommended and practical methods for modifying and maintaining this kind of codebase? Any insights into your workflow, editor configurations, or best practices would be greatly appreciated.

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions