And don’t forget about namespaces. Look at formats like HAL and ODATA that try to add HATEOAS onto JSON.
And don’t forget about namespaces. Look at formats like HAL and ODATA that try to add HATEOAS onto JSON.
Why? JSON hasn’t given us anything XML hasn’t, except maybe a bit of terseness.
I do agree SOAP is a bit over engineered, though, but that’s not the fault of XML.
We were using XML for that before JSON.
After spending enough time debugging Jenkins pipelines, I wish I had used shitty bash scripts.
If you’re reading this, you probably live in a country that is a party to United Nations Convention Against Torture.
If your company is allowing this, please contact your government or another member state.
Ya, streams may seem tedious (why do I have to call stream and collect?), but it’s like that for performance (and probably backwards compatibility).
If writing readable code is not peformant, then the language implementation needs to be fixed.
Not sure if this will help you, but I always do shutdown and then think about whether I want to do -r or -h. I’m sure it won’t help 🙂
And it must work on mobile.
I think of it more as archaeology. Going through layers of history to figure out wtf happened.
Ya, having null semantics is one thing, but having different null and absent/undefined semantics just seems like a bad idea.
People probably complain if their box isn’t full so they stopped doing that. Not worth the time to explain it to unreasonable customers.
This picture clearly demonstrates that the original picture is, in fact, select-a-size since they are 1/2 size instead of full size.
Yeah, network tetris. Played that a ton, too!
I’ve mapped U to <C-r>.
And the window?
That is not a firefox, it’s just a regular fox.
This is why I always write my methods from bottom to top. This way I’ve always got a return statement and I use my variables before they are even declared.
It would be pretty useless if cd was a child process that changed its own directory, only to return to bash and be back where you started.