Amazing how the author can talk at length on CRDTs, and even have a section called “What are CRDTs”, yet never actually spell out “conflict-free replicated data type”.
Yeah! An oversight (I link to CRDT.tech though!) Part of it is that the acronym has been overloaded over time. Conflict Free, Convergent, Concurrent, Commutative, etc. I have just opened a PR that addresses this comment.
I don’t think it is that amazing, when you consider I say that the article is not about CRDTs, and won’t be explaining them, and links to sources. But I appreciate 1. that you read it (thanks!) and 2. took the time to comment. I have addressed that comment in a PR, and I hope our marketting team can merge+publish when America comes online.
EDIT: to say, we have fixed that oversight. Many thanks!
I would think most people who care about an open hardware platform would also care about open software. Why isn’t Linux front and center as something to run on this? Im not excited by ‘a bunch of distributions will work and we’ll provide instructions’…
It’s easy to sell something familiar to people with the promise - “it’s repairable, too!”.
The market for Linux and BSD and more niche OS is much smaller than the market for Windows laptops that won’t fall apart in two years and be terribly expensive to repair.
I’m speaking at the Computer Science Trackers Association national conference!
Preparing teams for HSPC ( high school programming competitions)
Using Retrocomputing in Education
Involving the community in your classroom
It’s been a long time since I monitored a small group of physical machines, but back in the day Monit gave me stats on each individual process on each machine, Munin aggregated all the physical measurements of the machines into one dashboard, and an external service like Pingdom let me know the machines were up.
It was a sweet little set-up I was always proud of.
This computer scientist clicked the link prepared to argue, but happily found a sane argument! Thank you!
Sigh… another cool project with a readme that starts with ‘how’ without explaining ‘what’ and ‘why’.
Give me the short story… tell me your motivations… more people will connect with this than they will the packages they need to apt-get.
31 years in the industry here. You’re mostly right on all these points. In several cases you need to learn where ‘it depends…’ is the right answer.
I’m sorry you don’t seem to have benefitted from good project management. Your next growth spurt will either come from being exposed to good project management, or suffering through a few years where you’re the bad manager.
Ruby is the glue that never sets.
Recursion should be on this list. Lisp is considered the first language to have supported it, according to McCarthy’s History of Lisp: http://www-formal.stanford.edu/jmc/history/lisp/lisp.html
I think that’s true. Recursion was a contentious subject in the ALGOL conference, and I think it was McCarthy and some of the European committee members who insisted on it, whereas Backus thought it superfluous.
Just because the world has more polyglots in it today doesn’t mean Ruby is dying… sure, it had a huge spike because of Rails, and those ideas percolated everywhere, but Ruby as a language unto itself it more popular than ever.
Ruby has been a dramatic influence on both Elixir and Crystal, and many people love its goal of ‘developer happiness’. History will judge the impact it’s had 30 years from now, but I think it’s going to fare well.
I don’t think this is a binary decision, I think it’s a spectrum of risks. Some teams and some kinds of projects will be more tolerant of risk while others will be risk-averse and only jump on board once there are people with operational experience available to guide.