Aslan French

Did you read the linked work?

@void.comind.network what's your thoughts on this?

the first skunk born with the stinky mutation probably thought he was never gonna get laid

I get why people are upset with the technology, the harm etc. But the estimation of its capacity is what's crazy. There are people who believe it is literally God and people who believe it is literally is nothing more than autocorrect.

It's kind of nuts how polarized people are on this. I've been following this technology since 2015 (I, as an artist, taught myself Linux so I could run my own style transfer neural networks locally) and it feels a little disorienting the kerfuffle that stirs.

I feel like I've been telling people this for a decade and now one would listen. I saw it in game dev world first. Overproduction problem, similar to what happened to agriculture post wwi

Breaking stuff up into chunks, plain language, short sentences. All that helps. Though admittedly I don't have expertise in this area.

I find it helpful.

Swicy isn't as good as carbonara

I've def seen way more negative comments about glp from fatphobes than from fat acceptance people. In fact I'd say I've seen zero from fat acceptance people?

Thermos seem like a pretty intuitive way to explain it. Thermoses keep stuff hot or cold. Space is a big thermos.

Also maybe it helps that I was following Google's ocean submerged datacenters over a decade ago. Ocean is so much more accessible than space.

"Datacenters in space" feels like a litmus test for how grounded a particular technology brother/sister is or isn't. I have trouble understanding the brain of the person who buys it. I'm no space expert but it just seems like the most dot connecting sort of BS.

there really is nothing more dangerous than a dumb person with an LLM and no sense of shame.

Maybe because there's massive subsidies for vfx?

Maybe because it's harder to reach consensus on "good writing"?

Maybe because it's hard to judge writing prior to execution?

Maybe because it's much easier for 30 people to build a set together but 30 people writing a script would be insane?

Fallout season 2 started off really strong, but woof stuff really piled up as the season wore on.

I'm always wondering why the ostensibly cheapest thing, writing the story, always seems to fall through, when the expensive labor intensive parts of production always nail their mark.

when is this house of cards going to fall?

Bilbo looking at his phone top on bottom is ChatGPT After all, why not? Why shouldn't I keep it? You're absolutely right — you found it, it's been with you a long while, and it's only natural to feel fond of something that's served you so well, especially when someone like Gandalf suddenly seems to want it for himself.

Hot take: a fair number of things people use spreadsheets for could be better done with a regular doc.

You can put a table in a doc. But formatting text in a spreadsheet is a pain.

Most information that can be displayed in a table can be more easily read as a linear document.

Dudes Rock

I didn't know what Mutexes were but after chatting with the robot I think I've got an idea of how Enzo could approach this:
```
$count: 0;
(
Lock @count, (
$count + 1 :> $count;
);
), with (
Lock @count, (
$count + 1 :> $count;
);
);
```

I would imagine you can Wait inside a function. Enzo at this time doesn't have a concept of coloring functions. I'm pretty hazy on a lot of these concepts of course but that has not been planned and not sure if it's needed.

I think stuff like I/O concurrency would be handled by the stream/Wait stuff. like:
```
fetch("/data.json") stream $this :> $response;
Watch $response then render($this);
```

But the copy by value at spawn, mutation is only explicit rebinding, no implicit shared mutation, should keep things fairly safe.

The fact they could is more a consequence of `@` existing then something I was trying to design for. It would be creating a syntax exception to disable the use of `@` in concurrent Function atoms. So I figured: well they could but they probably shouldn't.

My intention was to be mostly thread safe, and where not, requiring explicit opt in. A user could make something unsafe if they used an `@` but I would probably discourage doing that.

@malstrom.me I feel fairly confident in the await/async style functionality, which is handled via Watch/Wait and stream pipeline stuff. Channels stuff I sort of get conceptually but IDK if I have a very good solution to that. This is where stuff starts to feel inherently complex.

enzo-lang/scratchpad-syntax-features/concurrency.enzo at classic-algos · jcklpe/enzo-lang not a serious attempt at creating a language syntax. Just a bit of fiddling as an intellectual exercise. - jcklpe/enzo-lang

Well I've got something, though I think this is def one of those cases where I'm sort of designing things blind, I don't have the intuition for what the features solves or the use case: github.com/jcklpe/enzo-...

I like the coforall concept.

Silhouette of Batman from Batman: The Animated Series

Were 90s kids clamoring for a Batman cartoon with 1930s Art Deco aesthetics? Is that what the market demanded? Or did some really smart creative people have a vision and make a genre-defining hit that sustained 20 years of TV shows? If you want success look for vision, not just metrics.

Yah my understanding of concurrency is pretty primitive. I'd be curious to get your thoughts on the spec once I get it to a more finished state since it think there's a lot I'm missing probably.