Very good library
01:34 – js-git
11:22 – jack
15:42 – Performance Issues
16:36 – Community Fundraisers & Support
21:41 – Atom
23:22 – npm
28:46 – js-git as a Database
30:49 – The Future of js-git & tedit
- Open Source
- Isaac Schlueter: Money and Open Source tl;dr – The current situation isn’t optimal
- Thoughts about future of js modules using js-git
p dir="ltr">35:31 – Replacing npm
A-DATA Premier Pro SP900 128GB SSD
Successfully build a Fusion Drive with SATA-3 6GB/s. And my mac become super fast now.
One of the most eye-catching features we’ve seen so far is the same always-listening experience that we’ve enjoyed on the Moto X. Anytime you need to do something with your watch, just say “OK Google" and everything from pulling up nearby gas stations, to restaurant reservations are just a quick voice command away.
Interesting project to change the doms according to html by React diff.
It compiles the ajax loaded html into jsx and convert to react components.
I hope next step will be reporting the already changed doms to React virtual dom tree.
Currently using a log of websocket. And I know there is EventSource for a long time.
Server-Sent Events vs. WebSockets
Why would you choose Server-Sent Events over WebSockets? Good question.
One reason SSEs have been kept in the shadow is because later APIs like WebSockets provide a richer protocol to perform bi-directional, full-duplex communication. Having a two-way channel is more attractive for things like games, messaging apps, and for cases where you need near real-time updates in both directions. However, in some scenarios data doesn’t need to be sent from the client. You simply need updates from some server action. A few examples would be friends’ status updates, stock tickers, news feeds, or other automated data push mechanisms (e.g. updating a client-side Web SQL Database or IndexedDB object store). If you’ll need to send data to a server, XMLHttpRequest is always a friend.
SSEs are sent over traditional HTTP. That means they do not require a special protocol or server implementation to get working. WebSockets on the other hand, require full-duplex connections and new Web Socket servers to handle the protocol. In addition, Server-Sent Events have a variety of features that WebSockets lack by design such as automatic reconnection, event IDs, and the ability to send arbitrary events.
It is interesting that many libraries are not using EventSource (SockJs seems support that).
I think websocket.io entry the market first and it is already very simple. So everyone support it until something 10 times better come out.
May be a library to normalize all notification of iOS, android and desktop browsers?