"This is what I've always found confusing as well about this push for AI."
I think it's a few things converging. One is that software developers have become more expensive for US corporations for several reasons and blaming layoffs on a third party is for some reason more palatable to a lot of people.
Another is that a lot of decision makers are pretty mediocre thinkers and know very little about the people they rule over, so they actually believe that machines will be able to automate what software developers do rather than what these decision makers do.
Then there's the ever-present allure of the promise that middle managers will somehow wrestle control over software crafts from the nerds, i.e. what has underpinned low-code business solutions for ages and always, always comes with very expensive consultants, commonly software developers, on the side.
The US does not set out to capture civilians, while the hamas does. It matters. All the rest of the comment makes no sense in light of that.
Also you omitted the part where I said I disagreed with what Israel did. But as a human I believe we are evil like that, and I am really sorry about it.
Israel didn't take responsibility for those until October 7th. Now clandestine operations happen all the time, like the Iranian bombing on Jewish center in Argentina in 1994: https://en.wikipedia.org/wiki/AMIA_bombing
While I understand why Israel would want to target Iranian nuclear scientists, I find it much harder to comprehend why Iran would go out of their way to bomb a Jewish community center in South America.
What editor you are using has no effect on things like copyright, while software that synthesises code might.
In commercial settings you are often required to label your produce and inform about things like 'Made in China' or possible adverse effects of consumption.
There are many techniques. You're most likely to come across things like declarative DSL:s and macros, then there are things like JAXB and similar tooling that generates code from data schemas, and some people script around data sources to glue boilerplate and so on.
Arguably snippet collections belong to this genre.
It's a tool used to build other tools, some of which have non-trivial amounts of users.
It's also a tool used by e.g. journalists and government agencies that dabble in stuff like research and evidence, and it would probably be more cumbersome for everyone involved if Google instead had to process requests and provide copies of material for these purposes.
Otherwise they'd probably have made life much harder for the yt-dlp-developers already. Not that I think they're nice in any way, but I don't think they're seriously trying to fully eradicate yt-dlp or related software.
Such a weird take. What are the similarities between your fantasies and land that to you make the philosophical convictions involved in private property laws applicable to those fantasies? Why isn't it good enough for you to fantasise about land and a tree, and why doesn't the answer to this undermine your reasoning?
Personally I'm not convinced by the arguments for private property, which makes your comparison even weirder than you likely intended.
Jakarta was chosen by the Eclipse Foundation because it is the largest city on the island of Java, and Oracle is virulently litigious around the Java trademark.
In the Java world it is rather common to use something called application servers. These are meta-applications that provide your applications an environment with things like database abstractions and the like, as well as admin interfaces.
It solves some of the same problems you might reach for Kubernetes or OpenShift for, your application gets access to external resources in structured ways and you get to look at dashboards.
GlassFish is an example of such an application server. WildFly is more common, and is the artist formerly known as JBoss. If you have some knowledge in the enterprise Java ecosystem you can quickly and easily (or maybe not, it depends) deploy your creations into these.
I think it's a few things converging. One is that software developers have become more expensive for US corporations for several reasons and blaming layoffs on a third party is for some reason more palatable to a lot of people.
Another is that a lot of decision makers are pretty mediocre thinkers and know very little about the people they rule over, so they actually believe that machines will be able to automate what software developers do rather than what these decision makers do.
Then there's the ever-present allure of the promise that middle managers will somehow wrestle control over software crafts from the nerds, i.e. what has underpinned low-code business solutions for ages and always, always comes with very expensive consultants, commonly software developers, on the side.
reply