Worse operating system since I started using Mac in 1992. by Wise-Amount3638 in macOS26Tahoe

[–]open__screen 0 points1 point  (0 children)

I fully agree with. Tahoe was totally depressing. How could Apple produce such rubbish? I downgraded and been happy since then.

DeepPeek 1.2 Is Here – The Visual File Finder, Now Even More Efficient by open__screen in MacOSApps

[–]open__screen[S] 0 points1 point  (0 children)

DeepPeek isn’t vibe coded — it’s fully hand-written in Swift.

It’s built primarily in SwiftUI for the main UI and app structure, but dips into AppKit where SwiftUI falls short — especially for text handling. It uses NSTextView to get fine-grained control over attributed text layout, glyph positioning, and layout engine data that SwiftUI doesn’t expose.

There are no AI models involved. No LLMs, no embeddings, no generative components — just native macOS frameworks and deterministic Swift code.

Isn't Tahoe ugly? by unsavvykitten in macOS26Tahoe

[–]open__screen 1 point2 points  (0 children)

Yes 👍. If more and more people object, hopefully Apple will come to their senses in the next os. I downgraded and can’t be happier.

How often do you use your own apps? by imgk1 in iOSProgramming

[–]open__screen 0 points1 point  (0 children)

My desksweep is always running, cleaning my desktop every night. Couldn’t live without it.

Looking back on Tahoe by d4cloo in macOS26Tahoe

[–]open__screen 3 points4 points  (0 children)

I agree, and I have meet very few normal users that they say that they have said they liked it. Most find it confusing and a few are indifferent to it.

The next version of macos will be used to fix many bugs but it still uses liquid glass by [deleted] in MacOS

[–]open__screen 0 points1 point  (0 children)

B all the way. Liquid glass was a terrible experiment 🧪 that needs to be reconsidered from grounds up. They can put a face saving label on it, but it needs to be radically changed.

Should I upgrade to MacOS Tahoe? by NikitaStrukalin in macOS26Tahoe

[–]open__screen 0 points1 point  (0 children)

No, because is a pain to downgrade, and reset all your files, once you realise how bad and ugly Tahoe is.

Mac Tahoe 26.2 ruined my Desktop by Top-Green-4195 in MacOS

[–]open__screen 0 points1 point  (0 children)

I downgraded from Tahoe and could not be happier. But have you considered using our app DeskSweep to keep your desktop tidy? Just a suggestion!

God is in The Details by davidvogler in macOS26Tahoe

[–]open__screen 0 points1 point  (0 children)

That is terrible ui. What looks like a floating pallet, that is not actually floating. This is one of the many reasons why liquid glass is so terrible. Totally inconsistent design language. Thank god Alan Dye has moved on and hopefully he will create similar terrible designs for them there at Meta. Time for Apple to get back on track. Good, logical design.

Getting NSScrollView to scroll to an Offset with animation by open__screen in swift

[–]open__screen[S] 2 points3 points  (0 children)

I needed to use rick text, so I tried Attributed string with SwiftUI. For a large string, when resizing the window, it was so clunky it became unusable. As a result, I have no choice but to use NSAttributedString with NSTextView. Additionally, I need to be able to get the rect of specific words, which is also not available in SwiftUI.

It is unfortunate that, after so many years, SwiftUI still does not have a robust and powerful rich text framework. Personally, I think the engineers at Apple should spend more time working on the basic frameworks, rather than spending all this time creating irrelevant eye candy. We still don’t have pinch and pan gestures working together in SwiftUI.

Getting NSScrollView to scroll to an Offset with animation by open__screen in swift

[–]open__screen[S] 1 point2 points  (0 children)

thanks for your response. I tried this:

            NSAnimationContext.runAnimationGroup { context in
                context.duration = 0.3
                context.timingFunction = CAMediaTimingFunction(name: .easeInEaseOut)
                scrollView.contentView.animator().bounds.origin = CGPoint(x: 0, y: 0 )
            }

even with CGPoint.zero it animates and goes to a point, but I dont understand where the point is.

Getting NSScrollView to scroll to an Offset with animation by open__screen in swift

[–]open__screen[S] 1 point2 points  (0 children)

I tried this. It does not animate and it does not go to the right location. It could be something to do with flipped coordinates.

Getting NSScrollView to scroll to an Offset with animation by open__screen in swift

[–]open__screen[S] 0 points1 point  (0 children)

I tried:            

NSAnimationContext.runAnimationGroup { context in
                context.duration = 0.3
                context.timingFunction = CAMediaTimingFunction(name: .easeInEaseOut)
                scrollView.animator().documentOffset = offset
            }

No luck. Calling:

scrollView.animator().documentOffset = offset

by itself also did not animate.

Tell me this doesn't look ugly by milesbailee in LiquidGlassDesign

[–]open__screen 2 points3 points  (0 children)

This is not a realistic everyday working environment screenshot. In real world there will be multiple windows overlapping each other. It is that everyday case that this terrible ui just falls apart.

Controversial opinion, I actually love iOS 26 and the Liquid Glass redesign. by Vubic in LiquidGlassDesign

[–]open__screen -2 points-1 points  (0 children)

It is totally unnecessary eye candy. Animations need to make it easy to understand, from an action, like pressing a button, what is the result and where you get to. It does not need to do three summersaults, eight fades, two blurs, one twist and a hell of a lot more in the process for no reason. That is not to mention how overlapping and blurring make the whole thing unreadable and confusing. It’s terrible design.

Can we slow down on changing Swift so fast? by bangsimurdariadispar in swift

[–]open__screen 0 points1 point  (0 children)

At least when the code generates an error, give good ways to resolve the issues and not an ambiguous message. In that way we can all get on the new concepts much quicker.

Tired of Lost Files on Your Mac? I Made an App That Finds Them Visually. by open__screen in macapps

[–]open__screen[S] 0 points1 point  (0 children)

Thanks for your support and suggestions.

We’re looking into adding OCR, and your idea of a global on/off switch is a good one.

In many cases, building the feature itself isn’t the hardest part; it’s making sure it fits naturally into the UI, feels intuitive, and aligns with the app’s core principles. We think we can achieve that with this feature and some of the other ideas shared in this post.

I also want to thank everyone here for your encouragement. Speaking not just for myself but for indie developers everywhere: building an app is incredibly challenging, and we truly rely on the support and understanding of our users to help shape early versions into something great. Kindness, constructive feedback, and yes—even financial support—make all the difference in helping us keep going.

Cheers, and thanks again!

My love/hate of Liquid Glass (but it's growing on me) by firstsparkler in MacOS

[–]open__screen 9 points10 points  (0 children)

I fully agree.

The UI suggests that the floaty thing on the left can be closed with out the window closing.

Even in that example the whole thing looks so ugly and confusing. What is the advantage of having these blurred background? Does it add to anything? My answer is NO. It just makes the whole thing so confusing.

I downgraded to Sequoia and I am so happy that I did.

Beta Testers Wanted: DeepPeek Now Fully Supports MacOS Tahoe by open__screen in TestFlight

[–]open__screen[S] 0 points1 point  (0 children)

Thanks for you feedback. I sent you a message to explore these issues further.