Earlier quoted context omitted.
remote dev (and I guess now codespaces) is one of those "clear differentiators" that is actually getting me to move away from intellij and friends.
I wish IntelliJ moves in this direction so bad - would gladly pay more for this. I tried switching to VS Code for my current project yesterday and it's the best VS Code scenario out of my projects - backend RoR frontend React/TS. TypeScript aspect is amazing but the Rails part is nowhere close to RubyMine. .NET (Core) was inferior to any IDE (even Xamarin ones) last time I tried it (~6 months back). IntelliJ Rider ha…
GitHub Codespaces
391–400 of 619 posts
Re: GitHub Codespaces
#392Earlier quoted context omitted.
I'd definitely encourage everyone to git GL a try - our teams switched over from GH + Jira about a year ago, and haven't looked back. The integrated CI and project management features are a game changer.
Git it a try, pun intended? :-D
Re: GitHub Codespaces
#393Must 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
Yeah, well good luck with that one. With this feature, MS just ventured in a space where no-one can compare yet. If this ever gets popular, that's check mate right here.
Re: GitHub Codespaces
#394Earlier quoted context omitted.
When someone builds something and doesn't actually mention why, its not unreasonable to ask what the motivation was...
Have you asked them? You can hit up pretty much anyone these days on Twitter and they'll respond, if the question is reasonable. You make it sound like someone owes you a response. If this is about GitHub Actions specifically there is quite a bit of info at https://github.blog/2019-08-08-github-actions-now-supports-c... . My takeaway is that it's about packaging up Azure Pipelines in a way that GitHub users understan…
Re: GitHub Codespaces
#395Must 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…
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 Git project screen, our UX research team has heard this feedback from other users. It's fair feedback, and we're looking at how to address it.
Re: GitHub Codespaces
#396Re: GitHub Codespaces
#397This is going to be great for open source—Being able to get a fully-configured dev environment at a click of a button greatly lowers the barrier to entry. I've had a few small OS contributions where the time to set up the environment was more than the time I spent programming! I could also see this being popular with engineering teams. No futzing with the new hire's computer, just have them open a web browser and the…
Personally I have no problem with Github, as its advantage far outweigh its disadvantage.
Re: GitHub Codespaces
#398This is going to be great for open source—Being able to get a fully-configured dev environment at a click of a button greatly lowers the barrier to entry. I've had a few small OS contributions where the time to set up the environment was more than the time I spent programming! I could also see this being popular with engineering teams. No futzing with the new hire's computer, just have them open a web browser and the…
Re: GitHub Codespaces
#399Earlier quoted context omitted.
I pay for the full JetBrains subscription. While I still use vscode for typescript and rust, I use JetBrains for anything else. It's one of those no brainer purchases that pays for itself within a month. Programmers create enormous value. If you can get even small single digit percentage improvements by leveraging better tooling, it pays for itself almost right away. I estimate conservatively I produce $500,000 in va…
Many vendors do think like this when they start their offer with 'how much is your time worth'? Indeed, your tool might save me 1 hour but it's not necessarily worth the price. On complex codebases though I mostly need the IDE just to navigate code. Anything released in the past decade knows how to index some classes, jump around and do 'find usage'. I agree that tooling most definitely helps, starting with your offi…
Software tools, keyboard shortcuts, libraries, frameworks and saas software are also good targets to optimize that often don't get enough attention.
Re: GitHub Codespaces
#400Earlier quoted context omitted.
> what makes you believe that it'll be easier to contribute after you get it [setup] for free I'm flabbergasted. Like.. I don't even know where to start. You've been through an on-boarding process before right? Have you led one? Haven't you ever watched a junior dev get dragged through all sorts of arbitrary "don't breathe on it" setups just so they can start making tiny isolated bug fixes? And even then, you're just…
I don't understand what your comment have to do with contributing to OSS. Anyway, I don't really believe that codespaces or any out of the box tool is going to be a magical solution for junior devs not be dragged in those kind of setups in the projects that you're referring to.
That's exactly what this is. The setup is part of a clonable environment. So for large scale compiled projects, you wouldn't have to:
1. Download the massive thing 2. Get it to compile 3. Potentially not have to compile many files that already have their `*.o` (or equivalent) file in the environment.
It could be like just walking up to some other developers fully functioning station, and getting started.