3 ms·
tldr; some labs adopt a proprietary communication and content management system (instead of using existing open protocols) because they don't have the technical
by superkuh 10y ago
tldr; some labs adopt a proprietary communication and content management system (instead of using existing open protocols) because they don't have the technical support, or time, to do it right.
In the short term this increases productivity but in the long term the lock-in will constrain.
- eschaton 10y agoAt the largest CS schools there was some use of a federated Zephyr system for a while from the early 1990s to the mid-2000s. While Zephyr the protocol isn't great, the culture was. And being based on an open protocol and Open Source codebase — since it came out of MIT Project Athena — lots of fun hacks were written atop it too. Also, the primary client "zwgc" (Zephyr WindowGram Client) could run reasonably on a low end workstation like a DECstation 3100 or SPARCstation 1 (8MB RAM, 25MHz RISC CPU, thin Ethernet or SLIP/PPP via dialup). None of this megabytes-of-HTML-and-JavaScript, gigabytes-of-RAM nonsense.
- lvs 10y agoThe very few examples cited in the piece represent outliers. I don't have any peers who are chatting on Slack. Email is fine, and most people know that distractions (like HN) are the devil's work.