11–20 of 43 posts
I don't really understand how a well funded startup like this, with something that is relatively trivial, yet critical to their product, decided to just shove it into GitHub.
They probably should have had a backup location from day 2 though, I agree. If nothing else, in case of a GitHub outage.
I don't really understand how a well funded startup like this, with something that is relatively trivial, yet critical to their product, decided to just shove it into GitHub.
Most folks seem fine with it, at least it still lives on like normal as far as I know. I think engineering principles flew out the window a long time ago, all people care about now is shipping as fast as they possibly can.
I don't really understand how a well funded startup like this, with something that is relatively trivial, yet critical to their product, decided to just shove it into GitHub.
Their product is the creation of Git repos. Putting it on the platform their customers want to use makes a lot of sense. They probably should have had a backup location from day 2 though, I agree. If nothing else, in case of a GitHub outage.
Maybe I read the landing page very wrong, but it seems to be a "app building toolkit" of some sorts? Not just "creation of git repos".
They could have made the GitHub repository creation happen when the user does some action, instead of at the stage of "create app" which probably every single user does at least once, even people with no intention of actually building apps.
Or better yet, offer their own viewer for Git repositories they themselves host. It's not overly difficult, and the `git` CLI tools even ship with a web UI you can take inspiration from.
I don't really understand how a well funded startup like this, with something that is relatively trivial, yet critical to their product, decided to just shove it into GitHub.
Their product is the creation of Git repos. Putting it on the platform their customers want to use makes a lot of sense. They probably should have had a backup location from day 2 though, I agree. If nothing else, in case of a GitHub outage.
Many mistakes were made by Lovable that they could be berated for but on a more positive note, there is a lesson for us all: if you're doing something that you're worried about being problematic (e.g: creating a large volume of GitHub repositories) reaching out is a good thing but it is important to understand who you are reaching out to. GitHub is a huge organization, front-line support is not likely to have intimat…
Getting a flag like this hardly “overloaded” anything. Alerts for these things usually trigger well below any actual risk to the system.
Earlier quoted context omitted.
Their product is the creation of Git repos. Putting it on the platform their customers want to use makes a lot of sense. They probably should have had a backup location from day 2 though, I agree. If nothing else, in case of a GitHub outage.
> Their product is the creation of Git repos. Putting it on the platform their customers want to use makes a lot of sense. Maybe I read the landing page very wrong, but it seems to be a "app building toolkit" of some sorts? Not just "creation of git repos". They could have made the GitHub repository creation happen when the user does some action, instead of at the stage of "create app" which probably every single use…
https://news.ycombinator.com/item?id=42646297
And now this post with an exaggerated title. Seems like they're shilling and trying to make Lovable sound like a product with such huge traction that it "even brought Github down". They keep making outlandish claims on social media too, like reaching $4m ARR in 5 weeks etc. This company is very suspicious.