Viewing profile — tmail21
tmail21
HN member- Joined
- Wed, Sep 16, 2015, 5:09 AM UTC
- HN karma
- 43
- Public activity
- 60 items
- HN profile
- View on Hacker News ↗
About tmail21
Recent public activity
-
comment
Comment #16090921
You might want to check out TMail21 ( https://tmail21.com ). It is thread (topic)-oriented. It also adds shared (versioned) facts to threads which opens up an interesting set of us…
-
comment
Comment #16001380
Actually we use React+mobx on both our web and RN stacks and it's been great. What we really like is that it is simple and extremely performant since in most cases it automatically…
-
comment
Comment #15192253
The issue is that these chat apps are inherently distracting. They work well for tight synchronous communication in small coherent groups. You might want to check out https://tmail…
-
comment
Comment #15009006
Sure. Hyperledger Fabric 1.0 has the option of "Channels" to limit viewership rights. In particular it restricts rights to a subset of the community. For example, you may have a 10…
-
comment
Comment #15008859
The other major issue with Blockchain is that "all nodes can see everything". This is theoretically a problem with distributed databases as well. However, in the case of distribute…
-
comment
Comment #14642868
agreed. Although have encountered most of these ideas before, the goo analogy (whether valid or not) made everything easier to relate to. ps) Not a physicist.
-
comment
Comment #14587626
I don't believe that one should try to create a single tool that covers both synchronous and asynchronous. Their UX is too different. It seems to me a better idea to create an asyn…
-
comment
Comment #14587414
These are some great points. You might want to check out https://tmail21.com . We built this around what we called Deep Collaboration (a riff on Deep Work). We built it to be Threa…
-
comment
Comment #14564420
You might want to consider a deep collaboration tool (specifically built for asynchronous communication) like TMail21 ( https://tmail21.com ) . Deep Collaboration makes Deep Work p…
-
comment
Comment #14369986
Not sure about the governance model of Kotlin. Hopefully it succeeds.
-
comment
Comment #14369947
Yes, but the resulting object is not a "List" and hence would not inter-operate with any function that took a List as input. In essence if the original object implements a List _in…
-
comment
Comment #14369051
Cool. This needs to be built into the language or somehow standardized by the community. With lack of standardization of immutable collections, there would be lots of different way…
-
comment
Comment #14368982
"Read-only" would not implement structural sharing. Consider the situation where you had a linked list with 10,000 elements and you wanted to return a new list with one new element…
-
comment
Comment #14368532
Looks like there is some distinction between Mutable, Read-only View and Immutable. According to this http://stackoverflow.com/questions/33727657/kotlin-and-immut... Kotlin does no…
-
comment
Comment #14367945
What about immutability? A key part of functional programming is using immutable structures to avoid side effects. My understanding is that Swift has these to some extent ("let" vs…
-
comment
Comment #14267430
How do you know for sure? :)
-
comment
Comment #14208392
Agreed that all of these can be used asynchronously. However, I would refer to these as "incidentally-asynchronous", in the sense that their design goals were not primarily to be a…
-
comment
Comment #14203799
Ever increasing distraction and "real-time" communication and collaboration are reaching a point of diminishing returns and actually decreasing our productivity. The book Deep Work…
-
comment
Comment #14090787
Hope this does not come across as self-serving, but I think it is relevant to the discussion. We have built a product around what we call "Deep Collaboration". Deep Collaboration i…
-
comment
Comment #13794254
The problem is that Slack is designed for synchronous communication. However there is a huge need for a collaboration tool that is designed for asynchronous communication. Being sy…
-
comment
Comment #13432844
I also agree that adding Facebook-style commenting is not the best approach. It has the virtue however of reducing clutter in a Slack channel (a laudable goal), but represents a mi…
- story
-
comment
Comment #13292388
If one absolutely wants real-time collaborative editing then the only (long-term) solution I see is something like a deep learning solution that continuously semantically analyzes …
-
comment
Comment #13292215
Yes, this problem could be mitigated somewhat by showing caret positions. But this method is very reliant on the users paying extremely close attention. It does not work at all whe…
-
comment
Comment #13292137
It is fairly trivial to construct an example where editors are editing _different_ sentences and OT takes two locally semantically correct states and converges to a semantically in…