gnachman

13 ms·

91.
by gnachman 8y ago
Please file an issue and include a debug log
92.
by gnachman 8y ago
You have to analyze a row of text at once to reorder glyphs, which is expensive and cannot be parallelized.
93.
by gnachman 8y ago
It’s a very hard to fix bug when restoring windows when the scroll bar style doesn’t match. I should revisit this.
94.
by gnachman 8y ago
Github’s issue tracker is lousy so issues have been on gitlab since google code slipped this mortal coil. I don’t want to lose my GitHub stars so code remains there. I guess there’s not much reason to change it now even if github does impro
95.
by gnachman 8y ago
It falls back to the old renderer in these cases. Transparency will be supported in Mojave.
96.
by gnachman 8y ago
It’s important to some people but probably not a majority. Ligatures are a best effort kind of thing. Where trade offs must be made, such as drawing performance, I choose to let the user make that choice.
97.
by gnachman 8y ago
It existed before I took it over but it has changes quite a bit since then, kinda maybe?
98.
by gnachman 8y ago
File an issue! There are only a few bits left for style so they have to be used judiciously. Or come up with a better scheme for storing character attributes.
99.
by gnachman 8y ago
Only if openstep catches up with Apple, or I retire. I wouldn’t hold my breath.
100.
by gnachman 8y ago
No, it's not. Each visible pane gets its own thread, and three frames are pipelined. That means you could easily keep two cores plus your GPU going full steam (provided you have an underpowered GPU, which you almost certainly do, becau
101.
by gnachman 8y ago
This will be fixed under macOS 10.14! It's already enabled on the nightly builds. The blending isn't quite right yet, but I only had a few hours to spend on it.
102.
by gnachman 8y ago
There is no official feature roadmap, but here's the current plan: 3.2.x will be focused on rendering improvements. The full change log is here: https://iterm2.com/appcasts/testing_changes3.txt 3.3, which is curre
103.
by gnachman 8y ago
iTerm2 was not designed for GPU rendering from day one so it suffers from some complexity that hurts performance. This will get better in macOS 10.14 because I won't have to worry about subpixel antialiasing which adds some extra steps
104.
by gnachman 8y ago
Yes, Terminal does it more independently. Maybe some day I'll make enough on Patreon that I can quit my day job and fix that :). If this is really important to you there are knobs you can turn to trade off refresh rate vs throughput. E
105.
by gnachman 8y ago
It's a funny feeling opening hacker news and seeing your project at the top :) In iTerm2's case it's because of bad decisions about a decade ago. The data model is read & written on the main thread. The main thread is sol
106.
by gnachman 8y ago
I released a build of iTerm2 last year that accidentally disabled subpixel AA and everyone flipped out. People definitely notice. But the reason I’m sad is that this wonderful hack was short lived: https://docs.google.com/do
107.
by gnachman 8y ago
Please fix the dumpster fire that is AppKit! Doing a grep for angry words in my source code and commits reminded me of some traumas over the years… * Core Data's generated classes are broken for one-to-many relationships * NSTableView
108.
by gnachman 8y ago
I guess I made the big time! The iTerm2 one is interesting because it came too late. Apple's patch disables Sierra's native tabbing. Version 3.1.3 did not disable it completely. I published a fix in version 3.1.4 which came out on
109.
by gnachman 8y ago
When the metal renderer is enabled the screen updates at 60fps. When it is not enabled, the refresh rate is governed by the current bandwidth. There are cases where the new renderer has lower throughput because it does not use adaptive fram
110.
by gnachman 9y ago
It’s good in traffic jams. You can relax a lot more than driving yourself or autopilot at high speed. The worst case scenario is a fender bender.
111.
by gnachman 9y ago
Aolserver’s legacy lives on?
112.
by gnachman 9y ago
The first paragraphs here are horrifying: https://www.mv-voice.com/morgue/2001/2001_01_19.supe19.html > According to Alana Lee, the EPA project manager for the site, the air stripper on the Netscape campus was
113.
by gnachman 9y ago
How do you know the variance of your sensors? Do you have to experiment in a controlled environment?
114.
by gnachman 9y ago
My experience at Google and Facebook is that junior devs are hires in great numbers. Intern season means you can’t find a parking spot because there are so many of them. This article doesn’t ring true to me, but my view of the world is narr
115.
by gnachman 9y ago
Thank you. I’ve been looking for a better explanation than wiggly snakes for thirty years.
116.
by gnachman 9y ago
That makes sense. Our problems are somewhat different. Do you need to deal with arbitrary combinations of foreground and background colors? For me this was the hardest problem to deal with because of subpixel antialiasing.
117.
by gnachman 9y ago
Caching is great but it doesn’t help you when paging through a big file where the entire screen contents get replaced on each update. Is that not what you benchmark?
118.
by gnachman 9y ago
I'm surprised you found creating attributed strings and CTLineRefs was acceptable. These are the main bottleneck in iTerm2's renderer, and I ditched them when rewriting the renderer in Metal. Since ASCII is an important fast-path
119.
by gnachman 9y ago
iTerm2's design is saddled by some history. At the time I took it over, everything was done in a single thread. By the time I realized I was going to stay with the project and how bad the design was, it was too late to change it. I&#x2
120.
by gnachman 9y ago
I recall seeing a Google tech talk over ten years ago where they talked about cleaning up OpenOffice (or was it StarOffice?) it was memorable because they mentioned it did #define private public. I’m impressed they kept at it and it sounds

More ›