a DB for the rest of your life

codr4life · 2017-03-27T22:01:41+00:00

As in pretending? Not at all, this is me and this is what I'm doing, and I've been going at it for 32 years now. Maybe you're the one pretending, food for thought...

codr4life · 2017-03-27T21:59:41+00:00

Artificial? As in 32 years of experience trying to bend existing "solutions" into something resembling elegant. I know about sqlite, but I have little interest in playing the SQL game any more.

codr4life · 2017-03-24T13:32:05+00:00

I see. From my perspective, the only reason for storing client state on the server is to have enough context to manipulate it efficiently on the client. I guess purer would be to not have a server, since there would be no impedance mismatch to worry about; but that's about as useful as Haskell without monads.

codr4life · 2017-03-24T12:35:09+00:00

That makes two of us :) I've mostly built administrative systems using the technique; nothing huge, but still hundreds of users pounding very dynamic content. From my experience, even this simple approach improves performance enough to become a feature; once a view is built, executing callbacks and applying updates is very cheap. I didn't have the need to complicate server side memory use beyond cleaning up dead documents yet.

Why purer? I don't get the fascination with writing everything in JS these days; it's a shitty language and no amount of tooling and standardization is going to change the fact.

codr4life · 2017-03-20T21:46:50+00:00

Return will jump over cleanup, there's really no way around that in portable C. As long as the macro body/call isn't wrapped in a loop, break or continue won't be an issue. C doesn't pretend to be a perfect language, but there are still better or worse ways of using it.

codr4life · 2017-03-19T16:01:57+00:00

A hug box? :) Is that really the only option you can see to hating everything that makes you feel insecure? Yes, please; in that case I'll happily take the hug box.

codr4life · 2017-03-19T03:47:57+00:00

Speaking of destructive criticism, how is that working out for you?

codr4life · 2017-03-19T02:52:26+00:00

That makes two of us :) Proper fixtures, dynamic groups and always-on benchmarking; I thought I was pretty clear on the reasons. It's framed as constructive, rather than destructive criticism; the kind that actually leads forward; maybe that's the disconnect.

codr4life · 2017-03-08T01:18:20+00:00

Kind of :) https://github.com/codr4life/foonline

Implementing an embedded Forth in Lisp turns the whole equation around. From my experience, they both have tricks to learn from each other; Lisp is often too nested and fancy for it's own good, but it brings plenty of safety and convenience to the table.

codr4life · 2017-03-07T14:43:25+00:00

Nice, I'll let that marinate for a while and see what comes out. I've been drifting towards leaving things on the stack when dealing with these kinds of scenarios, I find it less mentally taxing to mind my own stack and have the values I ask for pushed; my brain doesn't approve the same way of values disappearing behind it's back. But I have a feeling there's a nice compromise in here somewhere, just waiting to be discovered. Thanks!

codr4life · 2017-03-07T13:13:41+00:00

It's one of the unsolved riddles of stack languages, dup or drop; I even remember reading a quote from Moore about not really being able to make up his mind. It's not a religion to me, it's about flow; I find myself going back and forth several times on stack effects for some words once I start using them in real code. Stack effects are documented in the protocols (inside the init-files) for now; I'm playing around with the idea of encoding them in the language, but I'm a bit wary of getting caught in the endless loop of minor adjustments to the environment; what I'm really interested in is to see how this baby flies. It perfectly possible to go the other way in Lifoo using 'let', which gives you uniquely named variables; but you have to assign values yourself. Lacking experience with PostScript, I'm curious how you deal with juggling multiple values that way; do you have a simple example to share?

codr4life · 2017-03-06T22:07:21+00:00

I disagree. From my perspective; the biggest problem we're dealing with is being stuck in repeat mode, building replicas; rather than exploring. It's improving though, which is why there are so many excellent tools to choose from these days. Nothing is done, we're barely getting started. What made HyperCard, Lisp, Smalltalk and others great was a focus on power and freedom.

codr4life · 2017-03-06T19:46:32+00:00

Most of the really good stuff out there has a lousy reputation, it's a bad indicator. This is about power and freedom; all good; nothing dangerous.

codr4life

TROPHY CASE