Remember desqview?

Just call me Pepperidge Farms, I loved Desqview for the time. It worked well, given what they had to work with.

I mostly remember it from BBS's - it was _the_ way to run a multi-line BBS for a while.

GEOS was pretty cool too - amazing what you can fit in 64K if use a big enough hammer :-D

more info pls.

there is not much to brag about yet :'(

About a year ago I was curious about building an ECS-based game engine with world simulations like in dwarf fortress, but obviously at much smaller scale while playing Starfield. Something cool started to materialise after tinkering so I thought why not turn it into a space-sim roguelike with a simulated living world.

I use swift because it gives me fantastic devex with all its great type inference and macros + raylib gives me cross platform input handling / rendering and window management.

C-interop setup is basically instant - you point compiler to c headers and the API becomes immediately visible on swift side

As for swift ergonomics, I particularly love that I can now write very readable code, like:

> world.addRelation(attacker, Attacks.self, target) > world.addRelation(player, Owns.self, sword)

or

> for (entity, position) in world.query(Position.self).with(Health.self, Velocity.self).without(Enemy.self) {}

This sounds cool. You mentioned Swift's macros - would you mind talking a bit how you are using them?

a lot of cool-looking stuff in my ECS is supported by Swift parameter packs; however, once you start using them a lot you find limits pretty soon.

One example: the following wouldn't compile in swift:

  func query<each T, each K>(
    _ body: ((repeat each T), (repeat each K)) -> Void
  ) { ... }

so you kinda work around it with extra type wrappers but this looks ugly - I've been using macros to hide some of the ugliness away xD

edit: the example is oversimplified just to show the point - in this example compiler can't really tell where T ends and K starts, so its logical; but I had more complex cases where a human would've been able to infer types correctly

Do you use any bindings or directly use C functions (with a modulemap) in Swift?

No bindings, I wrote a few wrappers myself to make often used functions a bit more swifty, but otherwise its pretty smooth sailing

I do this on IRC to prevent people from using characters that clients will interpret. It's not safer, but it prevents a ton of password support issues.

Sure can. I can get grants specifically to hire someone. As long as that's specified in the grant, and I can prove that's what I did with the money, there's no issue. Non-profit in this circumstance, rather than education.

Yes, absolutely.

rocket man.

If I were mailgun, I'd be okay losing Evan as a customer.

I would try to see this from Evan's perspective. Its easy to find next to useless Sales people, its harder to find a good customer. Evan is a busy guy and said please don't waste my time with a Sales call this is only for your own benefit and then got something else.

And I don't want you Sales people poking around in my SaaS setup or in my data.

> Evan is a busy guy and said please don't waste my time

Busy people don't spend hours starting internet fights. They delete spam and move on with their day.

They do for vendors that draw their ire, maybe not for your average sales email.

In the comments he posts another interaction with a sales-person. Read his second reply... I'd be happy losing him too. (As a business owner I understand how we get spam like this all the time, and I almost always ignore it if it is clearly not targeted. If someone goes out of their way to list some real reasons why they like my company though, I would try to be a little nicer)

Agreed, this is silly.