No he is saying that many smart devices ignore your DNS (pi-hole) as they hardcoded their DNS address to 8.8.8.8. So it is important to have an additional layer to block at the firewall.

Prettier doesn’t allow me to control line wrapping.

does biome allow control over this? i don’t want long line to be inconsistently wrapped into multiple lines, and i want short array to be kept at multiple lines

it is HTJS now

React it is then 😄. It only has 2 dependencies:

- react
    - loose-envify
        - js-tokens

https://www.npmjs.com/package/react?activeTab=dependencies

Likely they want a lower time complexity.

for example a question can be trivially solved in O(n^2). but there is no know < O(n) solution, so they ask for O(n)

What do you want to use for frontend framework then?

python, ruby, java, C? Invent a new language?

you will see me screaming “X is for Y, it should have never been a whole framework for a frontend”

By banishing the bad part of the language with linter.

For instance, standard eslint preset has rules that enforce usage of ===, https://eslint.org/docs/latest/rules/eqeqeq

These rules often come with project starter template

Looks confusing at first, but I found it nice for accessing a month array.

const months = ["Jan", "Feb", ...];

months[0] === "Jan";

const label = months[date.getMonth()];

google for the things you want to host and append “termux” to it, e.g.:

• nextcloud on termux
• piped on termux

joke aside, story point can be quite arbitrary

npm ruin dev

npm ruin lint

npm ruin build

Wait… hosting on tor is free?

I have tested the code in both Chrome and MS Edge.

Is anything else running on the same page that you are testing?

You can test this in an empty environment like this: Enter this in your URL, “about:blank” and test the code in the console.

Here is the code for anyone else who want to try

async function slowLoop() {
    while (true) {
        console.time('sleepDuration')
        await new Promise(resolve => setTimeout(resolve, 1000))
        console.timeEnd('sleepDuration')
    }
}

It is not suppose to deviate too much. setTimeout will execute whenever possible at / after the given timeout duration. I am getting between 1006 to 1023 on my sysyem

Is your device performance starved during this test?