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

351–360 of 619 posts

Re: GitHub Codespaces

#351

Post by petetnt »

marceloabsousa wrote: post #260
petetnt wrote: post #235

Earlier quoted context omitted.

I contribute to various OSS (and private) projects all time just by using the GitHub code editor and catching errors or regressions if any in the CI. Having a fully fledged dev environment is even better.

This is pretty cool. Can you share a bit more about your experience? I would like to be able to help out this way.

Basically it's just the same as whipping out a simple text editor in hurry; if I need to modify multiple files, I just do multiple commits (do a change -> commit -> jump to my branch/fork -> do the rest of the changes one by one) as GitHub doesn't support editing multiple files for a single commit and then I wait for the CI results. If something goes awry I'll probably clone the repo at that point.

Re: GitHub Codespaces

#352

Post by yarrel »

danso wrote: post #88
PedroBatista wrote: post #8

Github is getting Microsofted, there were some good things about this in the recent past, but I wonder...

What does "getting Microsofted" mean, especially in the context of the last 10 years?

A thin dusting of "Open Source" over lock-in, spyware, and censorship.

To thunderous applause from people who are fooled by the first element of that.

Re: GitHub Codespaces

#353

Post by mplewis »

Austin_Conlon wrote: post #310
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

How do the implementations compare?

In this case, they don't. Codespaces offers a lot more functionality than the GitLab web IDE.

Re: GitHub Codespaces

#354

Post by hamandcheese »

yarrel wrote: post #336
sneak wrote: post #63

Earlier quoted context omitted.

There are perpetual reminders all around that Microsoft's only pretending to like f/oss because that's where the developer attention (and thus corporate money) is. There's spyware in all of their open source apps (TypeScript excluded, because they couldn't get away with it there) that you can of course patch out, but you can't get it removed from the project because, free software or not, Microsoft gets to decide wha…

Those of you downvoting this - can you explain what you disagree with here? Because it looks like a good analysis of this part of Microsoft's strategy to turn "Open Source" into a spyware-laden sausage machine for Azure.

I think the downvotes are because Microsoft has been providing some amazing tools completely free of charge. If that helps them sell more Azure... great! Everyone wins, except GitLab and AWS.

Calling it spyware is hyperbolic.

Keep it up Microsoft.

Re: GitHub Codespaces

#355

Post by lostinroutine »

I wonder how they will (did?) work around the keyboard shortcuts that Chrome reserves (and doesn't propagate to the page). For example, Cmd+T in VSCode opens up the quick search panel, while in Chrome it opens a new tab.

Re: GitHub Codespaces

#356

Post by threeseed »

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 weeds.

d) On the main Git project screen there are 15 buttons. Including again ones for "Add Kubernetes cluster" or "Add License" which you can't remove or hide even though it's irrelevant for 99% of Git projects.

e) Feature set and billing are all over the place. It has great project/issue management but in order to get say roadmaps you need to have everyone in your team on the $99/month plan. Even though they aren't developers. So in some cases Gitlab ends up being much more expensive than Jira + Github.

I could keep going. But Gitlab is an example of a company that is moving too fast and needs much better product management. I would take Github's more deliberate approach any day.

Re: GitHub Codespaces

#357

Post by peteri »

recursive wrote: post #188
twodave wrote: post #163

Earlier quoted context omitted.

Honestly, unless I'm working on a Windows machine, I find JetBrains Rider to be the best option for C# specifically. This is especially true if you like having your tests easily accessible from your IDE. That said, VSCode is still very nice for front-end pretty much universally, and it's also great for things like back-end Javascript/Typescript. I think Codespaces is really going to excel when it comes to things like…

> This is especially true if you like having your tests easily accessible from your IDE. I haven't used Rider, but I'm curious how it could be easier than the Visual Studio test explorer? It seems pretty convenient, and doesn't lack any obvious features I can think of.

I assume in part this is because the Rider test explorer is based on the one in Resharper.

Some stuff it does better is things like running 64 bit and 32 bit tests at the same time, supporting both nUnit 2 & 3 without having to disable/enable the plugin. Mind you I spent some time with code in release mode trying to work why I couldn't debug a test last week.

To be fair I hate what Resharper does for Visual Studio performance and a lot of the really useful refactoring in box these days so I no longer use it.

I prefer to stick with Visual Studio but I know lots of folks who are happy with Rider. It's good for all of us when there is competition in paid for developer tools.

Re: GitHub Codespaces

#358

Post by [deleted] »

yarrel wrote: post #337
buzzerbetrayed wrote: post #297

Earlier quoted context omitted.

> dashboards for managers with all sort of stats on developers: code quality with arbitrary rules, productivity (number of lines of codes), number of stars from other developers, etc. How does GitHub Codespaces allow for any of this? All of this was already possible with plain git, no?

You give managers too much credit.

[deleted]

Re: GitHub Codespaces

#359

Post by thwarted »

soVeryTired wrote: post #262
thwarted wrote: post #24

Earlier quoted context omitted.

I wish the vscode remote dev functionality didn't require a binary server/remote side component. I have a bunch of users who want to use it, but it's not compatible with the system libraries on our servers and dev environments.

Are you sure it needs a remote component? The remote SSH dev experience is actually pretty good in python.

Quite sure. Here's the documentation.

https://code.visualstudio.com/docs/remote/remote-overview

It seems like it runs all the functionality on the remote end, and the vscode instance you're running on the machine in front of you is just the GUI. To install this, you need ssh access, and then it drops some binaries on the remote system and uses ssh to start them up -- so it looks to a layman trying to get this working that "it only needs ssh", but that's just for the install stage. These binaries only work with more recent releases of glibc.

You know what's interesting about some of the features listed on that page:

- Develop on the same operating system you deploy to or use larger or more specialized hardware.

- Sandbox your development environment to avoid impacting your local machine configuration.

- Make it easy for new contributors to get started and keep everyone on a consistent environment.

- Use tools or runtimes not available on your local OS or manage multiple versions of them.

- Access an existing development environment from multiple machines or locations.

We have all those already with the way our development environments are setup, but the reason people want to use vscode is for the editor, no one asks about the above things.

Re: GitHub Codespaces

#360

Post by factorialboy »

tommoor wrote: post #290
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

I'm sure he'll have his usual blogpost moaning about how Gitlab already has it by end of day.

To be fair, nothing was announced today by GH that wasn't in GL for several years.

Perhaps the quality of VS Code trumps GL WebIDE ... But I am not the sort of developer to ditch my desktop editors / IDEs for something running in a browser (electron or otherwise).

Post reply on HN