When resizing, I expect to drag from the edge of a window. This is exactly how it works in macOS Tahoe, with a sufficient drag zone on the both sides. The only "strangeness" is that the drag zone extends further outside the window in the corner zone. IMO this is nice.

All that said, I REALLY would love to have a hotkey combo I can beep pressed down to resize anywhere over the window. Just like in many Unix/Linux window managers.

Yeah, I have to agree. The blog post seems convincing when you look at the images, but now that I've actually been playing with it, I can always drag the corner to resize. In fact, the corner provides much more draggable area than the window edges do. There's no problem.

So I agree it's strange that the drag zone extends so far beyond, but that's not really something to complain about...? Everywhere inside the corner where it feels reasonable to resize, it resizes. The article is expecting an absurd level of a drag zone on the inside.

Again, the large drag zone outside the corner is kinda weird. But honestly that's more just an understandable artifact of the corner drag zone being a square. If it were me, I probably wouldn't bother to round off one corner of the drag zone either.

There's a lot of stuff to criticize about Tahoe, but this would be about last on my list...

There is this obscure setting you can enable to be able to click anywhere on a window while holding Command + Control to move it.

defaults write −g NSWindowShouldDragOnGesture −bool true

This only supports moving around windows, not resizing.

And yet Mac OS didn't support resizing from edges, or any corner of the window except the lower-right ONE, until well into the 2000s. Incredibly dumb.

Yes, downvote facts.

After 25 years of building web frameworks at Vaadin, we asked: what if the AI is in the driver’s seat? Would we even need a UI?

In Computer–Human Interaction (CHI), the AI runs a business process. When it needs something from a human, it creates a purpose-built UI in real time, adapting as you interact.

No code. No pre-built app. Just AI “speaking” in UI.

Demo: computerhumaninteraction.com

Questions for HN: • Best use cases you can think of? • Which AI models would work best for this? (everything we’ve tried so far is either too slow or too dumb) • If CHI creates something innovative, please share the link to prompt here (you can copy it from the demo after it yields results)

Vaadin’s 3rd brand iteration is a refinement embracing touch of geekiness. Toolkit is for internal use, but shared publicly as it might help others building dev-led products.

I would love to see terminal/unix being part of the story. I realize that one can install Termux, but telling the story without it would be super attractive for developers. It would also further differentiate from iPad.

Any thoughts on this for us developers?

GP has said elsewhere that they are going to provide bootloader unlocking, so alternative OSes should be possible.

Estimating computing power of Fenix 6, Fenix 7 / Epix 2 and Apple Watch S8 and Ultra based on CPUs specs found by device tear downs. Comparing other HW aspects of the given watches as well.

To help myself decide if I'll keep my new Ultra or the trusty Fenix, documented differences sensors, hardware and training metrics. I think I now have an answer.

Location on Fenix 5 is quite inaccurate compared to Fenix 7 or Ultra - especially with tree cover.

I mean my Apple Watch 3 is spot-on compared to the Fenix 5 which could be off by double-digit percentages. I found the Fenix 5 was pretty accurate on straight paths. But, yeah, tree cover, switchbacking up hills, etc. really threw it off.

I totally get all the arguments in favor of the Fenix 7 or related. It's really a question IMO of whether you want a mostly dedicated watch for relatively hardcore outdoor activities or if you want an Apple Watch and its ecosystem to do routine day-to-day smartwatch things while also doing a lot of outdoor activities better than prior Apple Watches though probably not overall as well as a dedicated device.

I was sort of on the fence prior to the latest announcement but, for me, the Ultra seems the pretty clear choice.

Any proof for Garmin sensors being more precise?

TheQuantifiedScientist on his YouTube channel has great tests for many wearable devices and their sensors. His assessment has been very favorable for AW Ultra on HR, location and sleep when compared to Garmin devices: for sleep tracking Garmin is very inaccurate, for HR and location Fenix 7 and Ultra are identical. Fenix 6 and older are poor.

Blood oxygen and temperature seems to be quite inaccurate on both.

Just my own anecdata I guess. I’ve always found heartbeat and location tracking to be a lot better with the Garmins. I haven’t trained with the new Apple Watches yet though, so maybe I’m completely wrong…

Ultra has almost the double physical battery and may have some exclusive optimization to GPS and HR that may not come to other watches when released later this year.

I think that the iOS built-in map component does not support offline vector maps. Most apps (with exception of WorkOutDoors) use that and cannot support improper offline without Apple updating the component.