I agree I would expect a reference. Another difference between this an AvianVisitors is the image sources. AvianVisitors is all AI generated with a consistent prompt, but OP's is using chiefly public domain images with retouching by AI as needed.

Yeah agree

I understand OP is continuing the work and improving it as he sees fit, but that in my mind is a fork and should aknowledge the initial work that sparked it.

Maybe i'm wrong tho and this is completely parallel work! Waiting for OPs reply

Hi, yeah I'm not basing any of my coding or feature-work on that project. My biggest source of inspiration is actually just a paper poster I have hanging on my wall https://www.axelthorenfeldt.com/news/wwf-verdens-naturfonds-.... I wanted to make a version of that, showing the actual birds in my garden.

I accuse you of having good taste.

A fork implies that it builds upon code from another repository. I wouldn't use the word fork to mean "inspired by". I think it takes away from the effort that the author has put in. Anyone can create a fork of a project with the click of a button.

AI-prose may be vetted, but there is no way for a reader to know that for certain as much AI-prose is not.

As such, you cannot be sure if the writing contains correct and accurate information at all, even with modern models.

> you cannot be sure if the writing contains correct and accurate information at all

how is that related to LLMs?

Due to their past, LLMs need to prove themselves as correct and accurate. Bloggers have already gone through this gauntlet and have proven to be more likely to be correct and accurate.

Neither are a guarantee.

that title might be easier to parse, but it's less poetic and less attention grabbing

The goal as a blog author should not be to grab attention and mislead readers into starting your article only to realise it's not what they expected and were interested in.

Why do you think misleading was the goal?

To me it was a clear and a very fitting title.

(But my first language is german, maybe that has some influence)

I doubt it was OP's goal. Commenter I responded to on the other hand said that the original was more 'attention grabbing' than my clarifying amendment, and that's what I said ought not be the goal.

The video game Audiosurf[1] did this, as it has to generate the game track ahead of time so that it would be playable!

[1] https://en.wikipedia.org/wiki/Audiosurf

It's a good analysis but the AI slop writing makes me not trust you've reviewed this and I'm unable to finish or subscribe. I'm sure you're a great blogger but this is holding it back!

love the concept and dont mind that ai wrote the code, but please consider rewriting the readme out of the AI style and cadence, it's a bit exhausting seeing ai writing everywhere.

Sorry I'm not sure I understand your point

Sorry, meant say that Blacksky is much more important than the metrics you point to, with more detail on that wiki.

They're the first alternative full stack, the first alternative AppView, and that is something that the author should have mentioned. However, it weakens the argument so they left it out.

"Number of contributors" has never meant impact. You wouldn't dismiss openssl or curl, ya know?

Not OP but yeah that's the one!

Yes, I only open an IDE to run a debugger when needed. The vim support isn't exhaustive and it's jarring whenever a command doesn't work.

This is about Vi though and that's certainly more rare. For me that's only used over a rare ssh with vim not available but vi present

Well it depends, on still using.

I've been mostly using emacs past 30 years ie. about the time when system memory wasn't any more constraint which while single user was about 8MB at least. But I did earn my living before that about 7 years mostly using vi as most usable editor in the system and that 8MB was luxury most of that time.

But even emacs IMHO was and is vastly superior, vi still had it niche fast small edits and especially before log based transactional filesystems. After power outage or bad brownout event system crash there was great chance you got to fixing filesystem with fsck (which did often take lot of time) and worst cases finally debugfs trying to fiddle bits that you get fsck fixing rest.

Bringing system up with old system could be tedious. Before you get system enough up single user mode and just root fs mounted you had to resort you way forward using those modest tools you had there. It was really great if vi did work, but it too required sometimes more memory than you had before swap was active. If not, then ed was your friend, ex is just vi without visual mode.

For a long time vi was also able to edit very large files. It did not require reading whole file in memory before it allowed editing as for example emacs did (or mmap's it memory later).

These days I use vi for quick edits like someone above mentioned and like it more than any later replacement (nano etc) if emacs is not there, not worth installing it for just quick change or when can't install on (embedded) or someone else's system for any reason.

Vi is often available also *bsd based appliances which I've been using like Junos, Netscalers, etc.

Yes, I agree. Everyone in ICE or supporting them.