this kinda ties into a more general blind spot for nerds on the internet. there's no obligation for people to include you in their personal lives (or vice versa) just because you vaguely know them. if someone chooses to do so and you want it to continue, you gotta reciprocate somehow.

java might not see the same brisk pace in library development as other languages, but it's also 30 years old. aside from core issues with the language that can't be papered over by 3P libs, what's missing?

  Map myExtremelySpecificAndVeryLongTypeNameMap = myExtremelySpecificAndVeryLongTypeNameMapProvider.provide();

* no type level concept of a const object (ie, you can have a const reference to a List, but never a reference to a const list). this makes const-ness an implementation detail of the class itself! so frustrating that List:add() can throw depending on the underlying class.

* lack of tuples (and no, record doesn't count). this is just a syntactic sugar thing, but I really miss it from c++ and python.

* var is far less powerful than c++ auto.

in most cases, I actually prefer the syntax of c++, which is really saying something.

2. chickens are the ultimate garbage disposal. you can feed them any excess food from your household and they turn it into fresh eggs.

3. see 1. the volume of eggs gets out of control fast, but not quite on the scale that it’s viable for random people to build an FDA compliant business out of it. it’s hard to get rid of all of them, even for free.

investing more into cities like buffalo would also be great, but I don’t think they could realistically become a first choice for people who enjoy the benefits of a large metro area.

https://www.youtube.com/watch?v=ghT7G_9xyDU

we do see power requirements on the high end parts every generation, but that may be to maintain the desired SKU price points. there's clearly some major perf/watt improvements if you zoom out. idk how much is arch vs node, but they have plenty of room to dissipate more power over bigger dies if needed for the high end.

when the vast majority of daily trips are into and out of that dense core, that defines the most economic routes for building transit. beltways/bypasses exist to relieve the already saturated surface roads of the core. you don't see the same thing with trains because it's not necessary. it sucks for the passenger to transfer between three or four different trains to get from EWR to flatbush, but the rail infrastructure has plenty of capacity to accommodate a few extra pax on that route.

I think it would be a lot nicer to have urban life/transit built around many smaller cores with everyone living much closer to work. but in aggregate, businesses want the largest hiring base, and people want the best jobs they can get in the area.

trains would be even better, but people don't like to see the price tag.

almost not worth discussing honestly. this has become yet another factionalized holy war over the last decade.

the tinfoil hat probably isn't warranted in this case, but as a general principle, I try to let my friends make their own decisions around privacy.

"provided they control most of the dependencies" is a pretty important caveat by the way. many times I've seen people get the rug pulled out from under them by partner teams at the last second. it doesn't matter how clever you are or how hard you work. if you depend on something owned by a team far away in the org chart, they can always blow up your project with little consequence.