Readit NewsAustralia has a progressive tax structure, right? If you have multiple income sources how does each source know the proper withholdings? How do they know what deductions you'll be eligible for or are wanting to take?
If it works anything like what we've got in Norway, they take a rough percentage, and once every year when the taxes are filed, the IRS equivalent charges or repays the missing amount.
Related, I use Lightstream and their documentation[1] actually suggested to use synchronous=NORMAL. Any idea if this is a wise change? Should I revert back to the default of FULL using WAL + Lightstream?
Litestream is already backing up your changes, so synchronous=normal seems reasonable.
Additional features that would make me consider switching:
- jujitsu support
- IDE plugins
- code-base CI
P2P VCS doesn't cut it for me.
What sort of IDE plugin are you thinking of? As long as you have a git plugin it should work just fine (if you're thinking of something similar to github/gitlab plugins then I don't think there are any, but I'm not sure what those buy you).
It's possible to setup CI: https://app.radicle.xyz/nodes/ash.radicle.garden/rad%3AzwTxy...
Are there any differences from git, or tbh is there a project I can maybe contribute to on Radicle and learn from experience?
Can pitch in with helping out Windows support
It's "just" git, but you push to a special remote which will synchronize your repo on a p2p network.
There's also a CLI for issues and pr's, which also get's stored in your git repo.
Anyone using radicle for a project with external contributors?
I've tried it with some of my projects and it seems promising, but I wonder what it'd be like to use it on one of my more successful projects.
The JVM being a stack-machine is probably the least controversial thing about it. Wasm, CPython and Emacs all also have a stack-based bytecode language. The value, of course, comes from having a generic machine that you can then compile down into whatever machine code you want. Having a register machine doesn't seem very useful, as it's completely unnecessary for the front-end compiler to minimize register usage (the backend compiler will do that for you).
Specifying classpath isn't fun, I agree with that. Launch performance isn't good, and is generally a consequence of its high degree of dynamicism and JIT compiler, though of course there are ways around that (Leyden).
> I've written entire programs in JVM bytecode, without a compiler, and I see very little of value in it
I agree, I also see very little value in manually writing JVM bytecode programs. However, compiling into the JVM classfile format? Pretty darn useful.
Requires fewer instructions, so potentially faster evaluation, which is good for short-lived programs that ends before the JIT kicks in.
Stack machines requires less space per instruction, however, which reduces the size of the program (faster to load).