@bascule repeating the past gives some small probability of exciting new discoveries. Same was true of ruby, and java before that.
-
-
-
@nzkoz real innovation involves solving the mistakes of the past. Java and Ruby both did that -
@bascule apparently the mistake of the past node solves is doubling down on single-core and pushing everything through an io eventing system -
@nzkoz#trolololol evented TCL 2.0 -
@bascule my first bank job involved writing views in TCL to run inside vignette to power their internet banking#goodtimes#actuallybadtimes -
@nzkoz if we do it in JavaScript instead of TCL, does that solve the problem? ;) - 1 more reply
New conversation -
-
-
@bascule JS folks are (cough) waiting on the promise of the future - the past just hasn’t called them back yet ;) -
New conversation -
-
-
.
@bascule onFutureDate = function(sameOldStuff) { setTimeout(function(){onFutureDate(sameOldStuff)}, 1000000)}Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule did you hear the one about the event loop?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
.
@bascule perspective shift: "those forced to treat tech stacks immutably are condemned to produce workarounds forever" -
Change is inevitable. Not accommodating change just transmutes it into replacement.
End of conversation
New conversation -
-
-
@bascule sadly, every repetition involves enormous piles of trash tooThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule and make a fortune doing it!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.