lucassen

Some «security» features dont need to be secure. This is obviously one of those as the data is readable by all, but only modifiable by «those in the know», but if someone does anyway who cares.

I’ve done hardcoded frontend identity whitelists for authorization. Some times it’s fine to let hackers access stuff, but not the vanilla mass-market browsers. Feature flags etc

Research also suggests that NAFLD is present in up to 75% of people who are overweight and in more than 90% of people who have severe obesity, also called extreme obesity.

The public is pretty fat, you know.

that scottish reference seems to explain CBI exactly as I have understood UBI.

I found caprover to be great for simple web apps. the git push and build on prod server feels like a remnant from before proper ci/cd with docker built separately was as available.

this seems to be a common attitude in America. It’s game theory, but you should look more to the nash equilibrium than the prisoners dilemma. Unfortunately it must all start with trust, which seems like the fundamental scarcity in the US

> everything (local state management, API calls, forms, URL routing, etc)

hooks, axios, html, reach-router.

my point is that if you start with the assumption that browser APIs are sufficient, there is a natural progression to your project and «taste» in supporting libraries to react

to be honest, Id say the next level abstractions(gatsby and next) fill that role. I can’t think of a SPA alternative though

what are you referring to? I fear I am one of these incompetent devs since I don’t understand the implied transgression.

I spent a little time in it and I really like DBeaver. Free tier works great.