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

Yeah the Android is capable of 120 but often lower than 60 in practice


If you use a 120 Hz iPhone for 6 months and then switch back to your 12 mini, you'll notice immediately.


What you definitely notice between 60Hz vs 120Hz on a phone is the battery drain.

Depends a lot on the usage I guess. In a tablet where you may draw etc you can notice the difference definitely. Or if you play games on the phone. But otherwise I don't think the difference is that important as it is sometimes claimed.


Yeah, first thing I'd do is check if it can be disabled


Not for me. I tried out the high refresh rate thing, switched back to 60.. can't tell any difference at all. Same for high DPI vs "regular" DPI screens.

Screen flicker on CRTs with low refresh rates was terrible for me, but with modern flat panels.. nope, can't really tell the difference.


I used to switch between a MacBook Pro with a 120Hz display and a MacBook Air with a 60Hz display and never noticed any difference. I think I could probably have noticed if I'd put them side by side and compared the feel of the scrolling, but why would I do that?

There's a minority of people who really do notice stuff like this, which is fine. The problem is that for some reason, they sometimes have difficulty accepting that they're a minority.


I think this varies a lot from person to person. I find the effect to be incredibly subtle - one of my monitors reset it self to 60hz a while back, and I didn't catch the problem for days.


Scrolling text, I notice IMMEDIATELY


Sure, and maybe I'm odd, but I don't read text while scrolling. I stop scrolling and then read. So yes, if I just scroll up and down quickly I can see the refresh is different, but otherwise I don't notice it in my regular usage.


Plus we all grew up reading the 24fps text scroll in the Star Wars intro just fine. Until we convince a new generation of cinematographers to shoot in 120fps, it all seems a bit moot - even most digitally-authored content doesn't exceed 60fps (and tech people are the first to complain about things like the soap opera effect...)


The way frame rate work on conventional film vs. an LCD are completely different. It’s like trying to ask the bitrate of a Vinyl record.

Conventional film projectors don’t show each frame continuously, they transition the shutter blade smoothly between frames, and projectors often flash each one a couple of times (48 or 72hz). A cinema projector is going to demolish a LCD in smoothness and motion quality even if it technically has a higher refresh rate on paper.


Right, but we're mostly all watching 24 fps movies on LCDs. I don't have a cinema projector in my living room.


So when remastering from film, do they put each frame into the digital video and keep it 24 fps, or do they play the film and digitally record it at 60 fps to capture the projector effect?

Either way, DVDs were digital 29.97 fps at most.


There is a big difference between watxhing a movie and operating a device where your input makes things move on the screen, you notice the depay way more.


I find that watching something like a fast-pan in 24fps footage on a modern LCD is horrific. CRTs used to inherently smooth this sort of thing out, but now we get these harsh frame transitions. As much as the soap-opera-effect is maligned, a high refresh rate LCD needs some form of motion prediction for low frame rate content.


Yeah, which is why those TVs doing frame interpolation or whatever are beneficial for most people as long as they do it well. Even though AV pros might get annoyed at the fakeness.


Can you not literally see the frames skip as you move the mouse cursor across the screen? To me it’s OBVIOUS and excruciating and I’m only a light/casual gamer and use all my computers for work.


If I move my cursor slowly I can see the difference, I guess? But I don't habitually do that - I run with mouse/trackpad dialled to maximum acceleration, even at 120Hz there's a skip when you flick the cursor halfway across the screen. And I'm rarely scrolling a line at a time, I'm going page at a time.

I don't really get the obsession with smooth movement for desktop use (as opposed to gaming). Possibly this is a generational thing? Why is anyone intentionally using a computer primarily via slow analogue inputs?


If something is not noticeable when it gets "better", but it leads people to notice other stuff is "worse" over time, then I'd argue it's not actually a good thing to get.

Imagine if someone said "this food won't really taste better to you when you first eat it, but after 6 months you'll find other food tastes worse". To me, this would not be a selling point.


I didn't know how bad TV looked in the 90s. We watched a low res 19 inch TV from across the room. Did moving to HD make any real difference in our lives? Do we really enjoy TV that much more? Once the excitement wears off about 20 minutes into watching it, its still the same thing. If the story is good, you get into it either way and forget what you're watching it on.


Watching older TV shows I notice a lot more close ups of actors faces. I’m convinced it’s because the shows were produced with small screens in mind.


Sounds very similar to old glass panes being thinner at the top and thicker at the bottom. Did the glass flow over the years, or did we lose what was common knowledge at the time, for installers to orient each pane a certain way?


That one’s down to gravity, glass flows down very slowly over long periods.


Are you sure?

"It's sometimes said that glass in very old churches is thicker at the bottom than at the top because glass is a liquid, and so over several centuries it has flowed towards the bottom. This is not true. In mediaeval times, panes of glass were often made by the "Crown glass" process. A lump of molten glass was rolled, blown, expanded, flattened and finally spun into a disc before being cut into panes. The sheets were thicker towards the edge of the disc and were usually installed with the heavier side at the bottom. Other techniques of forming glass panes have been used, but it is only the relatively recent float glass processes that have produced good-quality flat sheets of glass." https://math.ucr.edu/home/baez/physics/General/Glass/glass.h...


Depends on the content. When people are talking in a nondescript (thing the "12 Angry Men" movie), SD is quite fine. Now compare it to Blade Runner or Scarface. Those movies absolutely benefit from more detail and colors.


I watched TV and used computers in the 90s and the whole time I was desperate for display technology to improve. Mainly CRT refresh rates, which often gave me a headache, but yeah I noticed the crappy pixel density all the time too. The nice Apple display I have now is one of my fave things I’ve ever bought and could only be improved by being >60Hz (which I do notice, but it’s not a big deal).


CRT refresh rates is super high, usually starting at 120hz... and now we are trying to do the same? you want to feel headache again?


> CRT refresh rates is super high, usually starting at 120hz...

That’s not my memory of it at all. They were often set to 60Hz by default, and increasing the setting to 75Hz would make it noticeably less flickery.

> and now we are trying to do the same? you want to feel headache again?

The headaches were from when it was too low.


That’s what I’m talking about. 80Hz was just enough to keep the headaches away for me and that was either impossible or came with other compromises for some monitors / video cards.


HD matters a lot for sports. Big screens and nice sound help with movies, which DVD quality is usually good enough for, but certain movies deserve to be a theater or IMAX. It doesn't matter for most other things. I still watch stuff in 360p or 240p.


Big of you to assume I only watch "if the story is good".

The kids make me watch Transformers - completely devoid of suspense or consistency. That 4k 120Hz OLED is the only thing getting me through that gauntlet.


Yes, I definitely remember noticing how much better TV was when we moved from 20" sets from last century to HD LCDs (and then much larger/higher-res LCDs) over the last 25 years.

And I would disagree that only the story matters. If that were the case, people wouldn't go to the theater (a trend that has started happening in the last 15 years as people have been able to rig their living rooms to give an experience that is nearly theater quality, especially when considering cost and convenience. When we had 20" TVs, they were no substitute for going to the movies.


People had giant TV’s in the past as well. They are cheaper now.

Either way, a larger screen is not the same improvement as higher resolution. And more importantly, the reason people may not go to the movies when they have a home theater system is partly due to justifying the cost of the theater system.


It's the same dynamic as with how we optimize for web pages speed. People don't immediately think that website responding 200ms faster is better. But they enjoy the experience more anyway (even if at some subconscious level) and they end up liking it more and spending more time with it.

With food also you could be incrementally getting better and better food and when you then try v1 it would taste bad.

It seems that we might also be noticing slight degradation more than slight improvement in general? No idea if that's true.


I don't think that's a good comparison.

I've often had new phones that are 'faster' but I barely notice the fastness until I go back to my old phone and realise that my finger-memory needs adapting because things take just a bit longer to load.

I'd assume it's similar for screen refresh rates.


That's not been my experience with the refresh rates, and it's not what GP and GGP said either. I have a 13 mini and have bought both 16 and Air. I kept them for 2 weeks and then returned.

When I got the phones, I did not notice any benefit related to screen refresh. I also did not notice any detriment when I went back to my 13 mini after two weeks on a 120 Hz screen.

But if it was as GP said, and it's only something you notice when you go back to a "lesser" screen, then that would not be a selling point in my book.


I always wondered why Windows users didn't notice the jagged text in 2001 and see a Mac as obviously better. You don't know what you aren't missing until it's gone.


This was exactly my experience when I stopped eating fast food regularly.


The true test here, which I don’t see much discussion around, isn’t how fast or how well agents can convert the existing apps to native; it’s how fast and how well the team can build entirely new features across platforms with native vs react. The existing app code is an unambiguous spec — perfect for agents to build from. Typical design specs, PRDs, and prompts have a lot more ambiguity. There’s a lot of iteration that needs to happen to get a feature from concept to launch and I’d wager that will not be as fast with the fully native approach.


The compile and build times on iOS (and Android) are also painfully slow. They claim to have "hot reloading" but only under very specific conditions, and it's not the whole app. When you're working with UI in particular, you can often edit and text your changes 10x faster on React than native. You could argue that the quality "gains" you get from native are partially negated by the reduction in iteration speed. Quality often comes from iteration and it's an order of magnitude faster with React.


Agreed, I’ve never used react native myself but I do use CapacitorJS to run JS (TS) apps and with a dev server I can hit save in my IDE and see it on my phone screen in <1 second on average. It’s so nice for iteration.

Throughout my career, I found that the faster I can go from wanting to try something to seeing it working, the better. Without that quick iteration cycle, I end up, not trying certain things or trying to batch all of my changes which then makes it harder to be sure what actually fixed it.


Exactly. I wouldn’t be surprised if Shopify ended up building some tooling to try to solve this, but Apple in particular is remarkably disinterested in or perhaps inept at improving the developer experience, and agents won’t magically fix that.


Because time is relative —— year for a 50 y/o is 1/50th of their life; a year for a 5 y/o is 1/5th of their life.


To be fair, Spotify was a slop factory long before LLMs started doing it


The bigger problem is that it doesn't help you learn the correct finger positions


It's not because of twitter character limits, it's because browsers collapse multiple consecutive spaces in html when they render text.


the subscriptions all have limits. when you hit the limit you again start paying per token.


occam's razor explanation: more tokens = more $.

models are incentivized by their makers to burn through as many tokens as they possibly can, so long as the customer doesn't cancel.


This is actually nonsense. More tokens means more capacity subscription and expense. Anthropic has enjoyed a high premium per million tokens because the quality per token was unusually high. Now it’s unusually low. This drives down the margin people will be willing to pay for the same number of tokens while driving up their capacity utilization. The economics are even worse for subscriptions.

Opus models have degraded rapidly since March, with each release being considerably less useful and considerably more verbose. The language is no so weirdly florid it’s difficult to understand, and its logical conclusions are almost always suspect. It goes off on clearly bizarre snipe hunts to the point it feels like I’m using a gpt 3 model at times. It’ll announce that it’s about to embark on building something then just return control to the user and wait. You can also tell perceptibly when they’re reducing model quality to load shed - it becomes stupider and stupider to the point you’re better off dumping state and switching to codex or just turning in for the day and hoping they secured more capacity tomorrow.

It’s an absolute race to the bottom with Anthropic on virtually every level. I’ve rarely seen a company so rapidly accumulate good will in the developer community as they did around 4.6 in December and January. By March, it was inconceivable to use anything else. 4.8 was a bit of a wake up call to not put all your harness eggs in one basket. 5 is straight up time to cancel territory.

I actually manually set my model back to the older versions to get anything serious done. More and more I use codex for anything non trivial.

This isn’t about avarice by the provide trying to get more tokens and more utilization. They’ve over subscribed for capacity as it is. If they can produce better quality for less tokens they can charge a higher margin and will be paid if, which is a better economic strategy overall. This is something else. I suspect it’s actually the opposite, they’re finding ways to cut capacity demand in ways that leads to worse behavior that leads to more capacity demands, worse output, worse quality, and worse margins, worse, worse, worse.

Just as I never saw a company accumulate such positive developer good will so fast, I’ve never seen one squander it so fast too.


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

Search: