The Official Funny Stuff Thread™
-
@boomzilla said in The Official Funny Stuff Thread™:
@raceprouk Your M fell over.
˙ʎɥʍ s,ʇɐɥʇ 'ʞunɹp s,ʇI
-
-
@polygeekery
return E_NO_CAP | E_NO_NUMBER | E_NOT_SPECIAL | E_TOO_SHORT;
-
North Korea announces immediate and unconditional surrender.
-
-
-
@cartman82 said in The Official Funny Stuff Thread™:
@polygeekery said in The Official Funny Stuff Thread™:
@cartman82 would have a field day with this:
What a looser.
I have my CV build system based on yaml, as is right and proper.
downvoted for yaml
-
@yamikuronue said in The Official Funny Stuff Thread™:
downvoted
forby yamli
-
LOCKED FOR JEFFINGOpen for posting
-
-
-
@anotherusername said in The Official Funny Stuff Thread™:
Is that a power distribution control room? Looks pretty old...
-
@yamikuronue said in The Official Funny Stuff Thread™:
downvoted for yaml
Don't tell me you prefer JSON…
-
@asdf Sure. It's not great, but anything's better than yaml. I'd rather use XML.
-
@yamikuronue said in The Official Funny Stuff Thread™:
It's not great, but anything's better than yaml. I'd rather use XML.
:P
I prefer JSON over YAML too.
-
-
http://i.imgur.com/AKPu1FD.png
Puss in Kinky Boots
-
@rhywden said in The Official Funny Stuff Thread™:
Above: An example of type hinting in a duck-typed language.
-
-
@boomzilla "arms dealer" XD
Filed under: Do Not Enter Into Arms Deal With Remaining Arm
-
-
@yamikuronue said in The Official Funny Stuff Thread™:
@asdf Sure. It's not great, but anything's better than yaml. I'd rather use XML.
Why?
-
@boomzilla now that I think about it, it would've been more consistent if she said "fingers 5/10" instead, so all of the ratings would be x/10.
-
@boomzilla said in The Official Funny Stuff Thread™:
Seems like someone full of disarming wit and charm.
-
@masonwheeler said in The Official Funny Stuff Thread™:
@yamikuronue said in The Official Funny Stuff Thread™:
@asdf Sure. It's not great, but anything's better than yaml. I'd rather use XML.
Why?
Spaces. Fucking spaces. Yaml is basically the markdown of formats.
-
@yamikuronue said in The Official Funny Stuff Thread™:
Spaces. Fucking spaces. Yaml is basically the markdown of formats.
I thought Markdown was the Markdown of formats. :P
Seriously, though, can you elaborate? I've got a personal project that does a lot of data storage work in JSON, and I've heard a lot of good things about YAML. I've been seriously considering changing things to use YAML for various reasons. What are the downsides?
-
@masonwheeler I liked the idea behind yaml, just like the idea behind markdown is good. But yaml is super picky about spaces, because it has to be -- it looks human readable, but is actually a very strictly parsed language. So you have one extra space or one too few somewhere in the middle of a 100-line config file, and you have to guess at where it is, because you won't get an intelligible error. A missing space or an extra space will give you "Error while parsing a block mapping" or worse "Error expected <block end>, but found '<block mapping start>'"
In Ansible, you'll get some gibberish failure to parse error that has no relation to where you're looking, but in Rancher, you just get an error with no explanation. The Rancher catalog is a yaml-based system where if it can't parse a specific version, it just doesn't show up; Docker-compose just barfs with "invalid compose file" or some such when that part's screwed up. Who wants to go space-hunting in the middle of a failed deploy? Not fun.
I have to run everything through a linter before I save it these days. What's really insidious is that it tries to guess what your indent style is, then holds you to that strictly. So from file to file the indents might be totally different, and we're never quite sure if it's significant or not.
So basically, all those times you try to markdown something and it comes out wrong and you have to go back and fix it, but in your application-parsed config file with terrible errors.
-
@yamikuronue said in The Official Funny Stuff Thread™:
@masonwheeler I liked the idea behind yaml, just like the idea behind markdown is good. But yaml is super picky about spaces, because it has to be --
Hmm. As I understand it, it more or less uses Python indentation style. What's your opinion on Python?
it looks human readable, but is actually a very strictly parsed language.
The in me wishes to point out that this is still human readable; it's just not particularly human-writeable.
So you have one extra space or one too few somewhere in the middle of a 100-line config file, and you have to guess at where it is, because you won't get an intelligible error. A missing space or an extra space will give you "Error while parsing a block mapping" or worse "Error expected <block end>, but found '<block mapping start>'"
Ugh. Python parsers can do a lot better than that.
Ansible
...
RancherWhat are those?
The Rancher catalog is a yaml-based system where if it can't parse a specific version, it just doesn't show up
Swallowing errors?
Docker-compose just barfs with "invalid compose file" or some such when that part's screwed up. Who wants to go space-hunting in the middle of a failed deploy? Not fun.
Ugh! Yeah, that sucks! :(
I have to run everything through a linter before I save it these days. What's really insidious is that it tries to guess what your indent style is, then holds you to that strictly. So from file to file the indents might be totally different, and we're never quite sure if it's significant or not.
Oh, lovely...
So basically, all those times you try to markdown something and it comes out wrong and you have to go back and fix it, but in your application-parsed config file with terrible errors.
Ugh. Yeah, that sounds like a whole lot of no fun.
What's generating these config files?
-
@masonwheeler said in The Official Funny Stuff Thread™:
What's generating these config files?
Humans at a terminal.
-
@yamikuronue Yeah, see what I mean? Human-readable, not human-writeable. :(
(Incidentally, I've heard the same said about both XML and JSON.)
-
@masonwheeler XML is wordy and long-winded and gross, but at least you can tell where the error is easier. A closing tag is easier to spot than a space.
-
-
@yamikuronue what, no joke about yami with yaml?
-
@wharrgarbl said in The Official Funny Stuff Thread™:
what, no joke about yami with yaml?
It's no laughing matter…
-
@yamikuronue said in The Official Funny Stuff Thread™:
A missing space or an extra space will give you "Error while parsing a block mapping" or worse "Error expected <block end>, but found '<block mapping start>'"
Sounds like you're using a shitty parser. Not exactly the fault of the format itself.
-
@yamikuronue said in The Official Funny Stuff Thread™:
What's generating these config files?
Humans at a terminal.
Found the problem. An IDE might help…
But XML or JSON are certainly not good alternatives. Maybe TOML?
-
"Come back here you!"
https://i.imgur.com/BmwzzTn.gifv
-
@asdf said in The Official Funny Stuff Thread™:
Found the problem. An IDE might help…
But XML or JSON are certainly not good alternatives. Maybe TOML?
My IDE has syntax support for XML, JSON and YAML (among other things). :p
Admittedly, I've got more plugins added to Eclipse than the average developer would think wise, but it does mean that it gives me a lot of assistance for most tasks (given that C# is a non-goal for me).
-
-
-
-
-
-
-
-
-
-
@tsaukpaetra said in The Official Funny Stuff Thread™:
I don't understand any of these...
I guess they're supposed to be anti-jokes.
-
-