le front end not actual work amirite

I mean yeah it would be nice but software isn’t perfect and validating html is not a sexy feature.

for content sites, stateless is fine. for web apps you need states of all different kinds. even the smallest detail is a state in an application.

endpoints themselves are stateless, but the web application is stateful. you only have to build the world once, and its much friendlier for end users.

well, no. because broken html can still function sometimes. but most importantly most of html is not even “broken”, just not “adhering to the complete standards”.

html is just formatting around the content. even completely devoid of html you can still see things. we’re not writing latex here and no one cares things are a little fucky.

as far as generated html go, you’re more likely to break it further if you fuck with it anyways.

you can setup a on-save script to force you to commit when the number of changes is greater than a certain number from the previous commit.

it means you commit too infrequently. your commit messages should be able to describe what u just did within 10 words.

uh in any actual company you almost never push to origin master. so I think it’s a joke.

you can do it like you weight 6v6 then 3v3 then for the last weighing you weight the 2 out of 3.

or you weigh 4v4 to find out which grouping of 4 the light weight person is in, then do 2v2 and 1v1.

it’s top 5%…

I did look it up and there is only 1 case from 2000 that set the high bar at 125. it’s not really representative of the whole.

hear hear, if it has problem then I take it to apple store for service. I don’t wanna waste time fucking about on my laptop. I’ll do trouble shooting on desktop but I just want long battery life and apple silicone beat the fuck out of anything else.

mind explaining?

for some stuff absolutely, styling frameworks like bootstrap and others kludged together the concept of grid based designs. css grid just makes it official and more flexible.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Equality

mdn goes into it more and it’s way more involved than I thought, looks like order of operand doesn’t matter. see the number to string section

2 equal signs will coerce the second operand into the type of first operand then do a comparison of it can. so 1 == “1” is true. this leads to strange bugs.

3 equal signs do not do implicit type conversion, cuts down on weird bugs. 1===“1” is false.

edit: it appears to be more complicated than that for double equals and the position of operands don’t matter. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Equality

bro we’re on css grid now

more people the better yeah