If you can find a piece of software that does what you need in a timely manner and is within your budget, then by all means use it and move on. But sometimes you need a feature or a flow that can’t be bought for any cost. You must roll your own.
I’d run for the hills if you can’t stand computers, because the only thing worse than computers is programming computers. But if you have the muster and the gumption you to can make the computer go beep.
Chances are there are ways to make it go beep without you writing your own software but what is the fun in doing that?
The Tool Makers Dilemma…
Sometimes though, you just build to build. This is very, very dangerous. It is the state that I am in right now with the Session Link Engine. I’ve learned and forgotten the web stuff a few times since I started with it in the late 90s.
The purpose of this build is to relearn the web and ship a web app. So what do we make? A modern wiki: https://sessionlink.herokuapp.com/
This was never meant to be a single player game… Perhaps the biggest change in humanity over the past 200 years is the ability to communicate over the wire or the air thousands of miles away instantly.
The Hive Mind is a real thing and is buzzing with all of your data. The aggregate.
I’ve been working on a proof of concept prototype for multi-user editing. Co-design if you will. Essentially a google docs shared cursor:
This has been my side project for a few months and it uses Typescript, React, and WebSockets. Beware that there is no privacy features yet. So be good.
Open it up in two+ different browsers/machines etc 🙂
Standback google docs.
I will do a walk-through of the source code soon. Here are some shots during development.
We still have callback hell here with my commando function. It is passed into every block and is the way that everything updates. Not sure if I will keep this but it works.
Main render from “Playbox” the root component of app. I have a file drop that isn’t being used yet.
The kids these days call it hydration/dehydration instead of deserialize/serialize:
On the todo list:
- Private Channels w/ XOR Key
- JSON Deltas not full blobs for transmission of edits
- Throttling server/client
- Usernames/Colors not random
- Actually Reseeding the data to new users
- Collision Avoidance Schemes w/ Time travel
- File Sharing
- Markdown Editing
- DataTable Editing