@emlyn I use the website in a Fluid container. Better than whalebird. Not native of course.

@jeffmc I use Fluid sometimes but I've never been a fan of the Tweeetdeck interface.

@emlyn Electron is a scourge in the guise of sanctity

@jeffmc I don't mind it in Slack that much but they've obviously put a lot of work into getting it to work well. By the time you do all that, I feel like you could have just implemented it on each platform.

@jeffmc The memory footprint and small non native feeling things will always be a problem though no matter how much work you put into it.

@emlyn agreed. The write once run everywhere strategy, in the effort to be platform neutral, is and always be a bad decision. But when managers tell people that Javascript is as efficient as native, they are either clueless, incompetent, or nefarious. I, still to this day, wonder how one can say an interpretive language is much better than a compiled language and keep a straight face. 35+ years in computer architecture and compilers leads me to just shake my head.

@jeffmc @emlyn "Write once, run everywhere" revitalization in the Javascript era is way worse than the Java one. It's like an era of forgetfulness... people writing nodejs modules attempting to reinvent what GNU already does (like an "rm" module--wtf?). And it's like people are just assuming that nobody is around who does lower level development...which was considered high level when I was in school. For these non-performant apps that show their true colors the second you resize the app window.

@volkan @justkevin @jeffmc there’s nothing that makes it inherently faster to write an app in JavaScript. If all you know is JavaScript then you won’t have to learn anything new but someone who knows how to build native apps can build a better app faster using the native tooling.