Hacker Newsnew | past | comments | ask | show | jobs | submit | jdsully's commentslogin

"consumers don’t shop based on the endurance metrics even if they should"

Its been well over a decade now and neither I nor anyone I know has ever had an SSD endurance issue. So it seems like the type of problem where you should just go enterprise if you have it.


But surely you see the core LLM innovation is that computers can now TALK to you.


Well, people can talk, yet stakeholder most of the time cannot explain what they want.


I sign up if I want to do a long road trip and cancel after. Worked great for that.


They hadn't bothered to add ipv6 support to most of their services and the ones that did have it usually were only dual stack - still requiring an ipv4 address.


They didn't require you to have a public IPv4 address. Just an IPv4 address.


Which requires dual-stack and all the issues that come with it, especially with private addresses.


That sounds like a failure in every direction. I see why you moved


Wickard V Filburn is simply bad law... The federal government has way too much power and MUCH more than was ever intended. Its not a feature it is indeed a bug. One caused by the Supreme Court.


>The federal government has way too much power and MUCH more than was ever intended. Its not a feature it is indeed a bug.

we got bigger and thus we got permutational orders of issues arising as a result. We had to redo the articles of confederation within 20 years of their drafting and that was with 13 states.

Bug or feature, I see it as an inevitability as we grew to 50 states and multiple territories that the federal government would need a stronger hand today than in 1787. Of course, that hand shouldn't be bypassing every section of the constitution to serve the federal government itself. These are the exact fears that caused Shay and Whiskey way back in the day coming to fruition.


Excel needed the x87 as well as they cared about maintaining the 80-bit precision in some places to get exactly the same recalc results. So they would have fixed it eventually most likely.


Ask a mechanic friend how often to do an oil change and they will 9 times out of 10 give you an answer without asking what model of car.


I can’t say I’m in the business of asking 10 or more friends to confirm this, but any number they provide without knowing the car is a guess at best, and likely erroring on side of caution. A Google search with the car model in the query virtually always returns the correct figure ranges for said car.


Ah but see the most important piece of information is not what the manufacturer specifies. Most mechanic friends would tell you manufacturers are over-extending the interval to make their cars look good to purchasers and because they only care about getting to the warranty end not total life of the car. While 3k miles old wisdom is out dated, if you do your own oil changes you can see a massive change in what comes out after 5k miles.

By over specifying the question you will miss out on the more important context.


Much of what you say is true, but again your mechanic friend can only provide a meaningful answer if they know the model of car. It’s the first question any half way competent mechanic will ask!

The cars sitting outside my home vary in oil service interval by over 10k miles, as just one simple example, and I don’t drive anything particularly exotic.

By under-specifying the question, you rob it of the context to be answered accurately.


At some point it makes sense to just let us use self signed certs. Nobody believes SSL is providing attestation anyways.


A lot corporate environments load their root cert and MITM you anyway


A lot of applications implement cert pinning for this exact reason


What does attestation mean in this context? The point of the Web PKI is to provide consistent cryptographic identity for online resources, not necessarily trustworthy ones.

(The classic problem with self-signed certs being that TOFU doesn’t scale to millions of users, particularly ones who don’t know what a certificate fingerprint is or what it means when it changes.)


Then you might as well get rid of TLS altogether.


You'd still want in transit encryption. There are other methods than centralized trust like fingerprinting to detect forgeries.


Haven’t seen any such system that scales to billions of user.


The most likely culprit was talking to other nodes via their public IP instead of their local ones. That gets billed as interent traffic (most expensive). The second culprit is your database or other nodes are in different AZs and you get a x-zone bandwidth charge.

Bandwidth inside the same zone is free.


I wrote Sum Buddy using a variety of AIs. Its a full featured AI spreadsheet. It started in Gemini's web interface and moved over to claude (which was a huge increase in capability). It has a bunch of paying customers now.

https://sumbuddy.net


lol, you brought back clippy and people pay for it?


It looks like your writing a letter. Want help?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: