6 ms·

There's an irony about posting in a topic about simple, vanilla, no-framework scripting and then linking to a repository with the following unnecessary ancillar

There's an irony about posting in a topic about simple, vanilla, no-framework scripting and then linking to a repository with the following unnecessary ancillary files: .gitignore .prettierrc README.md REQUIREMENTS.md manifest.webmanifest package.json tsconfig.json yarn.lock Plus the actual source code is spread over four TypeScript files, JavaScript, CSS, and HTML. This isn't meant as criticism of your code specifically but of "modern" web development which hypocritically espouses simplicity but actually increases complexity of development. My point is your app could have been a single HTML file (or HTML, JavaScript, and CSS if you want to split hairs). Instead there's 15+ files because that's the state of modern development.

wilsonrocks 7y ago
A lot of people think a README file is important.
apazzolini 7y ago
Right, OP totally should have included the interview question requirements as a commented block at the top of index.html instead of separating it out. It's way too complex as is. And definitely, .gitignore is well known to be responsible for the "complexity of web development." Maybe we should include .gitignore in index.html too?
- anarchodev 7y ago
  GitIgnore.jsx IMO
StreamBright 7y ago
These files are supposed to be in every single folder nowadays.
cc81 7y ago
>.prettierrc Just to take that example. Prettier made the state of modern web development so much better.
dentemple 7y ago
Most ancillary files aren't getting shipped to the user, so what's the point in complaining? Unless you're seriously arguing that extra documentation is a bad thing?
baxuz 7y ago
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.

wilsonrocks 7y ago

A lot of people think a README file is important.

apazzolini 7y ago

Right, OP totally should have included the interview question requirements as a commented block at the top of index.html instead of separating it out. It's way too complex as is. And definitely, .gitignore is well known to be responsible for the "complexity of web development." Maybe we should include .gitignore in index.html too?

anarchodev 7y ago
GitIgnore.jsx IMO

StreamBright 7y ago

These files are supposed to be in every single folder nowadays.

cc81 7y ago

>.prettierrc Just to take that example. Prettier made the state of modern web development so much better.

dentemple 7y ago

Most ancillary files aren't getting shipped to the user, so what's the point in complaining? Unless you're seriously arguing that extra documentation is a bad thing?

baxuz 7y ago

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.