Hacker News Reader

gorky1on Libgourou: A Free Implementation of Adobe's Adept DRM on ePub/PDF Files

That would be totally illegal if Nintendo was making the laws, but yes, pretty much.

gorky1on Libgourou: A Free Implementation of Adobe's Adept DRM on ePub/PDF Files

I'd say this doesn't bypass anything, it's just some kind of virtual device? I'm using it to read legally purchased books on unsupported hardware.

gorky1on Kobo announces color e-readers

There's an open source Adobe ADEPT DRM implementation that works well on Linux:

https://forge.soutade.fr/soutade/libgourou

gorky1on A Canadian payroll dependency chart

You're right, and it's extremely hard to undo.

Once you have that complexity, you'll always be taking away something from somebody by simplifying.

So all simplifications end up as additional "if" clauses, defeating the purpose.

gorky1on A Canadian payroll dependency chart

That's very cool, but that's taxes only.

For social security, you have to get certified by a completely different set of bureaucrats with partially incompatible requirements:

https://gkv-ag.de/

The simplifications, they are additional! (Usually.)

gorky1on If you're happy with OpenBSD, probably any computer is good enough

Intellij Idea on Linux runs surprisingly well on 15 year old T400 Thinkpads. It's actually pleasant to use for small hobby Java projects.

gorky1on Cyclic dependencies are evil (2013)

The question was "what has reflection got to do with it". I've used reflection for dependency inversion, so I think that's what it's got to do with it.

If you can do dependency inversion without reflection, more power to you :-) We can't do classpath scanning in the project I'm working on because of the size of the classpath, and compile time configuration using direct imports would introduce cycles, so reflection it is for us, in one form or another.

gorky1on Cyclic dependencies are evil (2013)

I've seen people learning about dependency inversion from a book called "Clean Architecture", then proceeding to apply it to every bit of code they write, to make it "clean". It makes code difficult to trace by reading alone. Indirection may be cheap, but it adds up.

gorky1on Cyclic dependencies are evil (2013)

It's called the "dependency inversion principle". People don't like to call it "reflection", and heap various layers like XML or dependency injection annotions on it, but technically, it comes down to reflection at runtime, as far as I've seen.

It certainly has its cost in additional complexity through indirection, but it's better than creating cyclic dependencies or giant balls of mud.

https://en.m.wikipedia.org/wiki/Dependency_inversion_princip...

gorky1on Cyclic dependencies are evil (2013)

Reflection allows you to put the interfaces to Account and Customer into a shared module and the business logic implementations into their own mutually independent modules, thus removing the cyclic compile time dependency.

You "wire up" the implementations at runtime, using reflection.

gorky1on 2017 Tax Software Developer's Guides and Test Cases

This kind of software chooses you :-)

Actually, it's quite rewarding once you get into it. Serious business, people depend on you getting it right, but still nobody dies if a bug slips by.

Getting into it requires a year or two, though.

gorky1on 2017 Tax Software Developer's Guides and Test Cases

https://www.bmf-steuerrechner.de/interface/pseudocode.jsp

There's a pdf version as well:

http://www.bundesfinanzministerium.de/Web/DE/Themen/Steuern/...

The problem is in computing the input values; it's quite hard to figure out without examples, except the most simple cases.