krisajenkins

Absolutely!

That article misses the #1 reason to use stored procedures - putting the code right by the data can be a massive performance boost. Like, orders of magnitude faster than travelling over the network.

That's a very fair question, and it got me thinking. So I wrote a full post answering it. But the short answer is, as long as you don't have to twist your architecture in knots to get high performance, then yes it's worth it. A system that can scale up, can also scale fast & cheap.

https://spacetimedb.com/blog/okay-but-does-it-need-to-scale

I don't think they have pivoted. They're just realising there's nothing game-specific about the database they built for BitCraft, and they're widening the scope.

The direction is more games-to-general-purpose than games-to-AI.

I totally agree. The thing that's drawing me to Spacetime is that it blends the processing model of actors and the data model of relational databases really neatly.

Data comes in, do something with it, store your state in a principled way, repeat. Add in subscriptions to data and it becomes reactive. Simple.

A coding video that walks you through building a Neovim plugin that can do some interesting Docker actions.

We ran out of good names years ago. Then Java came along and we used up all the words beginning with J. Then the dotcom years scooped up all the domain names and all the twsted up wrds like flickr. Then npm took all the variationsofpunctuation, varations-of-punctuation and variations_of_punctuation. Now there are no virgin words left in the English speaking world.

TBH, I'm amazed that Proton wasn't already taken.

An in-depth interview about Zig with Loris Cro of the Zig Foundation.

An interview with the creator of Gren, a new functional, fullstack programming language that branches off from Elm.

This is marvellous. IMO Functional has always been a bigger deal than Reactive. Great to see more of that pursuit of simplicity paying off.

Leading questions, I'm afraid. Yes, equality is still broken, maps are broken (and in new & interesting ways in EMCAScript 6), and the language is occasionally whitespace-sensitive.

JavaScript was hastily designed, has never recovered, and shows no sign of ever fixing the fundamental problems. :-(

Is equality still broken? Are maps still broken? Is it still a sporadically whitespace-sensitive language?

Writing JavaScript and feeling you're surrounded by errors is pretty normal. It's a hastily-designed language. There's no getting away from the fact that everything is going to feel a little bit fragile. Just accept it and don't expect perfection.

"locally stateful, globally pure-functional"

Can you expand on that, please? Because it seems to me that state fulness propagates up through the system. I can't imagine a system that was pure in the large but side-effecting in the small. I'd be interested to hear how that works...

Anyone know how the compilation times compare with regular Scala?

Love it. This is brilliant fun.

You're assuming that all the visits are evenly distributed over the day. I doubt that assumption will hold...

There's a typo on the first point. Instead of, "Java is an OOP programming language," it should read, "Java is an object-oriented OOP programming language."

That aside, it's a wonderfully enlightening document clearly written by someone well-versed in the issues. :-D

+1. Evil is great. I think it's made Emacs my favourite implementation of Vi yet.

FYC: I presented a History of Lisp talk at last year's ClojureX: http://skillsmatter.com/podcast/scala/a-walking-tour-of-cloj...

McCarthy himself said of his pre-Lisp research:

"To use functions as arguments, one needs a notation for functions, and it seemed natural to use the -notation of Church (1941). I didn't understand the rest of his book, so I wasn't tempted to try to implement his more general mechanism for defining functions. Church used higher order functionals instead of using conditional expressions. Conditional expressions are much more readily implemented on computers." - History of Lisp: http://goo.gl/EDuhl

I've always liked the fact the he did so much with a book he didn't understand the whole of. :-)

Amen. Kicking a customer should be the absolute last resort, not the first step.