Hacker News Reader

That is why I do not use Slack for Desktop, and just keep a pinned tab of Slack open almost all the time. I also tend to reduce my usage of any Electron-based app because I want to better make use of my laptop resources in my development workflow requirements.

I feel like I agree with most what's said there, the same would apply to NW.js and the likes.

This should be a heads up for GUI developers to [re]consider Qt and QML. It made real progress in the last few months. and there are some nice bindings to it.

01walidon Show HN: Qt binding for Go with support for all major operating systems

Oh right, almost forgot that..

01walidon Show HN: Qt binding for Go with support for all major operating systems

dumb question: will qtdeploy produce a single static binary for the whole app or is about some other sort of shared libraries deployment ?

01walidon HTTP throughput regression from Go 1.7.5 to 1.8

That's why I posted this, too many people would be affected by such regression. And would prefer sticking to Go 1.7.x

01walidon Standard Markdown

Please see my comment above...

01walidon Standard Markdown

I really disagree, RTL should be defined in Markdown,.. as the ZEN of Python says:

"Explicit is better than implicit."

this is a case where indicating RTL should be done explicitly, letting the parser/browser or whatever do the work still won't help. Why?

think about a mixed text of one sentence/line where there's only one word in Arabic at the beginning and the rest of it is Latin... the browser/parser or whatever will think of it like LTR text because the sum of latin words > sum of Arabic words. which is False.

A live example of this is Facebook. it does actually a Layout detection based on the content's language in comments. but it sucks in many cases. try to write a comment in Arabic with a mention of someone's name (the name in Latin) to see what I mean.

so IMO, neither dir='auto' nor the parser can detect this implicitly, we still don't have the AI for smarter detection, even if we have, there are cases where you want RTL regardless of the content. thus it SHOULD be defined in Markdown.

01walidon Standard Markdown

Since when Markdown was just about ASCII text ? then we can't write French, Arabic, Chinese using markdown ?

my whole point is to define a syntax indication in the specs on how RTL elements should be identified when converted to say HTML. when converted, THAT element (or the whole document) would contains dir="RTL" attribute in its tag.

for example, something like this:

<-rtl--

Foo

Bar

would convert to:

<p dir="rtl">Foo

Bar

</p>

Prettifying won't help... RTL elements/document should be indicated in markdown

01walidon Standard Markdown

No. It won't just work, it's even shown on your comment how awful it is.

To understand what I mean, try to inspect your comment, add `dir="rtl"` to the <p> tag of the Arabic text...