Well, 2 wrongs make one right, don't they?!
I wish we'd first fix women's rights and then extend their duties. What the OP does is just egoistically trying to make other groups also suffer.
I don't have intentions to justify an injustice. I'm saying why should we try to make it even harder for a disadvantaged group? It does not help a single German man if women also have to comply to this law.
Fixing women's rights on the other hand gives everybody the benefit of living in a society that is more fair. For me, that's a valuable goal.
As you said, you can only object if it goes against your conscience, but if you are against it for political reasons (e.g. you don't think its worth it to die for Germany), that's not a valid reason and your objection will be denied. They were also incredibly strict during the Cold War, only easing off a bit afterwards when they wanted a smaller military.
What's a reason that is politically and not against one's conscience? I assumed that one's political beliefs would also manifest in conscience.
The cold war has been over for a very long time. The whole process was reformed in 1984 by removing the mandatory oral hearing. Sources say that acceptance rate was above 90% after 1995. That's not good enough (should be 100%), but not terrible either.
> What's a reason that is politically and not against one's conscience? I assumed that one's political beliefs would also manifest in conscience.
For example, I don't think it's in my interest to defend or die for the German state. However, I would use violence to protect my life if someone tried to kill me or threatened my life directly. The German state would interpret this as a political objection rather than a conscientious one, since I am willing to use violence in principle. If I could convince them that I would let someone kill me without defending myself because I categorically reject violence for any reason, they might consider that a conscientious objection.
> Sources say that acceptance rate was above 90% after 1995.
Yes, as I said, after the Cold War, Germany no longer wanted to maintain such a large army, so they started accepting any reasonably well-written argument. But in any war, you can see that nation states will start struggling to recruit new soldiers as it becomes obvious to the population that it's a rather pointless endeavour to die for their state. So, they start forcing people. We've seen that in Russia, Ukraine, Israel, USA, etc.
>If I could convince them that I would let someone kill me without defending myself because I categorically reject violence for any reason, they might consider that a conscientious objection.
That is a complete fantasy of yours. Political convictions are explicitly stated as a valid type of justification for conscientious objection by the Act on Conscientious Objection to Military Service. It even states the reasons do not have to be logical or objectively comprehensible, which easily covers your "I'm not opposed to all violence in all theoretically cases, but I fundamentally reject service for the German state".
Thanks for clarifying! I did some own research and apparaently in those oral hearings, objectors were often tricked into contradicting themselves with quite absurd scenarios.
On the contrary, it says that even if you object, they can force you into "alternative service" without the use of arms. So they make you a soldier without a gun, or rather - a state slave.
Why does Deutsche Bank pop up in every shady financial deal? Cum Ex, business with Russia, Epstein, some shady deals with his Wingman Trump, and many more. Billions paid in fines, penalties, and settlements. How rotten can an institution be?
Is this based on your experience or is it just an assumption?
I only have anecdotes, but it does not reflect your claims, rather the exact opposite.
A lot of the boilerplate code doesn’t need to be type annotated, but annotating the main business logic doesn’t take more time and is not more complicated, but instead type annotations help write code that is more clear, more obvious, and it adds some kind of documentation.
It really depends on how you tackle gradual typing on a project level. The easiest way to sabotage is a "any new code must be fukly type checked" requirement, because it often means you also need to add type hints to any code you call, which leads to Optional[Union[Any]] nonsense if you let juniors (or coding assistants) go wild.
As always, no fancy new tech is a substitute for competent project management.
I never understood why AOT never took off for Java. The write once run anywhere quickly faded as an argument, the number of platforms that a software package needs to support is rather small.
Developers pay for tools gladly when the pricing model isn’t based on how much money you’re making.
I’m happy to drop a fixed 200e/mo on Claude but I’d never sign paperwork that required us to track user installs and deliver $0.02 per install to someone
Especially not if those kind of contracts don't survive an acquisition because then your acquisition is most likely dead in the water. The acquirer would have to re-negotiate the license and with a little luck they'd be screwed over because they have nowhere else to go.
That is something that I never understood, that that's even legal. You enter into an agreement (let's call it a contract, because that's how the other side treats it) and then, retroactively they get to pull the rug right out from under you.
I made the 'FOSS all the way' decision somewhere in '96 or so but unfortunately our bookkeeping system and our own software package only worked on Windows (this was an end-user thing) so we had to keep one windows machine around. I was pretty happy when we finally switched it off.
The funny thing is that I wouldn't even know where to start to develop on/for mac or windows, Linux just feels so much more powerful in that sense. Yes, it has some sharp edges but for the most part it is the best thing that could have happened to the world of software development.
I have done native cross-platform projects in https://wxwidgets.org/ and https://quasar.dev/ . Fine for basic interfaces, but static linking on Win64 gets dicey with lgpl libraries etc. YMMV
For iOS targets, one must use a MacOS environment with a non-free Apple developer account.
Personally, I like Apache 2.0, and standard quality of life *nix build tools. Everything Windows runs off a frozen VM backing image KVM COW file now, as even Microsoft can no longer resist the urge to break things. =3
Depends on the use-case, anyone that has seen the commercial host scaling cost of options like MATLAB usually ported to another language. lesson learned...
Commercial licensing is simply a variable cost, and if there is another FOSS option most people will make the right call. Some commercial licenses are just Faustian bargains, that can cost serious money to escape. =3
If we ignore gcj was never production ready, and basically the only good case that Red-Hat sponsored was to compile Eclipse, which was usually slower than
using the JIT anyway.
And that around 2009, most of the team left the project, some went to OpenJDK, others elsewhere, while GCC kept it around because gcj unit tests stressed parts of the GCC that weren't tested by other frontends, until the decision came to remove it completly.
As side note, I expect a similar outcome to gccgo, abandoned since Go added generics support.
Actually you do indirectly, via Windows licenses, Office, Azure, Visual Studio Professional and Ultimate licenses, C# DevKit.
Also you are forgetting AOT first came with NGEN, .NET Native, commercial, and on Mono side, Xamarin had some price points for AOT optimiztions, if I recall correctly.
However this is a moot point, you also don't pay for GraalVM, OpenJ9, or Android.
> I never understood why AOT never took off for Java.
GraalVM native images certainly are being adopted, the creation of native binaries via GraalVM is seamlessly integrated into stacks like Quarkus or Spring Boot. One small example would be kcctl, a CLI client for Kafka Connect (https://github.com/kcctl/kcctl/). I guess it boils down to the question of what constitutes "taking off" for you?
But it's also not that native images are unambiguously superior to running on the JVM. Build times definitely leave to be desired, not all 3rd party libraries can easily be used, not all GCs are supported, the closed world assumption is not always practical, peak performance may also be better with JIT. So the way I see it, AOT compiled apps are seen as a tactical tool by the Java community currently, utilized when their advantages (e.g. fast start-up) matter.
That said, interesting work is happening in OpenJDK's Project Leyden, which aims to move more work to AOT while being less disruptive to the development experience than GraalVM native binaries. Arguably, if you're using CDS, you are using AOT.
It simply defaults to an open world where you could just load a class from any source at any time to subclass something, or straight up apply some transformation to classes as they load via instrumentation. And defaults matter, so AOT compilation is not completely trivial (though it's not too bad either with GraalVM's native image, given that the framework you use (if any) supports it).
Meanwhile most "AOT-first" languages assume a closed-world where everything "that could ever exist" is already known fully.
I'm not sure how much Hotspot can do this, but JIT means you can target different CPUs, taking advantage of specific extensions or CPU quirks. It can also mean better cache performance because you don't need branches to handle different chips, so the branch is gone and the code is smaller.
reply