GTG3000 @ GTG3000 @programming.dev

Posts

0

Comments

170

Joined

2 yr. ago

I think some people expected their entire community to get up and move.

Well, perhaps that is healthier.

But it doesn't trap eyeballs.

Well for me, the real content of Reddit was finding an interesting thing and then reading a few dozen comments from people really in the know.

Here it's going to be a dozen top-level comments and maybe one of them will have a thread longer than three messages.

True, thank you.

So they're doing the same thing as that time they killed Edge and stretched its skin over chromium?

That guy has the worst presentation.

It varies with the source, but generally it's supposed to be a few things:

• The blasters used in the movie era are... Basically unstoppable? They're the pinnacle of weapon tech as far as mass arming is concerned.
• The armour is supposed to protect the stormtrooper against most "lower tech" weapons, think slug throwers, shrapnel from explosions, vibro-swords.
• Light sabers OP.
• You're supposed to be using droideka-style personal shields if you want to tank energy shots.

Of course, movies don't think about it too hard and just use them as mooks.

Less content, that is spread across multiple instances that can have duplicate communities.

You just can't keep doomscrolling here, the "active" search repeats all the time and the "best of the day" is like two pages.

And then there's specific communities that just... Stayed on Reddit.

In slav languages, you just go with how the neologism sounds. "Computer" ends in hard r, so it's masculine, for example.

Every once in a while there's going to be shit like with "coffee" though. It sounds neutral-gendered and is officially neutral-gendered, but there's been a big period when people believed it should be masculine because of the source language or some shit. Still a lot of people arguing about it.

The orient-ness of it all.

Well, there's a few things I personally think are a must for a config format:

1. It must be human readable and editable, in some way. - in many cases, you may want to go and change something in the config while the application proper isn't running. That rules out stuff like pickle or binary formats. Although I suppose sqlite and it's ilk still fulfill it, in a roundabout way.
2. It should be unambiguous, with one way to do something right. - this one's a doozie. JSON fulfills it since it's unambiguous about it's types, but many interpreted language configs will have options. And then YAML will have "no" turn into "false".
3. It should probably have comments. - handily failed by standard JSON implementations. Although to be fair a lot of parsers I've used understand comments. Or you can make a comment stripper real easily.
4. It should have obvious structure. - I've dealt with CSV configs before, I do not want to ever again.

Cue that lady Gaga music video.

Oh god, parsing complexity. I actually tried writing a YAML parser in my free time before and boy was that not worth the headache. So many little things that complicate parsing and are ignored by majority of users!

I really like python, but I can agree that it's no-delimiters style can be... Confusing at times. I definitely had to hunt down bugs that were introduced by wrong indentation. That and the way it handles global/local variables, mostly.

I do appreciate not having to enclose every key in "", and being able to copy values - but if we want that kind of logic making our configs, why not just switch to writing configurations in Lua? It certainly has less footguns than YAML and it has the niceties like "I can just write {key = "value"} instead of {"key": "value"}".

Well, I watched first few episodes before forming that opinion, I think it's just the usual "cynicism pushed to grotesque" thing many adult-oriented shows do that puts me off. But it's been a while and I don't really remember it well so I suppose another chance wouldn't hurt.

And thanks, I'll look into Strange New Worlds then.

Take your upvote and roll initiative.

Most comment-aware JSON parsers I've seen just use standard // to delineate comment lines.

Couldn't get into the Lower Decks because I am thoroughly tired of adult swim style of humour. But hey, people seem to like it and all power to them.

Don't really know what else is going on with Star Trek nowadays. Anything worth checking out?

Python has stricter rules about what can be cludged together and how.

Yaml is... Kind of nebulous, which is not a good thing for a data serialization format.

So what happens if you turn a cow into gold, machine that gold into things, then cast dispel magic?

That's fair. You could also adjust it to consume it's material components, so that you need to forage for them.

Turn it from "hunger-b-gone" to "I have a few twigs of [uniquely special] mistletoe in case we all fuck up our survival rolls and really need food".