magic_lobster_party @ magic_lobster_party @kbin.social

Posts

2

Comments

580

Joined

2 yr. ago

Screen locking yes, but that’s not screen saver.

Who even uses screensavers these days?

It was quite the Wild West with early browsers. Different browsers could interpret the same site in different ways. Some browser added their own functionality as they wished. There were no strict standards. Web developers didn’t exactly follow the W3C standards either. And then you could always do it in a Flash or Java applet if browsers didn’t support what you wanted.

This was also the time with the most diverse set of browsers. Today the web standards are much more formalized and more strictly followed, and ironically this is also the time where almost everybody use different flavors of Chrome.

Are you sure your code isn’t just overly convoluted?

Plot twist: it’s the team lead who goes on a leave

I use jq pretty much every day

Do you say weekend or weekends?

AC6 is already a Rusty dating sim

Ahem, it’s called Poe’s law

I would if it wasn’t so unbearably long. Only for the announcements though.

Indenting copy pasted yaml is always a pain in the butt. Any indentation you give is likely a valid yaml. Especially bad considering indentation has a significant meaning. You have to double check back and forth to ensure nothing bad has sneaked in.

With JSON there are no such discrepancies. It’s likely the editor has figured it out for you already. If it hasn’t it’s easy to prettify the JSON yourself.

JSON for serialization all the way. It’s simple and to the point. It does one thing and does it well. There’s little room for annoying surprises. Any JSON can easily be minified and prettified back and forth. If you want it in binary format you can convert it to BSON.

Yaml is too much of a feature creep. It tries to do way too many things at the same time. There are so many traps to fall into if you’re not cautious enough. The same thing can be written in multitudes of ways.

Underwhelming is a more appropriate wording. It’s a good game. It just leaves more to be desired. Especially after all these years of development.

I have played Zelda, but not BG3, and I agree that BG3 should win.

It’s more like the entire internet that has gotten worse

Talent show judges when you haven’t stopped the cycle of reincarnation:

I think a more appropriate one would be about the sunk cost fallacy. You should realize when it’s time to take a step back and reconsider your solution. Maybe you’re missing something obvious?

I don’t agree with the second one. Sometimes you can save weeks of planning with hours of work.

Json is incredibly easy to prettify.

That’s more of a weakness of yaml. There’s so many ways to specify the exact same thing. Not exactly what you need for configuration files maintained by multiple people. It easily becomes an big incoherent mess.

In JSON the default way is the only way. Nice and coherent.