Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Codespaces

github.com

Post reply on HN
Print view View original

551–560 of 619 posts

Re: GitHub Codespaces

#551

Post by dklend122 »

mcolyer wrote: post #80
preya2k wrote: post #4

Interestingly, it seems that Microsoft hast just renamed its "Visual Studio Online" (which was basically the same as this new product) to "Visual Studio Codespaces". So it seems that they are merging these two products. (See: https://visualstudio.microsoft.com/services/visual-studio-co... ) EDIT: They actually announced the renaming of the product a couple of days ago: https://techcrunch.com/2020/04/30/microsofts-vis…

Codespaces uses the same underlying technology as Visual Studio Codespaces to bring a fully GitHub-native experience to our GitHub users. We've been working with multiple teams on the Visual Studio side to make this happen (I work as the product lead on Codespaces)

Can we please have Julia support? :)

Re: GitHub Codespaces

#552

Post by franciscop »

twunde wrote: post #366
op03 wrote: post #272

Earlier quoted context omitted.

All that is nice. But who are they building this for? Who is asking for this stuff?

For Github Actions, the product launch has been a major success and has become a new monetizable product. Anecdotally, I've heard of some companies moving their Jenkins/Circle CI/Travis CI workflows over to it, better proof is the sheer number of Github Actions that are now easy to install. This also allows Github to compete directly with Bitbucket and Bitbucket pipelines. If your question is about who is asking for…

As an OSS developer, Github actions make a lot of sense and is very welcome since it's very easy to setup (now! it was impossible in the beginning) and if you use bash scripts/npm scripts AND a tiny bit of workflow code then they are very agnostic as well.

I am unsure about this Github Codespaces though, I'll be testing it but I am fairly skeptical about invest a lot in Github-specific tooling beyond what is needed by a typical repo. It seems like Github has been trying to "extend" git into a proprietary phase for a while, and now with Microsoft backing it I'll wait to see if it's still the same old concept of locking you in deep and then do as they please. Not sure, it does look like they are going nice for now, but I personally prefer to wait.

This Codespaces doesn't solve a specific need I could point out like Actions did before, but maybe I'm just not their target.

Re: GitHub Codespaces

#553

Post by alufers »

geokon wrote: post #549
icebraining wrote: post #422

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.

a bit of a noob question. I'd love to be able to tweak code on the spot. Like I'm showing something to my boss and he wants something quickly adjusted, I write a couple lines, commit and then with Github Actions I get back an updated executable immediately But I feel like things are set up explicitly to not work this way. Maybe I'm doing something wrong but can you trigger a rebuild of a prerelease? It seems you need…

You can set up your actions to build an executable for each commit on the master branch, it will be available as an artifact in the actions tab. This is useful if you want to test your built code.

Generally speaking, you shouldn't modify existing releases, since somebody may have downloaded them and he will have no way of knowing you have improved them.

Re: GitHub Codespaces

#554

Post by inopinatus »

twunde wrote: post #164
mcolyer wrote: post #80

Earlier quoted context omitted.

Codespaces uses the same underlying technology as Visual Studio Codespaces to bring a fully GitHub-native experience to our GitHub users. We've been working with multiple teams on the Visual Studio side to make this happen (I work as the product lead on Codespaces)

Similarly Github Actions is reusing a lot of Azure Pipelines under the hood. One of the most impressive parts about Microsoft's recent acquisitions is how quickly essentially two separate companies are now sharing code. It's hard enough to get different teams/products in the same company to use shared code in a meaningful way, and Microsoft has accomplished it with a new company.

GitHub’s acquisition of Microsoft is really paying off.

Re: GitHub Codespaces

#555

Post by legostormtroopr »

ketzo wrote: post #548
LoungeFlyZ wrote: post #528

Earlier quoted context omitted.

Do you really want to write coffee on your phone? I couldn't imagine wanting to every do that myself. Am I weird? :)

I will say it would be nice to review a PR while standing in line for groceries.

I'm gonna say you are in the minority there. Firstly, a Review should be just that a review of the code - not just a blind acceptance of a button. Its going to be hard to properly review code, which may be across multiple files, or may require switching within the same file, on a phone.

And secondly, work life balance, just because you can work while waiting in line for groceries doesn't mean you should

Re: GitHub Codespaces

#558

Post by geokon »

alufers wrote: post #553
geokon wrote: post #549

Earlier quoted context omitted.

a bit of a noob question. I'd love to be able to tweak code on the spot. Like I'm showing something to my boss and he wants something quickly adjusted, I write a couple lines, commit and then with Github Actions I get back an updated executable immediately But I feel like things are set up explicitly to not work this way. Maybe I'm doing something wrong but can you trigger a rebuild of a prerelease? It seems you need…

You can set up your actions to build an executable for each commit on the master branch, it will be available as an artifact in the actions tab. This is useful if you want to test your built code. Generally speaking, you shouldn't modify existing releases, since somebody may have downloaded them and he will have no way of knowing you have improved them.

I guess you're right. That this is the expected workflow. The way the UI by default dumps Prereleases and Releases together (with very small faint font to distinguish them) in the same tab called "Releases" is an issue so I sorta understand why you feel it'd be confusing. The UI is no good, but this is not an insurmountable problem

It's true you can have a latest artifact.. I will try using that - but I can't email a colleague and tell him/her to download an artifact. There is no "latest build action artifact" page and there is so much extraneous information that if they've never used github you'd need to attach an explanation of where to click.

I didn't feel my use-case was particularly unusual, but I guess it's doesn't fit Github's model.

Re: GitHub Codespaces

#559

Post by pinopinopino »

Sounds good, microsoft is building some interesting tools lately. I use visual code on the desktop for various languages, so it is a welcome to see it will be supported online through github repositories.

Re: GitHub Codespaces

#560

Post by traspler »

threeseed wrote: post #356
sparky_ wrote: post #284

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…

Ah yes, the "Who can find the open 2y old GitLab issue for our problem" game. There is always one and it always has a couple of "This is an issue for a customer " comments. At least even very old issues still get responses and seemingly are tracked somehow.

I kind of agree with the "too fast". It seems to me that many features are being created as a PoC to pad out features lists and having something new to market. It will then live on as barely useable and accumulates hundreds/thousands of issues as the devs seem to be spread way too thin over all the PoC, core and new features.

Post reply on HN