td521534f12

It's to make stuff like autocomplete or source browsing work in your IDE

The reason execution on install is a bigger deal than execution on import/run is because a lot of developers today run their code inside of sandboxed environments (containers, VMs, etc.) which prevents the malware from easily accessing stuff like session tokens.

I watched Lain with the subtitles on and I still won't claim I understood all the lines.

I'm pretty sure many of the lines are _not understandable by intent_, even.

"Present day... present time... ahahaha!"

A big reason Python and Java are juicy targets are because for a very long time pip and npm executed code on the user's machine on package install, not just on import. (This is changing in newer versions of pip and npm IIRC)

1. I have team members who live and work in very remote places, SSH-ing from there is possible but terrible.

2. We're all in the on call rotation and being able to reproduce a bug from literally anywhere is valuable.

3. We all spend at least a few weeks a year traveling for work, and hotel/conference center/random office wifi can be terrible.

We do have cloud based builds and some dev environments we can "check out" as needed for running stuff async or certain tests that can't be run on a laptop (e.g. Nvidia GPU specific functionality, certain functionality that requires a real server network instead of a local virtual network, large scale tests)

For the ability to run our full server-side application stack locally, including all services and as much of the test suite as possible, as well as the profilers, debuggers and telemetry tools to debug issues. Way faster to develop when you can have a change running live in about 3 seconds instead of 5 minutes, run targeted tests in seconds and a full test suite in a few minutes.

No it isn't, you can get a player at Best Buy for $3k and movies are like $15 once they're out on DVD. The high priced items in the store are for movies that are still only in theaters and not on streaming yet.

The ones built into the TVs suck because they don't get updated and are usually really slow and choppy to use. Everyone I know who doesn't use an HTPC, uses an Xbox or PlayStation to watch stuff.

The main reason people want replaceable batteries is so they can keep using their phone for several more years after the first battery wears out. The problem of recharging has been solved by extra batteries that snap onto the back of the phone and give you hours of extra charge in minutes.

The Xbox console is a pretty bad deal outside of the US because a lot of the software features (streaming apps etc.) don't work outside the US. Everyone buys PlayStation instead. Nintendo is of course doing their own separate thing focused on exclusive games.

Nuclear power plants take a very long time to build, it can be 7-10 years before you even begin construction due to all the permits, politics and planning.

As for scaling massive amounts of solar/wind... that's exactly what China is doing to power their infrastructure buildouts.

The second example is leaking API keys into the OS process tree.

There's a GCP API that lists the hardware advertised in each zone as a starting point. Then you have to actually attempt to provision hardware in each zone to try to get a sense of what capacity is available there. Combine the two and you can kind of map out a topology.

GCP is kind of odd in that some hardware is only available in certain zones, and some hardware is technically available in multiple zones but the capacity is not evenly spread. I've had to implement infrastructure code for GCP that interrogated hardware availability by region and zone to place VMs, trading off multi-AZ availability where it made sense.