What is the benefit of having this be a standard? Can't an agent follow a guide just as easily in document with similar content in a different structure?

Primarily this being a predictable location for agents. AI not having to fetch the sitemap or llms.txt and then a bunch of subsequent queries saves a lot of time and tokens. There's an advantages section[1] within the proposal docs.

[1]: https://www.installmd.org/#advantages

I don't think it's meant to be a point against abstraction or a point against complexity. I think it's widely understood that abstraction is part of how advancement is made in our practice, as well as in other disciplines. I have taken this saying to be an observation that there is almost always possible failure beneath the façade provided by the abstraction. Therefore, yes, you avoid having to let that complexity enter your brain, but only when the abstraction is holding. Beyond that point, often after pages are sent, you will still have to engage with the underlying complexity. A proactive measure following from this idea would be to provide support in or alongside your abstractions for situations where one must look under the bonnet.

You can do better now:

    #!/usr/bin/env java --source 25
    void main() {
        IO.println("Hello, World!");
    }

https://openjdk.org/jeps/330 https://openjdk.org/jeps/458 https://openjdk.org/jeps/512

I often combine these approaches with https://get-coursier.io/ when I need to fetch third-party dependencies.

What you are describing is basically remote buildkitd. That allows all of your docker builds to share a big cache. The cache-to/cache-from approach is of limited usefulness.

This is based on this write-up:

https://www.linkedin.com/pulse/wont-main-break-all-time-your...

archive copies:

https://archive.is/wI4b0

https://web.archive.org/web/20251211132753/https://www.linke...

https://ghostarchive.org/archive/bN17w

Triggering off of changed file paths is not a great way to achieve this because it's disconnected from the underlying dependency graph.

This is also a standard feature of GitLab CI.

What if I want to do something on my land that will poison the ground water for the area? What if I want to raise an invasive species on my land that will likely escape and devastate local wildlife? Should society be permissive and wait for the damage to be done before stopping me, instead of being proactive and stopping me from doing so before the fact?

Last time I checked that wasn't what he was planning on doing.

That is literally what he is doing. None of your lawn grass is native.

Last time i checked you were giving out blank checks. We live in a society

The problem is always how well one can prove that any harm was done, or that theoretical harm would be done.

This headline is misleading.

>This applies to work-managed devices and doesn’t affect personal devices.

"All Your Text Messages" implies _all_ messages, which is not the case.

But many jobs require you to bring your personal device, rather than giving you a separate work phone. And when you want to connect it to your work email or calendar, since that’s what’s expected these days, you are forced to opt into their IT team’s management of your personal device. I think that makes you fall under the privacy gap the article is describing.

Android is a multi-user OS. One of the ways this is exposed is via work profiles, which are walled off from the main profile. The IT management applies only to the work profile.

On android it splits into two seperate profiles. Personal and work and they do not share the same app data, photo,files, contacts etc.

I'm pretty sure this only works on Pixel phones if your employer enables the "Work Profile" from their MDM service. My previous employer didn't care to, and all my shit was mixed together.

Well, I am quite sure in many European countries I can refuse that practice as per work legislation.

Now if people aren't keen into fighting for their rights, that is another matter.

That practice sounds like it ought to be illegal. I'm glad I have never encountered it.

It is illegal, the only problem is that standing behind you is a rube who will absolutely let his employer use a private phone instead of demanding a company one

Maven does not support "scripts" as NPM does, such as the pre-install script used for this exploit. With scripts enabled, the mere act of downloading a dependency requires a high degree of trust in it.

Downloading a dependency also requires a high degree of trust in whatever transitive dependencies that a trusted dependency decides to pull in.