Even if you do switch to mavenCentral, there's only so much you could do about your dependencies. Unfortunately we still depend on JCenter's snapshot too much.

You raise a very interesting point there. I do wonder, however, how having such boundaries in place would affect exchange of information somehow. That's something I can sense in practice by living in a country where a large portion of the population don't speak english, however most of the tech material is made available in english.

I feel like for that to happen a much deeper cultural transformation in how we share information and global inequalities would have to come as well. The reason there's so much content in english is not because it's been constructed solely by authors who speak english natively (albeit probably the most common native language amongst blog authors, etc), but because many authors feel like they have to write it in english in order to speak to a broader, global audience.

there is no such thing as "regular people's interest". everyone's interest is a little bit different.

Not even the base of Maslow's hierarchy of needs?

That's impressive. But I'm also curious as to what other applications this setup can be useful for, because that looks to be one hell of an expensive operation. It's awesome to see such things actually happening.

While not done with neutrinos (at least not yet), a very similar setup is used for stufying geological structures. Usually either cosmic rays or muons produced by cosmic ray collisions are detected and depending on the number of detections over time, the density of the rock they pass through can be determined. By filtering the energy of the particles, you can look at radiation directionally (particles coming straight down have more energy than those that come at a shallower angle). You can have a detector next to a volcano and get an "x-ray" of that volcano.

Neutrino detectors can also "see" active nuclear reactors. One could imagine using a detector located outside of a suspect nation to validate their claims with regards to nuclear nonproliferation (ie that they're not running their reactors overtime to produce more plutonium than they report).

It was initially used to observe proton decay. By not detecting a decaying proton in the water tank, they could place the mean lifetime of a proton above 10^30 years.

Any company has a problem, which they size the value that it has to be tackled for, so they set budget, measure options, raise possible trade-offs, eventually succeed at dealing with it or get bitten due to lack of proper future-proofing, not evaluating environment/requirements properly, rinse and repeat. Once you've got several problems that require this kind of approach, carefully handpicking the possibly-but-not-proven best solution is not only time consuming but might lead to potentially awfully impactful consequences. When the decision to switch cloud provider services to one that may get you offline for half an hour leading to a million-dollar revenue impact, that's when we're talking enterprise.

I work in a big lumbering organization. Sure, there is some truth to that. But there is also just a lot of suboptimal decision making, because big organizations have complicated politics and policies, and it is often easier to keep coasting than do something better.

I think time plays a role. Trying to learn complicated stuff fast usually leads to not learning them well enough, in my experience. If I do so, jumping to wrong conclusions or applying a method on the wrong place/in the wrong way is almost guaranteed. So just keep reading, studying, picture yourself explaining it to a classroom, talk about it to colleagues and friends, engage on discussions about it online. Eventually you'll master the craft before you know it, and the good part is that such things may be on constant evolution and there will always be something new to learn. Just avoid being that one trick pony that knows a lot about one specific topic and that's it.