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.

I think some people would enjoy something akin to HyperCard for building custom TUIs and/or highly efficient web UIs.

Would a wider road not embolden drivers to increase their speed?

The issue isn't people going too fast, it's people turning left. 26 basically connects Portland on one end and Mt Hood recreation stuff on the other, and it used to be that there wasn't that much in between. Over the last few decades, a lot of development has gone up, meaning a lot more businesses and neighborhoods along both sides of 26, plus the highway has gotten a lot busier.

Every study on this topic says yes. Drivers go faster on roads where they can go faster, regardless of the speed limit. If you set a low speed limit on a road capable of supporting fast cars, people just ignore it - they obviously set the limit wrong, right? But if you make a road where people can't drive fast, they don't and they don't even feel that bad about it.

There is something to be said for having some basic data access libraries already in place, even if they are not ideal, so that developers can bang out functionality more quickly. That is the typical selling point of ORMs, isn't it? While there are well-known downsides, you can skip the ORM when it's not a good fit, or later when you realise that it is causing a problem.

Generally, I prefer to create functions for specific queries, rather than for specific "entity" types, and the return type of each query matching the result of the query. This fits with the reality that queries often involve multiple entity types.

My favourite application-later database tool so far is https://www.jooq.org/ because it allows for code generation from the database schema, allowing for type-safe construction of queries. I find this makes it easier to create and maintain queries. It is a relatively unopinionated power tool, with minimal attempts at "automagic" behaviour. I find myself missing jOOQ now that I am not working much with Java.

It's less complicated than you might think. A Java Development Kit (JDK) is a filesystem directory, and includes everything necessary to run a Java program. Most of the mysterious installers and version managers are managing a collection of these JDK directories in some fixed location on disk. You can download a JDK directory (tarball), and use the `java` binary within it directly.

There is also a convention of using the `JAVA_HOME` environment variable to allow tools to locate the correct JDK directory. For example, in a unix shell, add `$JAVA_HOME/bin` to your `PATH`.