Ideal Node.js hosting service
Here’s the URL of a GIT repo, containing a Node app. Run it with forever.
I want to be able to do a tail -f on the log so I can see what’s going on.
And to view its file system, perhaps through a browser-based JS app.
I think that’s about it. I give you a URL, you run it.I know some services get close, but I don’t want close. I want just this. A Node virtual machine.
Source: A Node virtual machine
A preview of Dave Winer’s new blogging system : 1999.io
Very interesting (and inspiring) to get an insight into the visions of the people behind Racket.
Long live Mind Traffic Control!
No New Year’s Resolutions or even questions this year. But as an honorary Brazilian, my new year doesn’t really start until after carnival, so now would be the time for it.
However here’s a quick update. The answer to the old MTC question is now resolved for me.
It’s time to put the bullet into the Mind Traffic Control that was. The case against it is overwhelming. MTC was written to learn the exciting new world of Google App Engine and the style of web programming of the mid to late 2000s … Python, something almost Django-like (ie. Rails-like). Backed by a relational database-like thing.
It’s a world I later fell out of love with. Python and Django are … fine. But they aren’t what continues to excite me in 2016.
I toyed with Meteor. But how to host on GAE? And, anyway, in 2016 I have the sickness … I just AM a Lisp programmer. Not necessarily a very good one or particularly experienced one. But I’ve succumbed. This is what I’ve been looking for all my life. It’s what I want to do, going forward.
So a rewrite in Clojure / ClojureScript. That presumably can be hosted on GAE. And I can have a wonderful new reactive UI with Om.
Yes … I’ve been playing around with it … but …
But then again. The old GAE database isn’t a good match for the circular queue of MTC. And worse, I’m not keen on storing my personal data on someone else’s cloud. Yes, it would have to be a single-page app. Yes, it ought to talk to remoteStorage and offer Dropbox etc. too.
These are all wonderful things and yes I am playing with them and want to use them. But … MTC? MTC is a todo-list app. There are a million and one such apps. They’re the “hello world” of browser-based GUI frameworks.
I’d love people to experience what’s good about MTC. But is it likely? How would I cut through the noise of those millions of alternatives? (Some of which are very slick.) Could I really get any kind of audience for a todo-list app in 2016? Does it make sense to put my energy in this direction?
And then again … if I’m going to boot up my browser and run a local server, then I have OWL.
OWL is great for more extensive, smart-disorganized note-taking. It’s just that it doesn’t have some of the charms of MTC. It’s not dynamic … tasks sit around and clog up the pages. You have to navigate around to find them. Sure, it’s pretty easy to navigate around – wikiness makes complexes of documents into small-worlds – but it’s still lacking that immediacy of the river / feed of tasks.
So last year I was fairly convinced that MTC was just going to become OWL hosting. But that isn’t what happened. There is still something to MTC, to the todo-queue concept. And it has resisted being subsumed within the OWL paradigm. My early enthusiasm for OWL was wrong about this. And my initial intuitions vindicated.
So what next? These last months I’ve been drawn back to the command-line. And also to Racket. Which compiles to fast executables. (Clojure is great, but the JVM does take a long time to start.)
And I’ve been admiring (again) todo.txt. Which in many ways is the right approach.
And so … I present : the new Mind Traffic Control. Which is, I admit, nothing but a short Racket program. That reads a file called “todo.txt” from somewhere on your machine. And does MTCish things with it.
– it’s (right now) a convenient command-line tool.
– it’s compatible with your existing todo.txt file. It doesn’t do everything that todo.sh does. But it has its own tricks.
– in particular, it keeps the queue-ness. You only see the latest item. And most of its commands are about flinging tasks you don’t care about now into the future where you don’t have to think about them (yet).
– obviously it loses a lot of what made the GAE-hosted, web-based MTC interesting. There’s no delegation to other users etc. But I’m not sure many people used that.
– very simple. very minimal.
I have to say … I am EXCITED by this … more excited than I’ve been by any potential refresh I could have made to the old MTC paradigm (even rewriting more or less the same thing in Meteor or ClojureScript / OM). This is fresh and different.
The Future : MTC has a new mission.
Firstly it’s going to be MY todo-queue tool. Previously, the web version was always thought about in terms of “what might people want?”. In practice, almost nobody else wanted it. Now MTC’s mission is “what do I need from a tool?” What maximizes my convenience? I like the command-line. I’m comfortable there. That’s where this is going to be.
Secondly, I’m not that into task-management software. I want software to help me DO stuff. And the focus of MTC going forward is going to be to add features to help me do. For example, I have an item with a link I wanted to read. I now read the link and want to post it to a link-blog. Can that feature be added to MTC? Why not? I come up with an idea for a new project and start putting todo items about it into MTC? Can MTC create the project directories for me? Can todo items be exploded into actual scripts? Within this environment? Once again, a direction worth exploring. (In a sense, MTC with extra tools could be seen as exploring the coming UI paradigm of bots in rivers.)
Syncthing is now my synchronization solution. I don’t think I’m going to worry about clouds and hosting, because I want to use horizontal P2P syncing as the way of making sure the queue is on all my devices.
The original MTC site will be updated shortly. You can, already, export your data from it in todo.txt format. That is now the recommended solution for MTC users. The new version of the site will probably continue to let you do that, without adding anything new to your queue. But it will give guidance on how to install and use the new software.
From hereon-in it’s all Lisp. I’m getting more fluent in Racket. I do have a nagging feeling that maybe I ought to convert to Clojure-like dialect. Which would allow me to use the same code in the browser, on a node server or even compiled using Pixie-Lang. I’m still thinking about this and will make a couple of small experiments in the near future and I’ll pay attention … will other people pick up the Racket code? Will I find myself with a new compelling reason to have MTC back in the browser? Is it worth moving to Rackjure to smooth a potential future port? Right now the code is still trivially small enough that I could port relatively quickly. But I’m watching.
Huh?!? I actually had no idea. Following up that last Jonathan Edwards video I discovered that SAP are funding a PARC-style research lab run by Alan Kay (!!!!!), who has hired Vi Hart, Bret Victor and Edwards among others, to go and do their crazy software art, reinvention of programming stuff.
And here’s the GitHub repository. Which is a pretty damned awesome move.
Jonathan Edwards has moved to Alan Kay’s research institute. And is working on, Transcript, a new system that makes it easy to script social apps on mobiles.
What is it that makes the web so great?
Linking. What is it that silos will not do.
… Here’s the problem. Linking hasn’t gotten an upgrade in many years.That’s not to say an upgrade isn’t possible, it is. But it takes two (or more) to make it happen. I can’t link to anything in a new way if it isn’t ready to be linked to in that way. And what we need for that to happen is collaboration.
Very good. So what kinds of upgrade to the linking standards / practices?