I really don't like posting in this passive-aggressive quote-answer format, but I feel that I need to address each point specifically.
> no-framework scripting
This isn't a script. It's a project for a mini app.
> My point is your app could have been a single HTML file (or HTML, JavaScript, and CSS if you want to split hairs)
The app has no bundled deps and no framework.
I actually just went on CodeSandbox, started a vanilla TS project (could've just as easily be JS + jsdoc since both CodeSandbox and VScode are using Monaco, but why would I?). 2 clicks. It uses parcel but I could've just used vanilla JS imports. That's what a few of the other artifacts are from.
Lastly, the app was built as a monolith initially and then I split out a few things to make it more readable.
> .gitignore
bruh.
> README.md
BRUH.
> REQUIREMENTS.md
It's there for the people who need more context
> manifest.webmanifest
It needs offline support. That's how the platform works. Same goes for sw.js
You're being a bit dishonest and writing in bad faith. If you work in web development, you know that the times of inline JS and styles in an HTML file, uploaded via FTP to a LAMP server are long gone. Like, 10+ years gone. If you are still romanticizing that, you may have an advanced case of Old Guard™.
If you are a non-web developer, then I hope you don't apply the same reasoning in your everyday work, for your colleagues' sakes.
> no-framework scripting
This isn't a script. It's a project for a mini app.
> My point is your app could have been a single HTML file (or HTML, JavaScript, and CSS if you want to split hairs)
The app has no bundled deps and no framework.
I actually just went on CodeSandbox, started a vanilla TS project (could've just as easily be JS + jsdoc since both CodeSandbox and VScode are using Monaco, but why would I?). 2 clicks. It uses parcel but I could've just used vanilla JS imports. That's what a few of the other artifacts are from.
Lastly, the app was built as a monolith initially and then I split out a few things to make it more readable.
> .gitignore
bruh.
> README.md
BRUH.
> REQUIREMENTS.md
It's there for the people who need more context
> manifest.webmanifest
It needs offline support. That's how the platform works. Same goes for sw.js
You're being a bit dishonest and writing in bad faith. If you work in web development, you know that the times of inline JS and styles in an HTML file, uploaded via FTP to a LAMP server are long gone. Like, 10+ years gone. If you are still romanticizing that, you may have an advanced case of Old Guard™.
If you are a non-web developer, then I hope you don't apply the same reasoning in your everyday work, for your colleagues' sakes.