HN user

daze42

121 karma
Posts6
Comments52
View on HN

This 100%. We're in the middle of an AI Manhattan Project and if "we" give up or slow down, another company or country will get AGI before "us" and there's no coming back after that. If there's a chance AGI is possible, it doesn't make sense to let someone else take the lead no matter how dangerous it could be.

Things in general across the board getting more expensive is a symptom of inflation, true. But I don't see how just a subset of businesses raising prices necessarily causes long term inflation. Even if all the existing grocery stores collude to raise prices together, that would just create market pressure for other grocery stores to pop up that can undercut and obtain a large amount of market share from the colluding businesses. So sure, there may be a blip of "inflation" while the market corrects and the new businesses start up, but overall it shouldn't cause actual inflation.

When You Know 6 years ago

Is he talking about Bitcoin specifically or cryptocurrency as a whole? If just Bitcoin, yes, I agree that the transactions per second (TPS) is too low for global adoption. But as far as I know, there's no technical reason it has to be that slow for all cryptocurrencies. Ethereum 2.0 is supposed to support 100,000+ TPS according to Vitalik. https://twitter.com/VitalikButerin/status/127796159495847116...

Slack is down 6 years ago

Availability zones are unique for each account. So my zone A could be your zone C, for example.

You bring up very good points. I certainly don't trust most if any of the other critical pieces of the stack. I think those are attack vectors or points of failure as well and that risk needs to be mitigated. But on the other hand, the NPM package web is much larger and the barrier to entry is much lower so I would consider it to be much higher risk than the rest of the stack.

We as an industry need to put work into reviewing, simplifying, and increasing visibility at all levels of the stack, especially firmware. We're building high and fast and while standing on the shoulders of giants is a great place to be, we need to make sure the giant is more than just a house of cards.

It's a minor problem until it becomes a major one. All it takes is one common dependency to go rogue or a bug to be exploited without the maintainers being around to fix it and a large part of the ecosystem becomes unusable. Using a dependency implies an element of trust and now we have a huge web of trust between thousands of maintainers that we really have no way to check. The larger that number grows, the higher the chance of catastrophic failure.

This is the hardest for me. It's almost like those two forces are in opposition to each other. I'd love to find an industry where they could align.

The headline and the article are both poorly worded.

"The team found that for every gram of alcohol consumed a day, the brain aged 0.02 years — or, seven-and-a-half days. (The average can of beer or small glass of wine contains 14 grams of alcohol)"

It makes it sound like every drink you have ages your brain by a week and that's not actually what the study says. What it really says is if you have one drink a day for an entire year, it ages the brain 11 days.

I've been using httpx 0.9.3 in production now for a couple months. I switched from requests when I realized I needed async support and it has been a dream to use.

The only issue I've run into has been with my attempt to reuse the same AsyncClient to make multiple concurrent requests to the same remote host. It looks like this issue may have been fixed in 0.10 or 0.11 so I'll be upgrading soon to check.

Also, be sure to check out the other fantastic projects by Encode. https://github.com/encode I stumbled upon httpx after using Starlette and Uvicorn for one of our microservices and and been pleasantly surprised by how easy to set up and use they are.