Photos app in iOS 18 is simply atrocious. Try sharing an album with friends. So many UX issues that it could be a case study.

I never understood why there’s such a huge disconnect between private albums and shared ones. My biggest gripe with shared ones is that they don’t provide full quality/res pics. I was going to ask why if a full quality backup is already in the cloud, but now I realize it might be because of the security architecture? Still, this should at least be an option, even if it means storing the data twice, especially since we’re paying for that storage anyway.

for those who don't want to go to twitter: https://xcancel.com/Steve_Yegge/status/1898674257808515242

Yeah, the author needs to get off X/Twitter. At this point posting to X is like driving around in a Cybertruck with a bumper sticker reading "I Approve of the Current Situation"

After years of react, svelte is such a relief. It’s such a joy to do webdev again. Claude’s auto completions in Cursor are often not great though.

I haven't used Claude much personally, but have seen https://svelte-llm.khromov.se/ built to help on that front, do you might want to check it out.

Actually, I forgot that this landed as an official part of the docs now: https://svelte.dev/docs/llms

It might still be a bit big, but PRs welcome if folks want to try slimming it down to just the stuff that's new in Svelte 5.

They're not expected to be with anything too new though It's in the nature of the training, you need many examples to get high quality

Tailwind and Sveltekit are the reason why I still love doing FE after all these years. Initially I was so sceptical of TW. I simply can't work without it now. Huge thank you to authors for their hard work.

Congrats on making this! Looks very cool! For me it was very hard to learn about your products from your website. It is painful to scroll, it lags a lot and I had to put very much effort into getting the information I wanted. The design definitely sparked interest, but website killed it. Good luck on your journey!

Congrats on launch, incredible work!

Btw, your pricing is broken :)

Should be fixed. Thanks for the note!

Very exciting, congrats on this! I’ve been watching numerous weather forecasts over the last couple of years because of my interests in mountain sports, and I am very very curious how will this improve forecast accuracy. Good luck worh everything.

Am I the only one that hasn't noticed the search input in the footer? :O

Thanks, 10 years of HN and I was still using "site:news.ycombinator.com"

Try https://hn.algolia.com — it’s great

That's where the footer search field points.

These days I use the search feature much more than commenting or reading posts. The frontpage is the usual recent news addiction treadmill, while for research into niche topics you can find a treasure trove of interesting comments in the archives.

Want more posts about Lisp, Smalltalk and reverse engineering, for example, rather than the usual front page drivel? Search for them.

On one hand I wish Algolia didn't give very old posts a lot of weight (it often prefers to show posts > 8+ years ago), on the other hand old content tends to be before the Eternal September of tech-adjacent people coming to this forum to discuss tech-adjacent light content, so it's actually a feature. The real value of HN is its archives IMO.

I also made a bookmarklet to show me HN posts from random dates, it is quite interesting to see what was interesting to people a decade ago, for example. Lots of comments in HN's heyday were pretty eye opening as well.

    javascript:(function() {function randomDate(start, end) {var date = new Date(+start + Math.random() \* (end - start));var day = ("0" + date.getDate()).slice(-2);var month = ("0" + (date.getMonth() + 1)).slice(-2);var year = date.getFullYear();return year + '-' + month + '-' + day;}var startDate = new Date(2007, 9, 9);var endDate = new Date();var randomDateStr = randomDate(startDate, endDate);var newUrl = 'https://news.ycombinator.com/front?day=' + randomDateStr;window.location.href = newUrl;})();

Also recommended is https://news.ycombinator.com/front, which shows you the frontpage stories from any day—a little bit like archive.org would do, except that it's not a snapshot, but a composite of all the front pages from a 24 hour period.

For example, here's HN from a year ago: https://news.ycombinator.com/front?day=2023-07-02.

https://news.ycombinator.com/highlights is another good resource (and if anyone notices a great HN comment, past or present, they're welcome to nominate it for the highlights list! just email hn@ycombinator.com).

Thanks Dan, that is in fact exactly what my bookmarklet does, it generates a random date (2012-01-02) and appends it to `https://news.ycombinator.com/front?day=`. I think there should be a `random` link on the HN header links that does what I am currently doing, it would be useful to have it built-in.

Ah sorry I missed that you were already pointing to those!

A 'random' link might be a good idea. For /highlights too.

Yep it's fairly easy to make a bookmarklet for /front but for /highlights it seems to depend on the id of the comment as a cursor rather than the date, so it would be nice to have them both as links in the header bar.

That's really neat. Thanks for providing it

What about workers? Isn’t it basically the same as offloading computation heavy work to separate thread? Also, we have WebAssembly. Afaik, js threads can now share memory using SharedArrayBuffers. So I don’t think we have this single thread limitation anymore :)

Idk about this specific app, but the main problem with workers is that any data their working on needs to be copied in or side-loaded into them once they spin up. I imagine for huge video files, having each worker load up a separate copy could be a bottleneck.

> the main problem with workers is that any data their working on needs to be copied in or side-loaded into them once they spin up

Isn't this no longer an issue thanks to SharedArrayBuffer?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

I believe the ONNX Runtime uses this for multithreading on the web, see https://github.com/nagadomi/nunif/issues/34

Ooh. Interesting. I wrote my last worker-based app a couple years ago for chunking and crunching some large datasets. I'll have to give this a go one weekend.

Indeed, Pikimov is using SharedArrayBuffers to decode video frames outside of the main thread

Why use mics for that if they have direct access to rpm of fans?

I can't speak for Apple, but for my Prusa 3D-printer: Worn/cheap ball bearings will make a rattling sound until they heat up and the balls expand. If you care about the auditory experience, using audio in the feedback loop makes some sense.

The goal is probably not to absolutely manage cooling but to focus on the audio experience and try to keep noise below some threshold.

I think that's an interesting idea, even if not everyone might be happy with the tradeoff (comes down to how much you care about noise vs getting throttled), especially for a vr device.

It seems a mis-prioritization of the kind that makes me dislike Apple products.

To avoid the imperfection of a bit of fan noise, throttle the entire experience. Great.

It is a machine you literally have on your head. I have not tried it, but I can believe that it requires some different UX considerations than normal computers. I would definitely not like to hear fan noise vibrating through my head.

Wait till you experience visual stutter in VR then...

There's a reason why the Vision Pro has separate chip that handles the real-time passthrough from cameras (and bunch of other sensor-fusion stuff, AIUI).

Wouldn't it still thermal throttle as the whole device gets hot, separate chip or not ?

I understand the threshold for heating up should be lower than with integrated chips, but we're talking about fan speeds, about when that threshold is still reached and cooling is needed.

In the old days, the device settings would allow the user to tune the trade-off to their own preferences. But current user design orthodoxy is that "settings are bad" to an extreme (I actually agree with the weaker formulation "too many settings are bad"... for some value of "many")

Being purely subjective if the user is less likely to notice the throttling than they are the fan noise, then it seems like the right call.

That really depends on what the effects of the throttling are. Stronger foveation or other rendering quality drops? Probably OK. Frame rate dropping below 75? Not in VR, never...

Good take, crazy to get downvoted for it, people get so defensive about their precious brands...

That's true. If they're doing a clever balance then it seems good.

Fine, their products are not made for you.

But they're a trillion dollar company because of their relentless focus on the end-user experience which you happen to dislike, but which most people love.

NVidia passed them in valuation, what does that say about NVidia's end-user experience ?

Profits or valuation can't be a measure of whether a company is doing right to their users or their UX quality.

UX isn't NVIDIA's business model. It is Apple's, and they've found there's shittons of money to be made giving a shit about UX, especially when virtually no one else will.

Apple's current position is cemented by ARM chip performance.

I maintain, bringing market cap to explain whether a company is good at or cares about UX is just irrelevant.

Because the RPM of a fan is not a 100% reliable indicator of its loudness. Sometimes a lower speed can even be louder than a higher one, because of certain resonances...

Presumably, knowing the fan you've installed into the device you've designed, you could map those noisy areas...

Yes, that could work (it would need to be done for each fan individually, because of manufacturing variation). But it's still not guaranteed that the fan will keep working the same way in the future, after some use/deterioration or in untested conditions.

Maybe to give additional fans when the environment is so loud you can't hear them anyway

Makes sense. Humans are really bad at perceiving the environmental noise floor. Our brains just tune it out, but it is has a huge impact on your perception of the loudness of fans that you've strapped to your face.

I can certainly see things like this causing a lot of unintended consequences. "It speeds up when I play loud music" is going to confuse many who don't know about this "feature".

“If you play the music loud, your fps will increase!”

Somewhat, although I guess the idea is still to keep perf flat and just throttle the cooling.

> You should read the link before commenting.

Twitter doesn’t show threads to people who are not logged in (e.g. if you don’t have an account). Shaming people for not reading what they can’t see (or even know exists) is unfair. Using archival sites doesn’t work as a bypass like on newspaper sites.

Not to mention people on Firefox, which from what I have read on HN might not even have access to it at all.

Twitter links should probably be downranked on HN until (if/when) they return to being more accessible.

I had no idea Twitter was doing that. That sucks.

However - I find that less onerous than a paywall and HN is mostly fine about those.

> I find that less onerous than a paywal

With a paywall you know what you’re missing or not. With Twitter that’s harder to determine, which I’d argue is worse. But I wouldn’t say either of our opinions is objectively correct.

> and HN is mostly fine about those.

It is explicitely fine with paywalls which have workarounds.

https://news.ycombinator.com/newsfaq.html

The post you're probably talking about was hidden under "Show Probable Spam" on my end.