Apparently array is short for associated array:-)

In PHP the array index supports different key types and there's various optimizations that need to happen when the indexes are all numeric, mixed, or all strings or anything else. Technically it's called associative as soon as even one of the indexes isn't numeric. Internally though they are always numeric and anything non integer is hashed internally with DJB2 (Daniel J. Bernstein) hash algorithm and then stored. Using a non numeric index is slightly slower for that reason.

But even if you only have numeric keys, those keys don't need to be consecutive, or start at 0.

In your example, why didn't a 6000% ROI not attract enough investors and introduce competitions, eventually lower the ROI?

Regulatory capture.

I have the feeling that Git winning the war hinges heavily on GitHub being the way to do open source projects, and that is changing given the sad state of GitHub.

Another contender is Jujutsu (jj) which allows you to use jj as frontend and use Git as the backend (with the potential to support any backend, e.g. Google's proprietary Piper), with the best ergonomic and the widest availability of hosting solutions.

I’ve recently switched to jj and it is truly amazing. It too about a week for me to “get it”. The tool is amazing but I think there’s way too much emphasis on what it does/allows rather than what benefits it brings to your workflow. If they get that marketing right I could see it growing. If not, I’ll keep using it

Would you be willing to pitch why you like jj and find it useful? How were you using git?

I use git mostly on single-dev projects, with branched development patterns.

Would someone like me with a simple git use-case find JJ enjoyable?

jj is amazing, even as a solo dev on small projects. It's difficult to explain because it depends of each usage, but it's very easy and safe (you can undo everything) to just try and see.

> I have the feeling that Git winning the war hinges heavily on GitHub being the way to do open source projects

Nah. At the time BitBucket was the better way to do open source projects, and they were Mercurial-first. But eventually they had to add Git support because there was so much demand.

Vendorizing using git submodule should be a robust mitigation for this problem.

Wouldn't locking dependencies be far more likely for dependency-users to do, and be approximately as effective for those that do?

subtree is better for this case, you want to encourage actual reading before running. reading won't catch everything but it catches a lot, and the burden isn't as high as people always complain about before they try it.

This feels like the modern analog of the king, the mice, and the cheese. What cats do I need to bring in to eat my git submodules?

`go:generate` is for the package provider, the command never runs when someone `go install` or `go get` the package.

Note that the NPM worms are spreading because the package providers are developing on their libraries without them noticing a malicious dependency. It is not users/consumers spreading the worm, it is developers spreading it.

Your mismatch is that you think in policies, not assessments here. Nothing in my normal go workflow will ask me if I want to run "curl download whatever from the internet" when I run go build.

Though I agree with the difference in workflow, there is not a single mechanism in go catching this. go.mod files can be just patched by the worm, and/or hidden behind a /v123 folder or whatever to play shenanigans on API differences.

https://github.com/wsvn53/scrcpy-mobile would allow you to control Android phone from an iOS device.

To me the most amazing thing of using Chromebook is that you can run the Tailscale _Android_ app and get your ChromeOS connected to your tailnet.

Overseerr is a write-only access to your Radarr/Sonarr library, so e.g. the user cannot accidentally delete a movie or choose to download a lower quality version.

Sounds great, but if my family wanted to access a web-ui in stead of shooting me a message in natural language I could also give them the Radarr / Sonarr UI.

Currently the profile is fixed. I guess they can delete movies but I can re-downlaod in 5 min so not a massive problem. I'm on a rolling-delete schedule anyway as my hard drives fill up quickly.

AFAKIT the built-in backup of a managed database will be gone if the database is deleted. This is true in AWS and GCP.

I still don't know why the product manager would decide this is a good UX.

IIRC in AWS you have the option to create a "final" snapshot of the DB instance when deleting it. I'm pretty sure that's the default behaviour when using the web console, but may merely be an option in the API interface.