It says she “Led the push for the Domestic Workers Bill of Rights Act, federal worker unionization”. Federal worker unionization is very undemocratic b/c federal employees essentially blackmail voters. They become untouchable.
Adobe used to have an app called Fireworks that was great for non-artists. They got it when they bought Macromedia. Too bad they killed it. I hope Graphite will replace it.
When i read the title, I thought they were finally going to fix gradle or improve maven. Those are the real on-ramps and they are a much bigger barrier to entry than main().
A cleaner/simpler alternative was Kobalt, but it’s now abandoned. A simple, official build tool would make the ecosystem easier to learn.
That’s the idea in Proof of time and space used by chia.net
You probably haven’t heard of this coin/network (invented by the inventor of bittorrent) b/c it doesn’t aim to be a speculative asset, but it does have a very sane programming model (in lisp)
Specifically, I was unable to find the gradle shadow/maven shade rules needed to use the jdk9+ version of the multi-release dependency "com.sun.xml.ws:jaxws-rt:2.3.5".
The reply I got on Stackoverflow from the person I think is the maintainer is "don't use fat jars", which is probably the correct solution, although most people use fat jars.
Lately, I've been reading that layered docker images should be a faster way to build and deploy java apps that have many tens of MB of dependencies that never change. It only works if you don't use fat jars.
Yes. But in the move to java 9 they broke java’s customary backward compatibility and left behind a lot of users.
It doesn’t help that there is no good, clear and complete guide on how to upgrade SOAP clients.
I went through this recently and learned that because jakarta uses multi-release jars, we have to do the regular dependency changes and also change our fat-jar based build/release to Docker images. In other words, they decided to throw out decades of users’ investment in learning the ecosystem.
I’m not surprised that people seem to be leaving the ecosystem.
Cedric Beust made a great alternative to Gradle called Kobalt. Unfortunately, Jetbrains went with Gradle — probably in order to associate Kotlin with a known entity.
Now we are stuck in a terrible situation where step 1 of any java/kotlin project is unpleasant because you have to write a long XML file (Maven) or a magical and incomprehensible build file in groovy/kts (Gradle).
Maybe the real problem with the paper is that it points out that GPT-3 and the like can completely distort search results by filling the web with auto-generated spam. Botnets could link spam pages to each other and even generate traffic. If that got into the wrong hands, we would be unable to distinguish truth from fiction.
If the general public heard of this, Google’s stock price might be hurt. In such a bot-filled world, humans might prefer to start their searches in walled-gardens or on sites that could better-validate content.
Have you taken a look at Pulumi? If infrastructure is going to be code, I’d like to code it in a type-safe DSL please. Otherwise refactoring is hell (as in Ansible).
Another promising effort in this direction is Jetbrains Space, which features CI config in a Kotlin DSL.