its not a bad idea to use one of the GPU Terminals on linux just for claude code, it works out a bit better

What a bad name for a webmail client

That's a blunt way of saying it, but I agree with the sentiment.

Which is a shame, because this is a project that could have had potential, but a poor name goes a long way towards discouraging it being taken seriously.

Have we learned nothing from GIMP? No, no we have not.

Git?

Well you're saying that from not just an Anglo centric pov but a US pov. 'Cockly' doesn't sound particularly bad to my British ears.

But then I live not so far from Penistone, so maybe I'm just used to these kind of naming schemes.

I've got a old dead multiplayer only game I would love to try and get a basic server online for again.... ( Wulfram II will always be missed )

IPFS also has issues with large datasets, anything larger then a few TBs cases nodes to explode and indexing takes forever.

Also the lookup time for files is too slow to use it on anything user facing.

Start clicking on stuff, You'll find it :)

I was clicking around like mad, nothing happened and I gave up

That whole list is a hoot,

has_toxicity_score_above_threshold

is a interesting value, I wonder were the 0.91 was though up at

I avoid Javascript outright because async/await/promise is confusing to me. I blame it on being a PHP Programmer and likes things to run serially.

I felt the same way coming from a threaded language.

Learning the event loop, then promises, then async/await is a must. Today, you probably should throw typescript on top.

A steep learning curve just to get back to a typed language that can do things concurrently.

You do get used to it, but it is a mess of stuff.

Threads are their own steep learning curve, I think it's just hard to do two things at once.

It's easy to do two things at once when you can ask two different entities to do them for you (threads).

What's hard is thinking about how to coordinate the work they are doing for you: when to consider them done, how to ask them if they did the work successfully, what to do if they need to use the same tool at some point during the work etc.

This is ridiculous. Handling real threads is much more complicated than handling async calls and the event loop of JavaScript.

Languages with threading require learning techniques to use them safely and many, including myself, have learned how.

Even if concurrency is easier to get right on node I'd say the node ecosystem has just layered on complexity in other ways to get to something just as difficult to use overall.

Promises and async/await sugar are only the tip of the iceberg.

/r/gatekeeping

It drove me crazy too, until I needed to use Puppeteer which requires you to write async/await (there are Puppeteer implementations in other languages, but they all seem to make compromises I didn't want). Generally speaking, async/await allows you to write code that looks and feels serial. Perhaps try using one of the async libraries for PHP to wrap your mind around the concept of async/await (like https://github.com/spatie/async)

Hyperscript can help with this. https://hyperscript.org/

Makes using a bit of JavaScript relatively simple, just not much in Stack Exchange yet which means reading docs..

The biggest feature of PHP for new people to the language is in-lining

You can do stupid stuff like

<table> <?php foreach($array as $row){ ?> <tr><td><?php echo $row[0];?></td></tr> <?php } ?>

Meaning you can just inlay PHP in your raw HTML as you please, this example will reprint the <tr> and <td> for every key in $array

I am working on a MicroPHP to shove into something like a RP2040 since PHP is really just a shell script for a whole bunch of C functions... but PHP eats too much ram currently on the micros

Two low end Hetzner/OVH Boxes for redundancy should do the trick

That's why AWS charges so much for outgoing traffic.