There. I made a really, really simple and lazy personal webpage. It has nothing on it that you don’t already know about me.
But its a place where I can put stuff if I so feel like it.
@shebang It has a very highschool IT class website vibe. Amazing domain though.
@matrix Dude, I don’t know how to use or make anything. I only know how to setup things for other people with actual skills and talent to use.
@cowanon @shebang @matrix
What also doesn't help is that html 5 as a standard is constantly changing whenever Google and Mozilla feel like it. It isn't like html4 and that are the specs. Its html5 and whatever update we have now... Also lots of css but 99% js because of some dumb-ass fuck that loads 3 different frameworks.
What also doesn't help is that html 5 as a standard is constantly changing whenever Google and Mozilla feel like it. It isn't like html4 and that are the specs. Its html5 and whatever update we have now... Also lots of css but 99% js because of some dumb-ass fuck that loads 3 different frameworks.
@cowanon @matrix @shebang
Yeah, that was terrible. Or xml with stylesheets, effing cancer (only Arma3 still uses this for their squad.xml). XML is your typical enterprise typesafe format; its structured, everything requires you to specify a data type and you know what to expect. And it was a trend, hype in the late '90s and early '00s to use this format and nobody liked it. Its one of those shitty formats they tried to crossover into other formats, so you end up with xhtml, or if you like json; xjson or jsonx in which it tries to get a handle on the data-types xml offers in the freeform we know as json. Look up the specs (by IBM iirc), its stoopid.
Remember SOAP?
Yeah, that was terrible. Or xml with stylesheets, effing cancer (only Arma3 still uses this for their squad.xml). XML is your typical enterprise typesafe format; its structured, everything requires you to specify a data type and you know what to expect. And it was a trend, hype in the late '90s and early '00s to use this format and nobody liked it. Its one of those shitty formats they tried to crossover into other formats, so you end up with xhtml, or if you like json; xjson or jsonx in which it tries to get a handle on the data-types xml offers in the freeform we know as json. Look up the specs (by IBM iirc), its stoopid.
Remember SOAP?
@cowanon @matrix @shebang
Keep it that way, unless you want to fuck over your load-balancer with an infinitly running connection that isn't worth the trouble.
Unless you have an electric car and your CPO or MSP uses OCPP to communicate between your charger and their backend (or their backend with other backends). Its all fun and games until you read the old specs of the protocol. Its essentially some protocol a university student hacked together thinking it was cool to use SOAP and stuff for chargers to communicate. This idea is great until it starts scaling and you need to do weird shit with your LBs because you have 30000 chargers connecting to your backend, non-stop.
Keep it that way, unless you want to fuck over your load-balancer with an infinitly running connection that isn't worth the trouble.
Unless you have an electric car and your CPO or MSP uses OCPP to communicate between your charger and their backend (or their backend with other backends). Its all fun and games until you read the old specs of the protocol. Its essentially some protocol a university student hacked together thinking it was cool to use SOAP and stuff for chargers to communicate. This idea is great until it starts scaling and you need to do weird shit with your LBs because you have 30000 chargers connecting to your backend, non-stop.
I learned <p> </p> then was like, "There. I know enough of this."