Inline means that your element should be treated like text. If your element is not text, then you shouldn’t use inline. In this screenshot the element is text, so it’s ok.
Inline means that your element should be treated like text. If your element is not text, then you shouldn’t use inline. In this screenshot the element is text, so it’s ok.
Inline is never needed and you already know that.
There’s nothing hard about semantic naming. Especially when you’re separating your elements into components and use SCSS or some other pre-processor.
Frameworks like bootstrap are a cancer.
Add a flag.
Yeah, why not?
If it calculates personal income tax, just call calculatePersonalIncomeTax
.
Hard disagree - that’s just dumb:
// Calculates tax
function calculateTax() { }
It’s not up to me. Or you.
Because no one is using JSON.parse directly. Do you guys even code?
You should remember that the gun death rate in the US is only three times lower than in Ukraine during an active war. US is a fucking war zone!
Plastic is better for the environment than everything else.
It’s done less and less because recycling plastic bottles is better.
Glass bottles are much much worse for the environment.
You’ve replied to the wrong person.
What’s the point of your schema if the receiving end is JavaScript, for example? You can convert a string to BigNumber, but you’ll get wrong data if you’re sending a number.
Why are you so ignorant?
Well, the issue is that JSON is based on JS types, but other languages can interpret the values in different ways. For example, Rust can interpret a number as a 64 bit int, but JS will always interpret a number as a double. So you cannot rely on numbers to represent data correctly between systems you don’t control or systems written in different languages.
Yaml is cancer.
No.