Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sdesol
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
55 ms
·
601.
▲
by
sdesol
9y ago
Can somebody from GitHub comment on this? > Apps cannot actively persuade users away from GitHub. This is listed as requirement from the "Requirements for listing an app on GitHub Marketplace" page. Is this saying your app shou
602.
▲
by
sdesol
9y ago
@sqs Since you are posting in here, I figure I would ask. Are there plans to provide an API for Sourcegraph in the near future? My product is more focused on code history discovery and I was thinking it would be nice to be able to quickly
603.
▲
by
sdesol
9y ago
So I ran a few tests by indexing https://github.com/Microsoft/vscode and these were the results DO - $10 | Vultr - $5 | Vultr - $10 ----------------------------------- 00:38:59 | 00:31:58 | 00:29:43
604.
▲
by
sdesol
9y ago
I did a blog post last year that compared DigitalOcean, Vultr, and my 7 year old laptop for my Git indexing engine. Vultr performed better than DigitalOcean in all my tests. You can find the numbers at https://gitsense.com/
605.
▲
by
sdesol
10y ago
I suspect the next big thing will be to incorporate machine learning into the software development life cycle. - Issue comments that are no longer relevant, should be collapsed by default. - You should be able to get a "too long;
606.
▲
by
sdesol
10y ago
I don't think people fully realize how truly difficult it is produce next generation dev tools. What GitLab is doing makes perfect business sense, since it's an order of a magnitude easier to create business focused solutions, co
607.
▲
by
sdesol
10y ago
For those that don't follow Git hosting, it may not be obvious, but GitHub's mind share, is truly massive. If you want to compete head to head with GitHub, you'll basically, have to wait for them to REALLY screw up. If you w
608.
▲
by
sdesol
10y ago
From what I've read so far, I get the impression, Gitter was purchased solely for marketing value. And in a lot of ways, is quite ingenious. I would suspect, 80% if not more of the discussions that occurs on Gitter, revolves around re
609.
▲
by
sdesol
10y ago
> The thing is there's no reason for a person to hold onto Gitlab This is the one area, I'm quite interested in seeing how things play out, from a human resources point of view. Since GitLab is so transparent, it'll be in
610.
▲
by
sdesol
10y ago
I've been following both projects with quite some interest and it looks like gogs has become much more active, now a days. Here's a quick break down on both projects: 3 months of commits activity: https://gitsense.com&
611.
▲
by
sdesol
10y ago
I've been studying the SCM war with great interest and I like to think of myself, as an impartial observer, from a Git hosting point of view. Since my product is built around Git and not Git hosting, it doesn't really matter to m
612.
▲
by
sdesol
10y ago
> 1st party == 3rd party This was actually the first thing that I actually noticed about Visual Studio Team Services, when I first looked at integrating my search and code analytics engine with VSTS. It was quite apparent that they want
613.
▲
by
sdesol
10y ago
I was planning on responding to the person that had replied, but their comment has since been removed, and because I can't edit my post, I'll add some insight, as to why I used ClearCase as an example. For those who have never wor
614.
▲
by
sdesol
10y ago
I did a quick comparison of Microsoft's fork and it appears they have done quite a bit with it. Microsoft's fork contains 67,522 commits. The official Git repo contains 45,810. It appears the bulk of the work started in 2010, wi
615.
▲
by
sdesol
10y ago
I believe this, pretty much summed up why > that's where the OSS community is It's also not just the community, but GitHub provides significantly better integration support, than GitLab. Since GitHub has such a robust API, it&
616.
▲
by
sdesol
10y ago
If they get this right, this can be MASSIVE for Microsoft in Enterprise. ClearCase was the reason why IBM was able to charge $1000+ per developer license fees. ClearCase did what a lot of Enterprise companies needed at the time, and most i
617.
▲
by
sdesol
10y ago
The heatmaps and the graphs in general, or more to help you orient yourself, when having to deal with a lot of information. They make it very easy to view activity across multiple files, branches and repos at once. For me personally, I main
618.
▲
by
sdesol
10y ago
> you can't really pinpoint any other one Yeah the heatmap only really shines when it's sparse, as the noise can be too much. The heatmap is intended to be used as a secondary visual aid. What I normally recommend, is for peo
619.
▲
by
sdesol
10y ago
> or any other commit heatmap for that matter The problem with heatmaps and how they are currently used by popular tools, is they only provide novelty metrics. That is, metrics that are interesting to look at and nothing more. Commit he
620.
▲
by
sdesol
10y ago
I think this is changing at a pretty fast pace ... well for Gitea anyways. It also looks like Gitea is lighting a fire under Gogs, as they appear to be iterating at a faster pace as well. Here's a very quick breakdown of what's
621.
▲
Ask HN: Open source projects on GitHub or GitLab that uses submodules
1 points
by
sdesol
10y ago
|
0 comments
622.
▲
Seamlessly add more powerful search to GitHub and GitLab
(gitsense.com)
1 points
by
sdesol
10y ago
|
0 comments
623.
▲
by
sdesol
10y ago
Well this is an apple and orange thing. With BigQuery, they deal with data dumps, while GitHub deals with constant streams of new data. However I do agree with the "What took so long?" sediment. This is something that should have
624.
▲
It looks like GitHub now supports commits search
(github.com)
4 points
by
sdesol
10y ago
|
0 comments
625.
▲
by
sdesol
10y ago
Thanks for the info. So if you look at the vendor diffs, it accounts for 1,479 out of 2,062 diffs. https://gitsense.com/gogs-gitea/gitea-vendor.png So the difference isn't as drastic as it appears.
626.
▲
by
sdesol
10y ago
They compete in the mindshare sense. If a company is determined to treat Git hosting as commodity product, they are going to look at gitlab, gogs/gitea, gitbucket, and a bunch of other solutions. As you point out, you either go with f
627.
▲
by
sdesol
10y ago
The number of files didn't grow by a factor of 22. The screenshot shows how many files were modified in that time frame. In the case of the screenshot, it showed what happened in the last 3 months. This is what was modified in the l
628.
▲
by
sdesol
10y ago
I did a quick analysis of the two projects and it looks like the changes between them are quite massive. Here's the overall breakdown. Graph of commits over the last year: https://gitsense.com/gogs-gitea/year.png
629.
▲
by
sdesol
10y ago
I am not saying it is a golden goose. I am saying it has potential to be. If he wants to work at his own pace, then all the power to him but this path most likey wont lead to anything but a hobby project. He can't expect others to n
630.
▲
by
sdesol
10y ago
> Not all PRs have to be merged on your schedule Considering how fast GitLab is moving, if Gogs/Gitea wants to remain relevant, they really have to move at a much faster pace than they use to. Judging by Unknwon's comment in t
More ›