1,116 karma · joined April 19, 2022
Edit: should we call them "special agents"? ;-)
I very much agree. A million dollar tech salary isn't that though.
Edit: the reason for avoiding this in the past was name-spacing. But the standard says you can use a hyphen and then you're OK, native elements won't ever use a `-`.
Edit 2: also it's great because it works fine with CSS selectors too. Write stuff like `<image-container>` in plain HTML docs and it's fine.
Edit 3: but also `<albums>` tags and etc which won't be adopted into the HTML standard soon work too if they don't conflict with element names, and the rare case that they might be adopted in the future as an element name can be resolved with a simple text search/replace.
Edit 4: This all really has little to do with javascript, but you can use `querySelector` and `querySelectorAll` with any of these made up names the same as any native name too.
It's very nice to write. I used and liked vue for a little while when it was needed(?) but modern HTML fills that gap.
Edit: Oh, it's simple. This is the version broadcast on The Simpsons TV show in 1989 and I must have heard it second-hand from my fellow students who were allowed to watch the Simpsons.
We use flask and go at work. I've been micro-framework or roll-my-own-framework most of my career. Go is new for me though, and it's grown on me enough that it's what I prefer for new web-facing projects even for little personal things.
Edit: oh right! Also the toplap documentary from 2005 has some actual video of early live coding performances from this community. https://archive.org/details/toplap-documentary
I hope this becomes common knowledge! There was a period somewhere between when the web platform didn't have good tools to make web applications (plus DOM manipulation was slow) and the mainstream adoption of es2015 in browsers when it made sense to do things like create a virtual DOM to allow for unavailable features at the expense of performance. It did have its place, but we don't need it anymore.
Remove a layer. In 2025 ES6 is ready for prime time, indeed.
Edit: for a more practical example, you don't need to go down the web components rabbithole just for native reactive components, MutationObserver can watch for your template fragments entering and exiting the DOM and run your init/destruct routines on them. Now you can just push HTML back from the server with fetch or xmlhttprequest or whatever, and as soon as your component's HTML enters the DOM it will be "hydrated" by your init routine via MutationObserver. Honestly, add some event signaling and XHR and you're further along to a smooth SPA-like experience than you might think.
Yeah, fair. :-) I live in a small town, the only check I write is my rent check, which I literally walk across the street to deposit. But I still on rare occasions receive checks as well.
I'm happy with my framework 13 four years later. I might switch to the stiffer hinge and/or a matte screen in the future. Might try one of the AMD mainboards in a few generations when they're cheaper and put my current mainboard into another case...
Edit: FWIW I bought a macbook air M1 a year after getting the framework 13, and ended up selling it. The battery life on the macbook air was significantly better, but I can still spend an entire workday in the park with the glossy framework 13 without needing to recharge so the extra battery life from the M1 didn't really have a ton of value for me.