Is this gonna be equivalent of ESLint + Prettier but in one performant package?

If you use QMK you’re in luck.

https://github.com/daniel5151/qmk_firmware/blob/discipline/keyboards/coseyfannitutti/discipline/keymaps/prilik/keymap.c#L145
https://github.com/ridingqwerty/qmk_firmware/blob/cfd632e021f2460c50dd9e283426cc6e28c9a475/users/ridingqwerty/process_records.c#L297

Thank you. After thinking about it overnight, I realized I asked a wrong question. Your answer still helps greatly and get me more than half way to satiate my curiosity.
Tolerance grade and example objects that require different grade/minimum pi accuracy is what I was looking for.

TIL there is a closer approximation than 22/7

Thank you, I already skimmed through that article before posting. Maybe I failed to put my question into words properly.

I want examples similar to pool/fence circumference in the article. Along the line of “We’re building x, and this is the worst rounding we can go, one fewer digit and it will be off by y”

Regarding SEO, What’s stopping maintainers from vandalizing their own fandom page?

It would not be difficult to make a bot to update fandom page with a convincing but slightly wrong info, after a few hundred iterations, it’s all useless. Go look at what google recommend and do complete opposite. I’m convinced this will bomb ranking and put whatever wiki they migrated to at the top.

Can you explain a bit more about “zooming, different levels of detail” you mention? Maybe break them down to separate issue you are having with the library, what does it do, what do you want that it’s not doing. If there is a way to tweak it then you don’t have to build the component from scratch.

But if you already abandoned the idea of tweaking timeline-js then you can have full control in vue, have to build it yourself though. Start by breaking the functionality of the timeline into separate interaction. From a quick look, timeline-js just make style attribute reactive. Have a box? good. Now put really long div in it with placeholder texture. Can you drag/scroll it? no? grab a suitable function from vueuse and make it scrollable. Follow with markers, zoom, dummy event items, data fetching (the actual width, marker spacing, events placement can be calculated from timestamp in json after this step), lazy loading, styling, animation, so on.

I don’t know how much experience do you have with each things required (html, css, js, vue) so it is a bit difficult to give useful answer.

Events?? TimelineJS3/blob/master/API.md
Not sure what else is available if you want to build the component yourself though.

but note that because TimelineJS’s primary use case is the embedded iframe, some of these methods have not been thoroughly tested.

I think you can replicate most of its function with vue alone, skip all the tedious work with vueuse. Lazy-load with Intersection Observer. Basic events and refs for zoom level.

I would start with putting all entries into a usable format. A CMS will help a lot. Maybe a JSON from your django server containing batch of entries, its timestamp, length, importance, tags, etc. Anything that is required to place entry on the timeline properly in vue.

EDIT:
Have you tried the official tutorial?

There is a trend line of the amount of shit you need to do to get linux to do things you want.
There is a trend line of the amount of shit you need to do to stop windows from doing things you don’t want.

Those two lines have crossed quite a while ago.

For quick overview of frameworks… there is Brad Traversy and Jeff Delaney (Fireship)

Shop around and pick a few to try out then dive down when you finally find a framework you like ¯\_(ツ)_/¯

I’d love myself a hole to go in right now

maybe I should have use wojak :|

I mean… if your room have a lot of stuff then it might take a while to find the source, if you aren’t being pranked. But random screws on your desk will never be as horrifying as random maggots on your desk.

Bought one many years ago, it’s unexpectedly pricey for a 5cm paper card (48 cards). IIRC it’s their excuse is “traditional look”. The box is nice though.

Already tried that. No significant improvement over running at uncapped with v-sync (60fps).

baseline:
uncapped with v-sync (60fps)
result: running at 40% usage and 40C temp.

nvidia cp config:
capping at 20fps with or without v-sync (running in background)
result: usage jump up and down predictably between 20% and 50%, no temperature difference.

Clearly worse than capping it at game engine level since ES2 shows linear and stable drop in GPU usage. I assume this varies greatly on different game engine.

Bun no good => ☹️
Don’t have to learn another shiny JS thing => 😀

I want to have separated accounts for different sets of project…
Signed up a second account… it got suspended instantly (after I log in with my main). According to ToS, I can’t have more than one account.

Nuh uh, You aren’t the only provider. Headed to Gitlab, no more bs.

Bun is designed as a drop-in replacement for Node.js. It natively implements hundreds of Node.js and Web APIs, including fs, path, Buffer and more.

The goal of Bun is to run most of the world’s server-side JavaScript and provide tools to improve performance, reduce complexity, and multiply developer productivity.

If it can replace node and pnpm at the same time then this sounds quite good actually.

EDIT
https://bun.sh/guides/ecosystem/vite

While Vite currently works with Bun, it has not been heavily optimized, nor has Vite been adapted to use Bun’s bundler, module resolver, or transpiler.

https://bun.sh/guides/ecosystem/nuxt

Bun supports Nuxt out of the box. Initialize a Nuxt app with official nuxi CLI.

I see. I might have done things in similar way without realizing what it is by just focusing on decoupling and reusability.

BEM is are methodology about atomic code design, it gives you a standards and guides how to simplify code maintaining.

Isn’t this also what Tailwind, UNOCSS and the likes about?
Sounds like he have a problem where working in project using BEM, different team use it in different way (which I think as what to expect). And when components are involved, is CSS convention really the focus here?

edit: ok, I think I finally got your point…
How does BEM differ from OOCSS, AMCSS, SMACSS, SUITCSS?
Well… this thing feels like frontend framework with extra step.