But really, the admissions were really nothing much, I'm actually surprised that's all they got. The former minister was forced to resign under allegations of corruption and was/is under investigation for it, no big surprise. And the talk about having access to Ljubljana's mayor (and that he is "for sale") - well that's been in the news for years, he's under several open investigations and many more were already closed (he always comes out victorious - either because he's innocent and it's all just hearsay, or more likely because he's extremely good at dodging liability and covering his tracks). The rest is just people who used to have some power trying to appear like they still have in order to impress a potential employer or get a business deal (that was the agents' cover).

Again, I hope the authorities are combing the tapes for evidence, but it really wasn't anything bombastic. That the Israelis were doing this on the other hand...

Dependency injection is great as long as its internal working can be easily understood. I've worked with projects where dependency injection comes in various contexts (application scoped, request scoped ..) and there are always problems with that, sooner or later.

Guess they will have more work now

My uncle had moved to the US and either still was on a green card or had just recently got his US citizenship and thet said why risk it? .. (they were kinda cute about it though, they just wrote "Jure Grm" which literally translates to "George Bush" in our language so if anyone was actually looking, they wouldn't have fooled them for a second).

They were just bitching about politics, not planning a coup or something, yet they felt insecure, even with the US.

Also, while a nice API document is a godsend (and sadly often missing in practice), a way to generate the consuming side of the API (again via various mechanisms) is also a very useful thing.

Re-reading the page, perhaps I got it wrong and it works the other way around? Voiden uses e.g. OpenAPI files and verifies it's still compliant with them? That would work, although it's a bit of a double effort.. still, useful in many cases.

My point being: wow, I've never thought about standardizing the layout, what a marvelous thought. Not for the general public perhaps, but for some programmers it would be a godsend. The whole terminal is basically non-ergonomic on other layouts. Stuff like ./ is right together on the US layout. Similar for coding. I preach to my fellow developers and they see my point but most won't go outside of what's provided by the OS for some reason.

I don't know enough about other European languages from my "region" to make a more general standard (though I suspect it wouldn't be as simple as creating a single "eastern" one, I doubt e.g. Hungarian and Polish have so much in common) but it's a good idea, something that could be collaborated on.

What is not fine is giving away your users' personal data to pay for your analytics bill.

I talked with our then national information law official (funny fact, same person is currently president of our country), rule of thumb is if you're not using your users' personal data to pay for other people's services (e.g Google analytics) or putting actual personal data in them, you're generally fine without the banner.

Further, if you're a small shop or individual acting in good faith and somehow still violated the law, they will issue a warning first so you can fix the issue. Only the blatant violations by people who should've known better will get a fine instantly (that is the practice here, anyway, I assumed that was the agreement between EU information officers)

I've had trouble watching some of his work to their end, there was just so much WTF and random stuff.

His name on a project is for me a signal to carefully check some reviews before committing.

People went all in with things like XSLT and namespaces, Java became the "language that transforms XML into stack traces" for no good reason and complex XML monstrosities were considered normal so when something simple came along it was a much needed breath of fresh air (we were even prepared to overlook its lack of comments). If it wasn't JSON it would have been something else, I'm sure.

I've worked with the Java implementation for writing Office files, the Apache POI. The internal package names for these classes are "hssf", "hwpf" and so on. It's not very obvious why until you Google it and, well, "hwpf" stands for "horrible word processor format", "hssf" is "horrible spreadsheet format" and so on. Implementing these things is often difficult for good reason, and sometimes for not so good reasons, but this is the first time I've encountered developers expressing such direct hostility towards what they were trying to implement.

But otherwise, Obsidian can be synced quite nicely whichever way you want (I use SyncThing personally), and the Obsidian developers actively encourage you to do so, even if that means they don't get your subscription money.

As for extending its functionality, plugins are really powerful, approachable and in general a joy to write (I wrote one for my private use, using the JS framework I know and not the one suggested by Obsidian, and it still works wonderful, I use it almost every day).

I really love Obsidian, matching its feature set will be no easy task for an open source project.