Hacker News Reader

Comment by wlesieutre | Hacker News Reader

If I’m not mistaken, the actual chat contents in Adium were rendered with web views, and its configurable message styling was done with HTML/CSS. The whole program wasn’t stuffed in the web view though, it was a presentation layer on top of a native backend.

EDIT- here’s a source on that http://meyerweb.com/eric/thoughts/2005/12/19/adium-chatting-...

View on HN

Yes, this is accurate. Adium’s message views were almost entirely HTML and CSS with very little JavaScript. The bulk of Adium’s “brains” were written in Objective-C (and plain C, via libpurple).

Yes, this is what the native macOS Messages.app does as well. On my Mac, with relatively heavy usage, I'm at around 100 MB of RAM.

It clearly works pretty well that way. Textual (Mac IRC client) is the same setup.

Slack, on the other hand, feels like JavaScript frameworks piled three or four deep, often getting its UI out of sync with the actual state.

Chats/channels will briefly flash (1) unread in the sidebar to tell me about my own message that I just sent, or I’ll continue to have a blue “10 new messages” banner in a conversation that I’m actively participating in.

I use it because it’s convenient, but there’s definitely room for improvement.

Wow, that's crazy. The iOS Messages app is native. I'm only familiar with iOS development... is AppKit that bad?

UIKit is noticeably better than AppKit but I doubt this is the reason why Messages is webview based. I don't know the exact reason behind it, but my guess is that they stopped caring about updating it when the people working on it either left or moved over to other projects.

I've taken that same guess after the new fancy effects and animations for iMessage got fully implemented in iOS 10 and barely supported at all in macOS Messages. It seemed like an afterthought on the Mac.

Well! You learn a new thing every day.

Reply on news.ycombinator.com