Except all of the ai created games posted to the various subreddits are awful. No one likes them, no one plays them. The ones that make it to steam end up getting abandoned when the devs hit a performance wall.

Game development just isn’t something AI can do well. Good games are not just recreations of existing titles.

>Except all of the ai created games posted to the various subreddits are awful. No one likes them, no one plays them.

As with anything else, 95% of it will always be crap. Taste is now the great differentiator.

Or the selfhosted subreddit.

The fake product scammers are going to absolutely love people like you. Glad it worked out for you but that’s putting a lot of blind trust in it.

Home assistant automations?

I read this as the aspirational dream of computers actually doing what you want. Yes, you can absolutely spend a bunch of time to build out the personal automation that will proactively inform you of relevant events. Yet, that is likely to be a lot of finicky messing around that may be pretty fragile and dependent upon N APIs staying fixed.

And this sounds like something you absolutely wouldn’t want an ai agent trying to figure out.

I get the endless captcha with a Southern California ip. Something emus either very broken or malicious.

This is just an advertisement for their service.

In my 20 years in this field I can easily count on one hand the times a diagram like this has been useful. I’ve seen more cases where they were clearly created to satisfy some exec that wanted to see it and never updated again.

If you are doing any architectural work, whether at the software or infrastructire level, I fail to see how you can deal without diagrams to 1/ understand interactions between all system components 2/ make your changes understood and validated by relevant people.

Granted I speak about real, useful, technical diagrams, whose purpose is to convey useful information and highlight data flows. Not marketing diagrams you may find on marketing presentations, but this is not what this discussion is about.

Chasing perfect diagrams is usually an exercise in self-deception, since the second the infra changes, whatever picture you drew is wrong. The trickier part is when the diagram becomes canon inside the org and nobody notices it diverged from reality years ago, so tribal knowledge beats the official chart every time.

Odd thing is, the only diagrams that seem to matter end up on whiteboards or living docs if anyone's actually building things. Few things age faster than polished Visio junk made for complaince audits and VP vanity.

In my company, we generate diagrams from data coming from external referencials that ARE source of truth, by process. Not the perfect solution, but much better than representations of a reality that has already moved miles ahead.

This is for the icons in the drop-down menus, not the icons in the menu bar.

This is not what the article is about though?

It could have used a screen shot.

Read Tonsky for that. https://tonsky.me/blog/tahoe-icons/ a disgrace. https://tonsky.me/blog/tahoe-icons/writing_direction@2x.webp...

This is disgusting. Like, I'm using macOS but just seeing this standalone makes me cringe.

Seems a bit deceptive to say "No cloud, no subscription, runs locally" when it still needs an api.

From head of README

“ Free, open source, runs locally. No cloud, no subscription beyond a free AISStream API key.”

I mean we don’t have the vessels floating around live locally inside machine :) Gotta get the AIS messages from somewhere

And the webserver is running locally, this is not web based, that’s the no cloud part

The real issue is copilot is implemented in their apps inconsistently. Very clear there’s little cross app planning. Apples solution is global and apps and hook into it or not. And if you turn it off apps done break.