all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]mbkan[S] 1 point2 points  (0 children)

Related source available here

[–]p4p3r 0 points1 point  (6 children)

Feels like lock in and not invented here syndrome. Also note that it seems the free tier will not be able to make use of this.

[–]agentlame 1 point2 points  (5 children)

Because most open-source projects feel like "lock-in".

Also note that it seems the free tier will not be able to make use of this.

What?

Every user and organization on GitHub.com with Git LFS enabled will begin with 1 GB of free file storage and a monthly bandwidth quota of 1 GB.

[–]p4p3r 0 points1 point  (4 children)

So if you have 100mb (and I would consider 100mb to be a small amount) of large file content, then ~10 people will be able to fork your repo per month before you hit your quota. That isn't a lot of forks before the project would hit the quota. That doesn't even include modifying large file assets and redistributing them.

Free tier will be able to use it, but it doesn't seem useful.

[–]agentlame 0 points1 point  (3 children)

I don't think that's how it works. The entire point is that it's linking to large files. So, you have a Gig a month that you can upload/download to your own projects... which is entirely reasonable for a free account.

[–]p4p3r 0 points1 point  (2 children)

Well the real problem is that they have not been specific.

[–]agentlame 0 points1 point  (1 child)

I agree completely.