amazing comment, thanks!

he did mention isolationist, so… we’d also have to consider how the eastern front would have evolved without lend-lease. not a historian so perhaps consensus is the Nazis still wouldn’t have had a chance, but still

it’s a bit hard to tell. of the buildings still standing and in use, the cathedral comes to mind, with was consecrated in 1238, but it stands on the site of the old mosque. this was torn down apparently in 1262, at which point construction on the cathedral began, but it would take centuries to finish everything.

there is another church that was named a parish in 1245 and so was probably already standing then, so perhaps that building is the oldest? I don’t knoe how much of that original building is still standing though

It’s one thing to just use the software, it’s another to open bug tickets that you expect the maintainer to prioritise. It’s free software, the maintainer doesn’t have to do anything for you. If they want tickets fixed with high priority, they should work something out with the maintainer.

Is the current incarnation beatable, or was that a while ago? I’m not making any progress

X11 being reliable because Xorg devs aren’t stupid

Not gonna disagree with the rest of what you said, but the Xorg devs and Wayland devs are mostly the same people

Because you can’t (easily) program gui apps to automate tasks, but combining a few terminal programs to get more complex behaviour is really easy

So from within vim :!pkill vim?

Yes please, I would love not being able to scan comments to see if they are relevant to what I’m trying to do

You could use jq, which will work no matter how the json is formatted.

Without trying it out, something like the following might work:

jq '.path.to.key.to.change |= 11' file.json > file.json.tmp && mv file.json.tmp file.json

Just pull the skin off, it takes just a few seconds

yeah man the woke libtards have gone too far, do they really expect to survive their jobs?? so privileged!

I think the main reason OOP has a well-known term and pattern for dependency injection is to differentiate these two (out of multiple) options:

• the constructor of my object creates other objects it depends on itself
• I construct the dependencies of my object elsewhere and pass them in to the constructor and use an interface to make it easy to swap behaviour

However, this becomes less of a pattern in functional programming as you wouldn’t make such objects to begin with. In FP, you pass all parameters where a function is invoked, and DI just becomes using generic parameters. You wouldn’t instantiate a dependency on each function call after all.

As this is such a minor change, it’s not really talked about much and it’s not really a pattern,