Circa 2006, I was in college, and I got hired to write a webapp for a college department. I didn't know JavaScript could have classes and capture variables, so I made the app with entirely global variables and plain functions combined with `eval`. It's over 2000 lines, and nobody after me could understand it.
I develop experimental software where backwards compatibility is the least of my concerns.
To avoid the SemVer nonsense imposed by Go and NPM, I simply name every version to be 0.0.yyyymmdd derived from commit date.
If Ubuntu and DPDK can name their versions by date, why can't I?
I run a small apt repository without signing, delivered over HTTPS only.
Then I tell users to put `trusted=yes` in the source line.
There's no APT signing key, no risk of compromise, and no need to backup.
IFRAMEs still require a top-level page and their positions still need CSS.
I usually use FRAMESET and FRAMEs: they are positioned perfectly in a grid, with no need for CSS or TABLE.
There's no postMessage API: you can write <A target=other-frame-name> to navigate to a page in another FRAME.
HTML5 doesn't have FRAMESET, but all the browsers still support HTML4 perfectly.
Several years ago, I wanted to make a huge lookup table in Node.js during a research project, but the program stopped making progress after a while.
This incident was detailed in my Quora answer:
https://www.quora.com/What-would-you-need-64GB-of-RAM-for/an...
I incorrectly concluded that Node.js has a limitation on how much memory it could use. After reading this article, I now understand that the real reason is that I'm setting too many properties on an Object, exceeding V8's limitation.
This ensures my LOL is authentic.