yumaikas

One big difference between Nova and -most- logic languages is that "forgetting" things is a normal part of operation. Nova is also forward chaining, rather than backtracking.

The end result ends up with Nova programs being something closer to an interpreter in a lot of cases, and writing inputs for said interpreter.

So, Nova doesn't do as much on your behalf as Prolog does, deliberately trying to be easier to reason about, and to have more predictable performance characteristics.

Nova's execution model is a lot friendlier to implement vs Prolog, for one.

One big reason reach for Nova are when I have something -very- state-machine shaped. It is quite good at that.

I'll try to come back later with more explanations

I don't quite have proper reactive/two-way data binds worked out, but grab/patch seem pretty nice as these things go. Also, the way this uses templates makes it very easy to move parts of the template around.

It's also largely injection safe because it's using innerText or value unless told otherwise.

Remote: yes

Willing to relocate: No

Technologies: C#, ASP.NET, React, Typescript, JavaScript, HTML, CSS, Tailwind, Godot, Lua, Elixir, Powershell, git, Golang

Résumé/CV: https://junglecoder.com/downloads/Resume/AndrewOwenFullstack...

email: yumaikas94@gmail.com

The thing about Erlang behaviors is that they rely on several other pieces of Erlang to work well.

One big one is being able to be notified when another process goes down, or is aborted.

The other big one is being able to reason about state in the face of such failure.

Erlang decided to go with immutable data structures, shared nothing processes, and the OTP behaviors generally expect you to decompose the behavior of the various bits into functions that represent a single atomic step.

The more of those properties that you don't share with Erlang, the harder it will be to adopt OTP style semantics in your system.

What about blockchains would make them an effective stand-in for building trust over time? One is a ledger, the other is an interpersonal relationship, and the two really are not the same.

If I'm going to take a risk, I'd rather take a risk where there's some human expectation of managing bumps in the road, and which has some means of redress if sufficient malice is involved, instead of one where a smart contract bug means that I've lost a lot of money.

It's worth calling out that this is not an absolute value. It's definitely the predominant one, but businesses can and do exist where the core motive is to make sure that everyone working for the company shares in the success of the company equally.

And I think it is past time to be challenging that status quo

It also partly inspired my first efforts at building a scientific calculator (which would never be quite finished).

I definitely recommend it for folks who want to build context on the lower levels of computers, as a start into understanding CPUs, binary/hex, and other parts of how we tricked sand into thinking with lighting.

Of other note is that Erlang seems to enable folks that use it to punch above their weight class when it comes to running services internally and such.

Serverless is far from the only valid way to run things these days.

IDK, an EDM Knife sounds like a cool idea.

Double check against ADHD.

If you have it, it changes how you approach all of the advice you might get, because it means your brain is literally physically different in how it manager attention.

If you don't, that's also valuable intel.

Either way, you'll also want to learn what emotions are in play with your new project cycles. Emotions tend to indicate needs, if indirectly, and if whatever need is driving all of the new projects is not met in some way, it'll continue to frustrate attempts to focus on one project. This is because starting a new project is a well-worn path for you at this point. That goes triple of ADHD or other neurophysical forces are in play.

Like, Commander Keen and the other of those games are the same amount of effort that might go in to a particularly well staffed month-long game jam today, just in terms of assets and total needed code. CV-11s video on Quake has a section covering that transition from mostly 2D to mostly 3D. It caught a lot folks off guard.

Godot does take a little bit to learn, but it is quite rewarding.

There are a number of larger side projects, game and no, that I've either completed or abandoned over the years, and, like you said, scoping down has been a primary way to help actually get them done.

But, I've also just now found a time slot to work on something consistently in, which has made a big difference.

Many folks don't account for how much "project management" is a key skill in efforts like this.

And, I'd argue that if you want to consider indie-level gamedev efforts, it makes sense to spend 6 months as a hobbyist first, to kinda feel out the territory.

And, for me, if someone interviewed and showed off a game project, I know they've dealt with lots of mutable state, and the challenges therein, which is worth something.

And ridicule is part of the point of text (not subtext) of the essay. Dan is making an emotional argument as much as he's making a logical one, because a lot of people will hear the emotional one where the logical one would just bounce off. Making something harmful actually seem uncool is a valid tactic, IMO.

Like, calling out Vitalik as a butthurt Warlock main is an attempt to make his origin story around the EVM seem to have a pathetic origin. Instead of applying himself to getting better at the new warlock meta, he went off and created a thing that has enabled a lot of real economic harm.

And pointing out the connection to Peter Thiel is as much about pointing out the involvement of big money in cryptocurrency as any specific character of Vitalik.

And it's not like Vitalik hasn't had a lot of chances to go "damn, the EVM is being used for a lot of harm. Maybe it wasn't worth it?"

Or maybe he has, and I (and Dan, because I think he'd have brought that up) have missed it?

Might I ask what you built it with?

I've found that I like Fennel (and Janet as well, both created by the same author, though they have different maintainers) quite a bit. Turns out that having simple semantics and a very regular syntax makes for a language that makes writing basic code feel nice.

That being said, one would hope that Youtube would have better user segementation, but I can't imagine that is an easy problem.

It's also recommended by Troy Hunt, who has a reputation at stake in all of this, since he runs stuff like https://haveibeenpwned.com