Or they are visually impaired and their a11y stack is not there yet

To be fair, having multiple country that has open source governing body would help to have a redundant in case one country goes mental

SEA market is not a good one for high end stuff. Until they can get big enough to make budget level THEN they may get into Indonesia officially

It does make me wonder tho, because I know universal power supply exists. But the question is how efficient it is and how much would it save cost by having a single type of optimized manufacturing line compared to 2.

Edit: Hmm, I just realized they could make a variant of the same PCB so I guess the cost saving is moot point

A switch is an input type checkbox isn’t it?

This is how bluesky does it. So as I mentioned earlier, it is the user that opt to be moderated and they can choose their moderator.

I would like to add something too because I only remember it just now. But I recall someone mentioned that bluesky moderation is unique and I quite like the idea but I’ve never used bluesky myself so idk how true it is. Basically, an account chooses who to trusts to be a moderator for said account. So that content that is curated by said moderator is the one that the account sees. If the account opt to not be moderated then it can see everything

Because whether you agree or not, sandbox is a necessary for banking app. No other app should ever be able to EASILY (emphasis on easily) perform arbitrary read on the banking app data.

Until web standard can agree to have device bound session, it won’t happen. Cookie stealer malware is just too dangerous to perform financial transaction. So maybe for read only stuff it is fine

That’s more in line with what I was thinking, yeah. The rest is just hoping that people will not abuse the tag (which, with enough mass, the noise would probably be drowned out by genuine people anyway)

Implementation wise, I think it would be like tagging. See how many people tag the post as what

I only need ORM to have the flexibility of DSL table modeling for repeated fields. Think, createdAt, updatedAt, id (and the PK that comes with it), etc. After the migrations are written, I prefer to use a query builder

Please save yourself from lunacy by using pnpm. You can always use shamefullyHoist to get the npm compatibility

I am surprised this is not the norm, It looks like that this person have a tendency to lean into the extreme (like with his previous blog about chaining). I always feel like every syntactic sugar of any kind are to be treated like any other design/style philosophy. Too much of it is not good. Look at Java that is OOP to the extreme. Any language would quickly became unusable if any one of the features/design philosophy are (ab)used.

Not to the degree where bun support it. But NodeJS itself has now supported running typescript for a while

Extended attributes are not KDE specific. KDE just utilize that feature while others just don’t

The post already addressed that. JWT do have their place and that’s mainly for server to server handoff with short lived lifespan. After which, the recommendation is using Device Bound Session Cookie

It means manufacturers are now eyeing linux as a viable marketable product. If they can pocket the difference between the windows license no matter how cheap, you bet they would do it

For Proxy specifically, that is how vue ref is actually implemented. By making a proxy so you get reactivity.

Alternatively, just do it sqlite style. Open source, closed development