HN user

CydeWeys

28,659 karma
Posts5
Comments7,288
View on HN
Ti-84 Evo 3 months ago

One other factor that others haven't yet covered is that the different lines had different capabilities, e.g. the T-89 had Computer Algebra System symbolic manipulation meaning it could pretty much solve many types of math problems on its own, so it wasn't generally allowed in school. And then the Ti-85/86 was a step down, but had matrix support that the lower models lacked, so it was necessary for some specific types of classes.

My favorite was always the TI-85/86 line. I loved those F1-F5 buttons right beneath the screen, which made the interface overall better to navigate. The first programming I ever did was on one of those (either the 85 or 82, can't exactly remember at this point which I owned first). And, the only thing of note I ever had stolen from me was a TI-82, taken out of my unattended backpack by another student during gym class :( (And I had even carved my name into the back of it with a knife, so it would've been identifiable.)

I'm not really sure what the point of this article is. Yes, obviously, you need to implement systems that are secure and performant so that you don't get a backed-up line of people waiting an hour just to get into the office in the morning. But that's a notably flawed rollout; millions of employees go into badge-in-required offices every day without issue. And it's kind of hard to imagine running a large office while lacking such basic physical security as "keep unauthorized people out of the building". Having electronic badges and readers is table stakes.

especially when it comes to dynamic range

You can solve this by having multiple cameras for each vantage point, with different sensors and lenses that are optimized for different light levels. Tesla isn't doing this mind you, but with the use of multiple cameras, it should be easy enough to exceed the dynamic range of the human eye so long as you are auto-selecting whichever camera is getting you the correct exposure at any given point.

Beg for forgiveness, don't ask permission. I got Shingrix when I was under the age of 40, and at no cost to myself even, simply by scheduling a Shingrix vaccine at CVS. It wasn't until I went back for the booster shot months later that the nurse was like "Wait, aren't you too young for this?", but they nevertheless gave me the second dose to complete the vaccine course. You can just so things.

I'm amazed that the article doesn't discuss the end of ZIRP. The bursting of the art market bubble in mid 2022 coincides exactly with when interest rates started rising following the 'transitory' inflation caused by pandemic relief measures. This was also the same time that we started seeing hiring freezes in tech, the bursting of the luxury watch bubble, etc. It's all tied together, and has the same root cause: It stopped being cheap to borrow money, and it started being lucrative to lend it out for guaranteed returns (e.g. by buying Treasuries) rather than speculating on artworks, or NFTs, or whatever.

Sadly there's a bunch of interesting communities on there that aren't really available anywhere else, plus some of the competing platforms are even worse just in different ways (though their ads are for sure better).

Hey man, just wanted to let you know, I had to downvote a bunch of your comments in this thread, not because I disagree with you, but because your commenting style is unnecessarily hostile and abusive. You can politely disagree with someone without calling their take "stupid and clueless", or any of the other mean-spirited things you've said elsewhere in the thread.

I curate a relatively tame Twitter feed, but X has been showing me animated advertisements of some fleshlight-like device going to town on a dildo. W. T. A. F.

It's started making me worried that I can't even use the app in a place where anyone else is, lest someone shoulder surf that and wonder WTF I'm looking at.

Ironically, most of his stories were blowing smoke. He wasn't actually nearly as successful at any of that as he was at making up stories and convincing everyone how successful he had been at it. When dealing with a con artist, rule number one is believe nothing they say, certainly not about what they've done!

I'm wondering why the hood is so big, given that it doesn't need to contain an engine? Is that where the batteries are located? Or is it just mostly empty space in the form of a frunk serving as a crumple zone to meet crash testing standards? I hope it's not just a strictly aesthetic thing, because you could reduce that distance and end up with an even more practical truck.

These are luxury products. That's not the point. They use precious metals when steel would work just as well, and the really high end ones take hundreds of hours of hand labor to very finely decorated the dials and movements. Why? Because it's luxury. It's art.

And let's not even get into how much money they spend on marketing and sponsorships ..

These fine-grained attempts at parsing the words to mean things other than how they are commonly used doesn't serve any purpose. Yes, of course the act of physically typing in characters in a programming language is not exactly the same thing about thinking about the algorithms you want the computer to do, but so what? It's trivial and it doesn't matter, and specifically using language to highlight that difference is pointless. To use an analogy, people will often say that "so and so website says X", but the website didn't actually say anything; it can't talk. What they mean is they read so and so text on a website. But we all know what they mean, and it's annoying and pointless to jump in to correct the language there. Similarly, it's annoying and pointless to pedantically argue that "well actually that's not programming, that's coding".

All users of the service. Because RDAP has a fully specified format, your client can interpret it in predictable ways and then actually present the information to the user in a consistent format (or be used programmatically). WHOIS is just a blob of text that every service implements somewhat differently, so WHOISing domains across different registrars/registries does not provide a consistent UI, and it's often confusing.

It's the same data. What's different is essentially the transport layer for the information.

Two protocols that have the same data would be quite redundant.

When one is plaintext, underspecified, and decades old, they're not. I don't think you realize how primitive WHOIS is; this is the entirety of its RFC: https://datatracker.ietf.org/doc/html/rfc3912 Note how it doesn't go any farther than "it's a plain text blob retrieved over TCP". Now contrast with the RDAP RFCs, which fully specify every aspect of how an RDAP service works:

https://datatracker.ietf.org/doc/html/rfc7480 https://datatracker.ietf.org/doc/html/rfc7481 https://datatracker.ietf.org/doc/html/rfc7482 https://datatracker.ietf.org/doc/html/rfc7483

Integrating with WHOIS is a nightmare, as every registrar/registry does it differently since there's no common specification other than "connect over TCP". RDAP is fully specified, so you can simply use a language-specific library and then inspect a strongly typed response object returned by said library to get specific information out of the response. It's a night-and-day difference, and there's obviously a reason for the new spec to exist even though it conveys the same data. It's absolutely not redundant.

It has already stopped working for domains on TLDs that have sunset WHOIS and over the next few months it'll stop working for a lot more TLDs and registrars. The command line tool is nothing more than a thin client that queries a server WHOIS endpoint.