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

The supported version of DisplayPort in that TV is on par (-ish) with HDMI 2.0; and not enough for HDR 4k120; which is one of the selling points of HDMI2.1.

The complete list of TVs from major brands that do this is very easy to compile; here it is in its entirety:

My understanding is that the HDMI 2.1 port situation on TVs is, weirdly enough, a SoC limitation from a single vendor.

Almost everyone (apart from... Samsung and LG, IIRC) is using MediaTek SoC for the brains for the TVs, and they just seem to be unable to make one that has enough bandwidth for 4xHDMI 2.1.

AFAIK LG and Samsung still handle theirs in-house (and that's why LG was the very first "big" vendor to ship 2.1 at all, and they rolled it out to all four ports even on their midrange TV's in _2019_!); and it's common to see those brands have more 2.1 ports.

This should be getting better in 2025/2026 model years, since it seems MediaTek has finally managed to ship a SoC that does it; but it's ridiculous how long it's taken.


I don’t make the purchasing decision for my employer, but I certainly have to deal with their fallout, so I’ll keep complaining if that’s okay with you.

If you are not part of the solution, then you are part of the problem.

If you’re so lucky that your employer lets you use any $TOOL you want, great, but I _have_ to use GitHub actions.

So I’m part of the problem? Me specifically?


What is it that you actually want me to do here?

Just refuse to do my job because I think the tools suck?


The I/O blocks are similar, but very much not the same between the different Axy/Mz chips.

They're different even between A19 Pro in an iPhone Air and the one in 17 Pros! The Air one doesn't support 10Gbps USB-C.


Well sure, they're iterating between models. But in many cases they're quite literally copy/pasting designs. Any imagined separation between the hardware teams is fantasy based. The comment I replied to is nonsensical.

"They're different even between A19 Pro in an iPhone Air and the one in 17 Pros"

The SoC and I/O blocks are quite literally identical. An A19 Pro is an A19 Pro, aside from binning for core disables. The difference is in the wiring and physical connector on the device which puts a ceiling on the features supported, one of which is 10Gbps. The Air famously includes some new "3D printed" super thin Titanium USB-C port, using the 4 pins rather than the "pro" 9 pin 10Gbps capable connector. The SoC is identical, they just only wired it up for USB 2.0.


I've had multiple USB-C chargers broken like this.

Now, admittedly, "being yanked by a robot vacuum and falling on the ground" is outside the design parameters for a port; but I absolutely had USB-C ports fail in a way that Lightning would have not.

(Not the person you're replying to, but also a "Lightning was a better physical connector than USB-C" weirdo.)


This argument could be put in a museum as a perfect illustration of the "Perfect is the enemy of good" maxim.

Would just relying on the information from your employers cover all possible edge-cases? No.

Would it dramatically simplify the process for (tens?) millions of people? Absolutely.


The info that the IRS has from your employer is maybe 5 boxes on your return. Literally takes a few minutes to take the info from your w-2 and put it on a 1040.


If it's so easy, why is the IRS unable to do that? Why must I retype all of the information that they already have? If there's anything they don't have, I have zero issue tying that in myself.


The number and type of people living in your household is not an edge case. It applies to almost everyone, has huge tax impacts, and the IRS doesn’t know.


The argument is that you don't need a third party like Intuit to get this information. The IRS could get it themselves - they choose not to.


They can’t. Because IRS IT has been starved, beaten and abused for 20 years. If they had the resources and leadership, all of this could be possible via MOUs and better data access/normalization from the mainframes.


I agree, but IMO this is a choice. Not a fact of life.


It looks and feels much better to many (but not all) people.

I don't really know how you expect that to translate into a ROI point.


I imagine your mouse still moves plenty though.


If "the mouse looks nice" is the selling point, I'm not sold.


You've been lucky in that the countries you've travelled to all stamped your passport.

This gets much murkier in the EU, or being a non-citizen with Global Entry traveling to the US, etc.

To get a driving license in Japan without having to retake the exam, I had to prove that I lived in the country that issued my license for at least 90 days after I got it (presumably because they had some issues with people getting licenses in jurisdictions that are... easier to get the licenses in.).

This was a _very_ non-trivial thing to do for a document I first got over ten years ago, in a country that is part of the Schengen zone.


No that's what I meant - I just didn't report the countries that didn't stamp my passport. To report dates of entry and exit of every country I've visited would be impossible, I don't think I have that information at all. Quite likely in many cases nobody does.

But yeah I think the place where I got lucky is that nobody ever checked.


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

Search: