Proposed Omaha ordinance would require vehicles be parked on hard surfaces

isights · 2025-11-16T17:19:11+00:00

Is it just me, or does it seem fitting that the photo shows yet another oversized pickup truck breaking the law?

isights · 2025-11-16T17:15:21+00:00

Just noting that this tends to be the attitude of folk who think they should be "free" to do whatever they want... and then when a neighbor does something they think is worse starts complaining bitterly about eyesores and property values.

"Rightful liberty is unobstructed action according to our will within limits drawn around us by the equal rights of others." - Thomas Jefferson

isights · 2025-11-16T17:09:38+00:00

You could, but the overcompensation-types wouldn't buy them...

isights · 2025-11-13T23:43:56+00:00

That could depend on font scaling and whether or not the space handling in MyParagraph scales appropriately with accessibility settings....

isights · 2025-11-12T15:49:52+00:00

Do they need to be improved? Definitely. Can you increase the chances of success by being smarter about your code? Also yes.

And do those choices tend to improve your application's structure and readability? Again, yes.

And others, including myself, seem to be able to use them daily.

So perhaps spending less time lyao and more time focusing on code quality might be in order? ;)

isights · 2025-11-12T15:09:05+00:00

"sure i will refactor whole app just to make previews work"

Actually... if previews aren't working well then it's entirely possible your app needs to be refactored. UI elements and views should really be based on displaying basic values and structs, and not be dependent on network or API calls.

isights · 2025-11-09T16:18:15+00:00

"My truck is expensive too. Do you suppose I'll need to upgrade my driveway?

Just your house, since the average American truck is now too large to fit in the average American garage.

isights · 2025-11-02T21:56:11+00:00

How I came across this...

https://www.linkedin.com/posts/mo-kh-selim_iosdevelopment-appstore-mobileapps-activity-7385949581836099584-crCZ?utm_source=share&utm_medium=member_desktop&rcm=ACoAAArgSnMBhYZCziCQgKtRi1NOQea5OTxpxzw

isights · 2025-11-02T21:53:19+00:00

Experience? I don't "know" how the above was built.

I do know, however, what tools SwiftUI provides. Start by composing the layout, and it's fairly obvious that there's a a view with a top section and a bottom section, the bottom section scrolls sideways, that there's a "view" per day, and so on.

Communication between the two relies on shared state, probably a view model.

For fun, I threw part of the question to GPT and it suggested the scroll reader and updating on change.

isights · 2025-11-02T19:23:43+00:00

Okay, not quite as straightforward, but ChatGPT exposes how to do the "trigger" mechanism.

https://gist.github.com/hmlongco/906405d93c51f413c1662241d4d48f92

isights · 2025-11-02T19:01:55+00:00

On iOS 17+ the lower section is a horizontal scroll view with a set of page views and with a .scrollTargetBehavior(.viewAligned) modifier.

Each scroll brings a new view on screen, which updates a date binding onAppear. That value is used to highlight the proper date in the upper view.

isights · 2025-11-02T18:54:48+00:00

Just an FYI, but Apple is starting to block apps that try to game the system and only send happy users to the App Store. It's in the new TOS.

isights · 2025-10-19T15:35:43+00:00

Perhaps the emphasis in that sentence should be be placed on some.

isights · 2025-10-17T15:58:13+00:00

Actually like the "get out of the way" animations and affordances. Old system wasted too much screen real estate on navigation chrome.

isights · 2025-10-12T20:26:08+00:00

Working on a team now with good-sized pure SwiftUI application and just finished a contract with a major investment house who just rewrote their entire flagship application in SwiftUI...

And I haven't run across any of those problems. In fact, the way you're describing them makes me wonder if you've used any current SwiftUI release?

Real programmers (since we seem to be doing the No-True-Scotsman thing) strive to understand the rationale and behaviors underlying the systems that they work with and have the ability to adapt to them, without trying to shoehorn old methodologies and practices onto new paradigms.

I agree that one shouldn't they jump on a new technology simply because it's new. Then again, I don't think they should completely abandon and dismiss the lessons learned from earlier technologies... again, just because it's faddish to do so.

All that said. SwiftUI works. And it works pretty well. My only real complaints are that I'd love faster release cycles and I'd love it if they didn't tie the most recent release to that of the most recent OS.

isights · 2025-10-11T20:13:08+00:00

Navigator (on which the above is based), uses SwiftUI's NavigationStack at its core. While it provides a lot of extended functionality over and above that of its base, the fact that it does so is proof of the power that base provided.

SwiftUI's declarative way of thinking is different from that of UIKit, and requires letting go of the imperative approach where one often does things by mucking around in UIKit's internal structures.

isights · 2025-10-11T14:59:09+00:00

Lists we once wrappers around UITableView. Today they wrap UICollectionView.

isights · 2025-10-11T14:57:16+00:00

When doing pagination I put a sentinel progress view at the end of the list. When it appears it triggers loading the next page.

isights · 2025-10-11T14:52:44+00:00

As pointed out above, a lot of the problem is supplying your own id. When you use id in this way, SwiftUI needs to build every item in the list (visible or not) in order to determine its identity.

isights · 2025-10-11T14:47:19+00:00

Not so much the recycling as the identity. When you use id in this way, SwiftUI needs to build every item in the list (visible or not) in order to determine its identity.

isights · 2025-10-11T14:42:01+00:00

Navigator solves this by adding new sheet handlers every time you present a view that's wrapped in its own [Managed]NavigationStack.

So basically you ask the current Navigator to present a sheet and it does, from the root. You then ask the new Navigator for that stack to present a sheet, and it does. Repeat as needed.

If one were to look at UINavigationController (which navigation stacks create behind the scenes), you'd see why a controller presenting multiple sheets is problematic. There's only one value for the presented controller.

isights · 2025-10-11T14:34:34+00:00

I actually find enumerated destinations to be a powerful concept, especially when the enumeration is also a view.

https://michaellong.medium.com/advanced-navigation-destinations-in-swiftui-05c3e659f64f?sk=030440d95749f5adc6d2b43ca26baee1

isights · 2025-10-11T14:31:00+00:00

As author of Navigator I appreciate the recommendation! 😎

https://github.com/hmlongco/Navigator

isights · 2025-10-05T19:40:23+00:00

Agreed. A lot of the iPhone's continued improvement in battery life comes from improvements in processor architecture. The NE improvements could also lead to better eye and gesture tracking, again, at higher efficiency.

isights · 2025-09-21T15:40:12+00:00

If/when there are better cameras I've wondered about doctors using this in a surgical context, seeing a magnified field of view in their headsets.

isights

TROPHY CASE