Git VS scalar

Boy, I can't find this either (but also, the kernel mailing list is _really_ difficult to search). I really remember Linus saying something like "it's not a real SCM, but maybe someone could build one on top of it someday" or something like that, but I cannot figure out how to find that.

You _can_ see, though, that in his first README, he refers to what he's building as not a "real SCM":

https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23...

Here is the direct link, as HN somehow removes the query string: https://github.com/git/git/commits?author=peff&since=2023-10...

Yes, but you are referring to standalone scripts, not functions defined within a Bash script.

Compare for example the following helper code used for git command completion inside Bash and inside PowerShell.

Bash: https://github.com/git/git/blob/master/contrib/completion/gi...

`master` is also used as the default name for the default branch in newly created repositories. See option `--initial-branch` of `git init` and config variable `init.defaultBranch` [2] to override. Git for Windows, for example, allows setting the config option in its installer.

Source code:

- for merge commit formatting: https://github.com/git/git/blob/2108fe4a1976f95821e13503fd33...

> which branch on a remote is considered the default

That part is actually covered by "the default branch in newly created repositories". There are two different places where its done:

- This is the one you probably mean: [1]

- This is an obscure feature: [2]. A Stack Overflow comment [3] calls it "one of the abandoned experiments that were being done before the concept of a remote was invented".

Both of the places use function git_default_branch_name from refs.c [4], which uses config variable `init.defaultBranch` I've mentioned above.

[1] https://github.com/git/git/blob/v2.43.0/remote.c#L2380-L2383

[2] https://github.com/git/git/blob/v2.43.0/remote.c#L328-L338

[3] https://stackoverflow.com/a/54132016/1083697

[4] https://github.com/git/git/blob/v2.43.0/refs.c#L671-L705

There's a comment about that here: https://github.com/git/git/blob/bc5204569f7db44d22477485afd5...

    When writing or updating patterns, assume that the contents these

You know another project with much of its source files in the top-level directory? https://github.com/git/git

Scalar - alternative to redoc that has been frantically building out the premium features that redoc's parent company charges absorbent prices for.

+ a link to our repo: https://github.com/scalar/scalar

Hey HN this story is from 2018 but I always wanted to share it.

I had just launched my first SaaS, it was 100% funded by my student loans (I don't recommend anyone do this ). I was extremely lucky that the launch went viral on Hacker News, Producthunt, and Twitter which resulted in 4-6 paying customers a day.

After about a month the paying customers were dwindling to around 2-3 a day and I needed to find a cost effective way to bring this back up. My SaaS was a website builder called Launchaco and it was impossibly expensive to acquire customers via paid ads. I landed on making a free / open-sourced AI logo builder as a loss leader when I realized a lot of our users were paying for “AI logo makers”.

At the time “AI Logo makers“ were quite literally just vertically aligning icons + fonts with fake loading screens saying "generating logos with AI", and then charging between $20 - $250 for the resulting logos. From the get-go the business model of these logo makers seemed sketchy at best, but when I started to dig into how they were licensing their fonts that’s when alarm bells really started to go off.

For those unfamiliar with font licensing, the short of it is that not all fonts are licensed to use as logos, and a handful of our competitors were ignoring this (some were profiting 100’s of thousands from fonts they didn’t have a license to distribute). I made a massive spreadsheet of all the biggest logo builders, dug into their source code to see what fonts they were using and manually checked if they were properly licensed. The result was hundreds of improperly licensed fonts across several very popular logo builder tools.

Fast forward 2 months to the launch day of our logo builder, I sent emails to about 100 different font foundries and independent typographers showing them how these logo builders were abusing their fonts.

Not coincidentally some of these companies temporarily shut down for a couple months after I sent those emails and some are still being sued to this day. All the fonts used for Launchaco’s AI Logo Maker were creative commons and we attributed the author per logo downloaded, we also open-sourced the brain behind our AI Logo Maker; we were excited to ship an Open-Core product for the first time & it was well received!

Post launch- Launchaco was getting a dozen or so paying customers a day and eventually was acquired by Namecheap. I recently left and now am working on a free / open source api docs tool which you can check out here: https://github.com/scalar/scalar :)

> working on a free / open source api docs tool, https://github.com/scalar/scalar

> scalar.com

damn son, that namecheap paycheck must have been a pretty penny.

You could take the OpenAPI json generated from this project and feed it to https://docs.scalar.com/swagger-editor which generates boilerplate in several formats, including Python

hey! co-founder here, appreciate your comment.

Ah that's great feedback!

As for the rendering of the schemas, we have a pull request in draft from this morning! hopefully will be done ASAP

https://github.com/scalar/scalar/pull/244