📰 Collaboration with Atom Teletype📅 August 9th, 2018 ⏲️ 1 min 55 secs
Origin of the name “Teletype”
Collaborating remotely seems painful when it is about coding a script or styling a web page between team members or friend, specially when it should be in a real time.
Real time Collaborations
The first time I tried to collaborate with a classmate, I remember using MSN by creating a shared folder and putting all the source code. when changing a file, we wait for the synchronisation and then we refresh the page. But it seems painful because We don’t know what is editing and that’s why we voice chat to take decisions.
Git was a huge tool for me at the beginning, but in the end, it changed my perspective of working and uploading the source code in the server. With GIT, we expect a whole process of pushing and pulling requests to receive the collaboration codes. We have to run git pull to get the updated code on our local machine. That’s why GIT is not the best solution to work in real time.
With Teletype is’t real time and secure
Today, there are many tools like google docs and many other tools that offer real-time collaboration, we share a document and we see lots of people writing at the same time. Such a connection and amazing sharing. We write with people who are thousands of miles away from us writing a plan or a doc. It’s great to write a document, presentation, sketches but if we want to edit a node script running with “nodemon” it’s a little bit confusing because we have to replace the updated file with the old one and re-run the script each update. Now, such a tool is implemented today in a text editor developed by Github called Atom, this IDE which becomes indispensable for me finally integrates it into its list of packages under the name of Teletype.
With Teletype, there is no centralized servers, only a sharing P2P connexions between developers. it only run one host who shares the code and the others share it even if the host closes the session.