Live data from Hacker News

Native all the way, until you need text

justsitandgrin.im

1–10 of 328 posts

Re: Native all the way, until you need text

#3
I just wish there was a native Markdown renderer / editor library in C that I can use cross-platform - in the style of something like IMGUI (where the library outputs a list of primitives for you to render yourself in any graphics API).

Or well... since we now have Claude I might have a jab at this someday in my free time.

Re: Native all the way, until you need text

#5
post #4

How is "performance" defined? Does it take into account the amount of memory required in each case?

The purpose of limiting memory use is so your computer does not become laggy as you run out of memory. We don’t do it for its own sake.

But then, what’s the point in using an inherently laggy technique to save memory?

Re: Native all the way, until you need text

#6
post #4

How is "performance" defined? Does it take into account the amount of memory required in each case?

The purpose of limiting memory use is so your computer does not become laggy as you run out of memory. We don’t do it for its own sake. But then, what’s the point in using an inherently laggy technique to save memory?

How about running many tasks on the machine at the same time?

Re: Native all the way, until you need text

#8
I've had pretty much the same experience with my AI chat app. Nothing works well. Markdown rendering is slow and laggy, streaming is slow and laggy, everything locks up the UI. I've tried at least 5 of the most popular text editor components for UIKit and SwiftUI on GitHub, and all were broken in one way or another, buggy, and slow as well. It's ridiculous.

Re: Native all the way, until you need text

#10
I remember being a junior engineer in 2015, and being asked to render a clickable link within a paragraph in an iOS app. Swift had just been released so we were still entirely on the ObjC/UIKit stack. It was an absolute nightmare. I _barely_ managed to make it work. I haven't really touched iOS since about 2016, so I assumed the new SwiftUI stuff would have this stuff built in. Obviously. Kind of insane that it wasn't.
Post reply on HN