Hacker News .hnnew | past | comments | ask | show | jobs | submit | john01dav's commentslogin

> I like it when different producers select a different subset of priorities for their offer. Competition at work. One of the reasons we witnessed such an awesome evolution in the smartphone market. > > I hate it when a bureaucrat dictates a set of demands with absolutely zero regard to the cost or the tradeoffs involved in product decisions and market competition.

I generally agree with that sentiment, except we don't have a vibrant market of many options with many different trade offs. Finding headphone jack, solid reparability, user swappable battery, easily replaceable USB port, and all the other things that one might want is basically impossible. The vast majority of phones are highly unrepairable, have no headphone jack, have everything soldered to a tiny number of internal boards, and are full of anti repair dark patterns.


Such phones with removable batteries are incredibly rare, such that finding one is quite likely to fail if you have any other concerns at all.

If a truly well made phone was common and made by many people, then there'd be much less argument for this regulation.


Phones with removable batteries are rare because only a small fraction of people want phones with removable batteries. Phone manufacturers also dislike removable batteries because customers buy cheap 3rd party batteries and complain when these batteries perform poorly or malfunction, sometimes by exploding. And then the headline is, “Phone made by company X explodes.” not, “Cheap battery explodes.” Removable batteries also introduce new failure modes like contacts degrading, causing phones to power off unexpectedly when jostled or flexed in certain ways. That increases the risk of a recall and bad PR.

I and millions of others want a phone that is smaller than the current offerings. Heck, my 13 mini is too big for my tastes. But I don’t think that means the government should force phone manufacturers to make smaller phones. So too for features like removable batteries, physical keyboards, or headphone jacks.


What do you mean by "rare"? You just click "order". It's not like you have to go on the quest for the lost arc or anything like that. They are uncommon in the sense that people don't actually get them, but that's not because of a lack of availability. People do not want them.

They mean the models are rare, not the devices. The claim is if you want feature X + removable battery, it's unlikely that you will find it. People's willingness to forgo the battery for feature X therefore doesn't tell you if people care about removable batteries in an absolute sense, just that they care relatively less than they do about feature X.

You could argue that the market already reflects people's desires via, eg., Apple's market research. They could argue that democracy in the EU also reflects people's desires.


They're rare because outside of the tiny minority of people who complain loudly on HN, nobody cares about this feature.

> I have no doubt - if it hasn’t already happened - that some apps will unironically embrace the most ridiculous option by shipping as electron apps that implement a TUI layer as their front-end.

Claude code is almost there

https://levelup.gitconnected.com/theres-a-react-app-running-...


Whoever ends up using these devices second hand will be in for a rude awakening, which is bad for that person (even if it means that it just ends up going to ewaste and they get nothing) and bad for the environment. It's also bad for anyone who orders one new and isn't aware of the changes, although I agree that that is less bad than with phones due to the fact that a pi largely mitigates it.


This attitude is widespread enough to hold the world back by forcing everyone who interacts with the public Internet to support ipv4 (some technology), "for free". So, either way, we're forcing one of them. So, we might as well lean towards supporting the one that isn't hard capped at 4 billion addresses in a world with at least 2x as many devices. Have you ever tried to deal with NAT punchthrough? That's way more difficult to fix than having to properly configure your server.


> Have you ever tried to deal with NAT punchthrough? That's way more difficult to fix than having to properly configure your server.

Yes I did, and I no longer support that either. For my setups it is local private ipv4 networks all the way now! How tailscale or other VPN deals with that is not my problem!

If two nodes are on different networks, they should not be allowed to talk to each other anyway. Seems like security risk! Clean design, simple rules!


You are so very incredibly wrong about absolutely everything here.


> If two nodes are on different networks, they should not be allowed to talk to each other anyway.

We are so lucky people like you aren't in charge, or we wouldn't have the internet in the first place.


I suspect that if that ruling was made, then many other drugs being made at home for personal use might become legalized, at least unless states decide to go and ban it too. Note that I am not taking a position here on if that's desirable.


That's arguing around the point.

If the law is broken, fix the law. Don't pervert logic to pretend that the existing law dictates what you want is correct.

If Roe v Wade is based on faulty logic, cool - overturn it. But it then becomes Congress's responsibility to replace it with the correct version.

The federal government isn't supposed to police people's personal behavior. "Federal" comes from "federation" as in, the group of states in the union. It's the job of the legislature to write the laws, the job of the judiciary to interpret the laws, and the job of the states to do these things for areas that don't rise to the level enumerated in the Constitution.

When you get it twisted, you end up with this tug-of-war where corrupt politicians try to put biased judges on the bench to mold the rules to their whims without actually having to pass them.


> If the law is broken, fix the law

If you follow that argument to its conclusion, you end up at: fixing the law requires amending the Constitution, and if the law for amending the constitution is broken, the remedy is revolution. Most participants prefer the current practice instead.


Maybe we could get enough support behind an amendment to amend the amendment process.


If anyone considers that outcome to be strange - that's how most things are supposed to be regulated. It's doubly specified in the wording of the constitution and 10A.

If one takes the opinion interstate commerce means buying, selling and transporting.

It's also how the current system works. Most drug convictions are based on state law. Federal drug prosecutions are 2% of the total. Every state has its version of controlled substances act.

Nothing much would change at all.


I just put this into YouTube search and got results that contraindicate your claim¹:

> "sanic" the hedgehog

The quotes seem to shut down autocorrect

1: there's nothing that I see about the T-shirt, but the first result is titled "Sanic DA hedgeh0g". I will not be looking at what this video is. Several other results also include the word "sanic" in relation to the hedgehog.


Did you mean to respond to one of the sibling comments that are talking about autocorrect? I don’t understand what would be contradictory between what I said and what you said.


Just stick XFCE on a modern minimal-ish (meaning not Ubuntu, mainly) distribution and you'll have this with modern compatibility. Debian and Fedora are both good options. If you want something more minimal as your XFCE basd, there are other options too.


XFCE is saddled with its GTK requirement, and GTK gets worse with every version. Even though XFCE is still on GTK3, that's a big downgrade from GTK2 because it forces you to run Wayland if you don't want your GUI frame rate arbitrary capped at 60 fps.

For people wanting the old-fashioned fast and simple GUI experience, I recommend LXQt.


What use is there in display frame rates above 60 fps?


It makes it easier to treat the computer as part of your own body, allowing operation without conscious thought, as you would a pencil or similar hand tool.


> What use is there in display frame rates above 60 fps?

On a CRT monitor the difference between running at 60 Hz and even a just slightly better 72 Hz was night and day. Unbearable flickening vs a much better experience. I remember having some little utility for Windows that'd allow the display rate to be 75 (not 72 but 75). Under Linux I was writing modelines myself (these were the days!) to have the refresh rate and screen size (in pixels) I liked: I was running "weird" resolutions like 832x604 @ 75 Hz instead of 800x600 @ 60 Hz, just to gain a little bit more screen real estate and better refresh rate.

Now since monitors started using flat panels: I sure as heck have no idea if 60 fps vs 120 fps or whatever change anything for a "desktop" usage. I don't think the problem of the image fading too quickly at 60 Hz that CRT had is still present. But I'm not sure about it.


120 FPS vs 60 FPS is definitely noticeable for desktop use. Scrolling and dragging are night and day, but even simple mouse cursor movement is noticeably smoother.


Outside of gaming, not much. However, now that I'm used to a 144Hz main monitor, there is no world where I would get back. You just feel the difference.

So basically, no use when you've not tasted 120+Hz displays. And don't because once you do, you won't go back.


I have a 165hz display that I use at 60hz. Running it at max speed while all I'm doing is writing code or browsing the web feels like a waste of electricity, and might even be bad for the display's longevity.

But for gaming, it really is hard to go back to 60.


Mine supports variable refresh rate, which means for most desktops tasks (I.e when nothing is moving), it runs at 48Hz.

Incredibly, Linux has better support than windows for it on the desktop: DWM runs full blast, while sway supports VRR on the desktop. Windows will only enable it for games (and games that support it). Disclaimer: Wayland compositor required.

It’s not enabled by default on e.g. sway because on some GPU and monitor combos, it can make the display flicker. But if you can, give it a try!


Windows 11 idles at around 60 Hz in 120 Hz modes on my VRR ("G-SYNC Compatible") display when the "Dynamic refresh rate" option is enabled, and supports VRR for applications other than games (e.g., fullscreen 24 FPS video playback runs at 48 Hz* via VRR rather than mode switching, even with "Dynamic refresh rate" disabled).

* The minimum variable refresh rate my display (LG C4) supports is 40 Hz.


Ah, then Windows 11 has at least one improvement compared to Windows 10 as far as user experience goes. Good to know, as I never made the jump


I use KDE + Nvidia, and last I looked into it, it only worked if you had one monitor enabled. That's fine for gaming, not for working.

But it has been a while since I've tried it, maybe I should look into it again


AFAIK it’s very compositor-dependent. Works fine with disparate monitors on Sway + NVIDIA (1x144 VRR, 2x60 no VRR + 1x120 VRR when the TV is on).

The state of Wayland compositors move fast, so support may be here. Last thing I’m waiting for is sway 1.12 that will bring HDR.


I, for one, lose track of the mouse way less often at 165Hz.


I lose track of the mouse less often at 1024x768!


You need a bigger cursor.


MXLinux is really great for something like xfce and I really loved the snapshotting feature of it too. Highly recommended.


I have seen things approved by those sort of organizations that were extremely dangerous, such as a listed fire alarm that when installed has a significant chance of becoming silently deactivated.

With that said, it can be even worse when it isn't listed.


The newer Android version could simply give empty data (for example, location is 0,0 latitude longitude, there are no visible WiFi networks), when the permission is missing and an app on the old SDK version requests it.

Of course, they don't like this because then apps can't easily refuse to work if not allowed to spy.


That can have some very extreme legal ramifications.

Consider - it's a voip dialing client which has a requirement to provide location for E911 support.

If the OS vendor starts providing invalid data, it's the OS vendor which ends up being liable for the person's death.

e.g. https://www.cnet.com/home/internet/texas-sues-vonage-over-91...

which is from 2005, but gives you an idea of the liability involved.


Phone companies are required to make sure 911 works on their phones. Random people on the internet aren't required to make sure 911 works on random apps, even if they look like phones.


The comment you're replying to literally has an example of an internet calling service being fined $20,000 for not properly directing 911 calls.

I guess Vonage should try to appeal the case and say pocksuppet said they're not required to do that.


Vonage sells phone services that happen to use the internet. This is not the same as being WhatsApp.


It can't have "extreme ramifications", Google's own phone couldn't call 911 for a while.

And you can manually force only the voip dialing apps instead of everyone


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

Search: