461–470 of 619 posts
Earlier quoted context omitted.
Github has had a built-in editor for almost a decade, you just had to click the Edit button in the file: https://github.blog/2011-04-26-forking-with-the-edit-button/ (the button has since changed look to a Pencil icon) This is not to disparage you, just to note that it may not have such a great effect.
You still have to fork
Earlier quoted context omitted.
Why not post the change here so someone else could contribute it? Sounds useful.
That'd be awesome! diff --git a/src/strconv/atof.go b/src/strconv/atof.go index 28ad094..49cec69 100644 --- a/src/strconv/atof.go +++ b/src/strconv/atof.go @@ -410,12 +410,12 @@ out: } // Exact powers of 10. -var float64pow10 = []float64{ +var float64pow10 = [...]float64{ 1e0, 1e1, 1e2, 1e3, 1e4, 1e5, 1e6, 1e7, 1e8, 1e9, 1e10, 1e11, 1e12, 1e13, 1e14, 1e15, 1e16, 1e17, 1e18, 1e19, 1e20, 1e21, 1e22, } -var float32pow10…
Earlier quoted context omitted.
I think that you are wrong on VS Code Remote not being open source. Here is the relevant repository: https://github.com/microsoft/vscode-remote-release . Corresponding official documentation ( https://code.visualstudio.com/docs/remote/remote-overview ) states that Visual Studio Codespaces is essentially a managed service of Visual Studio Code Remote Development. BTW, there is also an interesting alternative, the `cod…
I vaguely remember a post a while back (maybe a year ago) where they said they can't make a part of their remote technology open-source. Maybe things have changed, but I was quite sure it was something they were keeping close to them. Also thanks for pointing out the certificate issue. I was actually leaving it that way on purpose, but I guess it can reflect poorly on my product, so I should just update the landing p…
Earlier quoted context omitted.
Having APIs designed for public consumption probably helped.
My experience with azure storage didn't make me think it was "designed"...
Earlier quoted context omitted.
Hopefully the licensing requirements can be made simple as well! I recently wanted to submit a 3 character change to golang that significantly speeds up strconv.ParseFloat(), but lost interest about 2-3 minutes into reading this: https://golang.org/doc/contribute.html
That seems outside of the scope of an in-browser text editor...
To the parent poster's point, I feel if I could easily submit even a small subset of the trivial changes I have sitting around in local forks, it'd greatly improve several projects.
Must be fun for @sytse to watch these GitHub announcements every year, where they consistently release the same thing GitLab rolled out two years prior. Codespaces -> https://docs.gitlab.com/ee/user/project/web_ide/ Insights -> https://docs.gitlab.com/ee/user/project/insights/ GH Actions -> https://docs.gitlab.com/ee/ci/ etc
Gitlab is a bit of a mess though: a) Gitlab.com is ridiculously slow. Even the CEO admits they failed to invest in it. b) You can't disable features you don't need so you end up with a sidebar full of Kubernetes and Security features for a Git project dedicated to documentation. c) Staggering amount of open issues and merge requests so you feel discouraged from even raising anything since it just gets lost in the wee…
I've studied GitLab's code history for a while, and they have been moving at a very fast pace for years now. Below is a one year window (from today) into to their gitlab repo.
Some points of interest are:
1) 15k commits are merge commits.
2) The vast majority of the code churn is ruby, which is expected.
3) Based on the bus factor, a lot of files that are iterated on, have less than 10 unique contributors. And there are a handful of files that are iterated on a lot, by a lot of people.
4) A lot of the code changes are 10 lines of churn (lines added, changed, deleted) or less, which indicates incremental improvements/bug fixes/etc., as opposed to adding new functionality.
Something that I'm not doing right now, is mapping the churn, to the number of unique contributors. It would be interesting to see if there is a pattern to their churn vs number of contributors.
GitLab is definitely moving at a very fast pace, and it would be interesting to map this to their issues, but their API is extremely slow, so I've never bothered trying.
Edit: For the scatter charts, the x-axis represents the number of files. And the y-axis is number of contributors (bus factor chart) and churn size (churn chart)
Earlier quoted context omitted.
Everything about Github's PR workflow is killer to me, so to me personally the message I take away from this is that Source Hut isn't even competing with Github in the parts I care about.
If the one particular aspect I mentioned isn't for you then why even bother wasting your valuable time responding? Just go read their website instead and see if there is something for you. Maybe there is, maybe there isn't, but at least then you'd know definitively. Much better use of your time and effort. I'll even save you a few clicks: https://drewdevault.com/2018/11/15/sr.ht-general-availabilit... https://sourceh…
Earlier quoted context omitted.
My experience with azure storage didn't make me think it was "designed"...
Azure storage is definitely the black sheep. They cleaned up the VM/compute layer a few years ago with the introduction of Azure Resource Manager (ARM), but storage hasn't gotten that big an overhaul yet. And it shows. They seem to be slowly improving things under the hood though...
Earlier quoted context omitted.
Gitlab is a bit of a mess though: a) Gitlab.com is ridiculously slow. Even the CEO admits they failed to invest in it. b) You can't disable features you don't need so you end up with a sidebar full of Kubernetes and Security features for a Git project dedicated to documentation. c) Staggering amount of open issues and merge requests so you feel discouraged from even raising anything since it just gets lost in the wee…
Thank you for your feedback! Regarding performance, we've made some recent improvements (here's one example: https://gitlab.com/gitlab-org/gitlab/-/issues/30507#note_293... ), but we know we need to do more. We're actively working to improve our sitespeed ( https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7154 ), and we have several other improvements in process this quarter. Regarding disabling features and the…
Issues fall through the cracks because there's no internal health oversight, take this issue for example: https://gitlab.com/gitlab-org/gitlab/-/issues/21907 It simply ceased to exist because the original staff member left GitLab.
I've also seen community MRs with weeks of work go to waste because GL staff couldn't take proper ownership/responsibility to see them through.
I think having a "all hands" week where all work stops except for going through current GitLab.org issues, fixing labeling/priorities, adding related issues and pinging the correct leads would do WONDERS.
Sadly, if GitHub adds scoped labels and descriptions we'll be making a move over as it's the final piece of the puzzle.
I have a VPS that runs code-server and I use 'save as app' in Edge so that it captures control keys properly. It feels like it's native and using ssh tunnels it feels 99% native, and I can pick back up working on any computer.
I ended up with this set up because I have a Galaxy Book S and VS Code doesn't have an ARM build. Very excited!