News for hackers. Stuff that matters.
Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @03:42AM (#24339437)
> as a co-founder who is spending less time as a developer, and more time in meetings, writing emails, strategy papers, [...] this is just amazing [...] I’ve been spending a lot of time getting Windows Subsystem for Linux working

lol, just ssh into a $3 vps as dev machine, real Ubuntu, real tmux/(n)vim, no setup, no hassle

Edit: to be fair, Cloud9 was my entry drug into remote development bringing me to my setup above; the idea is awesome and Github Codespaces is too but there are just too many limitations and having a real, ever-running Linux vps everywhere, even on your phone is just magic and even when you write strategy papers...

Re:First Impressions of GitHub Codespaces by coldtea on Tuesday September 01, 2020 @04:05AM (#24339542)
>lol, just ssh into a $3 vps as dev machine, real Ubuntu, real tmux/(n)vim, no setup, no hassle

Infamous Dropbox comment: https://news.ycombinator.com/item?id=9224

Re:First Impressions of GitHub Codespaces by swiley on Tuesday September 01, 2020 @07:30AM (#24340643)
Meh. The difference is that rsync doesn’t really do what Dropbox does (handle syncing both ways) otherwise they would have been right. Ssh+tmux really does do everything this does and it does it in a way that doesn’t tie you to any single organization. The current company I work for uses the ssh to a VM style setup and I was able to just jump in. Everything was where I expected it to be.
Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @04:09AM (#24339563)
Yeah but in contrast the idea isn't new, Cloud9 did this ages ago. Github has the advantage that they own a huge dev focused platform. My point is if you deal a bit with code, even as a founder who writes strategy papers all day long, getting into tmux/vim isn't harder than a vscode-like interface, it pays off in the long run
Re:First Impressions of GitHub Codespaces by wp381640 on Tuesday September 01, 2020 @04:29AM (#24339650)
XDrive -> Dropbox
Re:First Impressions of GitHub Codespaces by josephg on Tuesday September 01, 2020 @03:50AM (#24339484)
I respect developers who make that work, but the development experience over SSH (vim, etc) is never as good as local development. You can't use vs code. You have to deal with lag delaying keystrokes. If you download a file and want to copy it into your dev environment you need to SCP it over. If you want to test a network service its nontrivial to point your local browser at the remote machine. If you sleep your laptop and open it again, you need to reconnect your SSH sessions. Etc etc.

A lot of these issues can be solved with enough extra work setting everything up - but that completely defeats the point. "no setup, no hassle" is never my experience.

Re:First Impressions of GitHub Codespaces by Philip-J-Fry on Tuesday September 01, 2020 @03:56AM (#24339514)
>You can't use vs code

Have I got news for you https://code.visualstudio.com/docs/remote/ssh

Re:First Impressions of GitHub Codespaces by andybak on Tuesday September 01, 2020 @06:05AM (#24340095)
That requires installing VS Code locally whereas I thought we were talking about a "no install" dev environment?
Re:First Impressions of GitHub Codespaces by Aperocky on Tuesday September 01, 2020 @04:19AM (#24339606)
vim once you get into it is as powerful as vscode, and runs just fine in machine without GUI installed.

Funny enough, your description is exactly how I work, except the java part, but then vscode doesn't have an edge with java either.

Re:First Impressions of GitHub Codespaces by dividedbyzero on Tuesday September 01, 2020 @06:02AM (#24340084)
> vim once you get into it is as powerful as vscode

Maybe, with a lot of effort to set it up like that, and a steep and long learning curve with lots and lots of idiosyncracies, because it's really ancient tech that was made for a completely different kind of computer, and you have to actually like living in a terminal and vim's idiosyncracies in particular.

Re:First Impressions of GitHub Codespaces by Aperocky on Tuesday September 01, 2020 @12:30PM (#24343539)
You're probably right, but the advantages of vim in my mind compared to IDE/VSCode/Atom is:

1. Ability to open up any sized file. Anyone who accidentally clicked on a 15mb log file in the directory know what I'm talking about.

2. commands, specifically %s, norm, etc applied over visual mode. norm is particularly powerful when you want to batch edit.

3. macros, the ability to define macros both beforehand, and on the fly is really useful.

4. Availability. Any linux box I ever sshed into has never failed to have vim.

^^ Those are the features that imo are important and won't be available as a vim plugin to other IDEs. People also don't realize how vim has these feature that matches other IDEs.

1. Plugins, the vim plugin world is as rich as other IDEs like vscode.

2. language servers, these can run in the background and provide autocomplete, code smell, e.g. jedi, tsserver-vim.

Re:First Impressions of GitHub Codespaces by bblough on Wednesday September 02, 2020 @01:37PM (#24355657)
TIL about norm. Thanks!
Re:First Impressions of GitHub Codespaces by markild on Tuesday September 01, 2020 @03:57AM (#24339517)
I guess that's where vscode's remote ssh extension comes into play.

There's things to be said about it being closed source, but it _definitely_ also removes, IMO, the pain points of remote editing.

Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @04:07AM (#24339553)
> vs code

check coc.vim, uses vsc's native LSP, 99% of LSP's features

> delaying keystrokes

I have 16ms latency as my 60hz screen does and def less latency than a local vscode

just use a vps close to where you are

Re:First Impressions of GitHub Codespaces by robotmay on Tuesday September 01, 2020 @04:18AM (#24339601)
Or use Mosh, which eliminates the keystroke lag.
Re:First Impressions of GitHub Codespaces by antihero on Tuesday September 01, 2020 @04:40AM (#24339691)
Some people don't want to use vim, they want to use VSCode.
Re:First Impressions of GitHub Codespaces by vidarh on Tuesday September 01, 2020 @04:23AM (#24339614)
All of these frankly just sounds like you're unfamiliar with the typical workflow over ssh and have different tooling preferences.

Nothing wrong with that - it's a matter of taste. But personally the reason I often work over ssh connections is that I find the local-only development experience deeply deficient. I package up environments in containers that I can bring up anywhere by dropping in a systemd unit file to pull the images, which means I don't have to worry about whether I have my laptop with me as long as I have ssh access, or about environments changing when I switch laptops. I can also bring those environments up in containers on my laptop, of course. Once I got into the habit of packaging up everything that way it became easy to do, and keep cutting down on the setup effort when I change laptops or make other changes.

The flexibility to be able to access the same environment and editor anywhere is an important reason why I insist on using editors that work in a terminal, because that flexibility is far more important to me than any specific editor features. While most of the time I work locally, when I need to ssh in somewhere, not having to deal with a different environment matters. And ssh vs. entering a container is a close enough equivalent that the same workflows apply for the most part.

Last couple of years I've used my own client-server based editor that holds all the buffers in a separate process (and traps all exceptions and forwards them to the client, and checkpoints its internal state - I have a couple of years worth of open buffers in RAM, but it just adds to ~24M), because I wanted an editor I could get exactly how I wanted in exactly the language I wanted, and it was worth it.

Lag is an issue if on a slow phone connection or something, but you surprisingly quickly get used to working even with ~100ms+ lag, and that's a rare exception. As long as you pick a VPS provider reasonably close 15ms-30ms is not hard. I'm in London, and mostly use Hetzner in Germany, get consistent <20ms to them. It's not noticeable when I log into them. There are few places in the world where you can't find VPS providers close enough. Of course it depends on having decent internet access, so I'm sure there are places that isn't viable. That said, years back I worked over SSH from Beijing to servers in Texas, and even that worked well enough despite the lag.

And if you work on things remotely, you quickly get used to download things straight to the remote machine rather than download and copy over whenever possible, and it usually is possible - wget, curl, lynx and links can take a while to get used to, but it's rare I need to resort to downloading anything locally. Not that it is usually a problem if I do, but of course more dependent on upload speeds.

Pointing a local browser to a remote machine requires no setup, just knowing the IP. If you want an encrypted tunnel, all it takes is a flag to your ssh client to port-forward. First thing I'll do if I need to do work against a remote server regularly is to set up an alias in .ssh/config to pass the right options.

Similarly setting up autossh or similar to automatically re-establish ssh connections (and re-attach to screen or tmux) is a simple one-time affair if you often need to re-attach, but if you run screen or tmux anyway (and I couldn't imagine not doing that on any machines I do actual work on), it's trivial to re-attach to the same state anyway. I run bspwm - a programmable tiling wm, which also means I can easily set up workspaces where it automatically triggers suitable scripts to set up the right windows ssh'd in to the right screen sessions on login, as well.

It's true some of this is extra work, but it's extra work once and you have setups you can copy everywhere, and there's extra work to get used to any new tool, but once you get used to these workflows they are extra-ordinarily flexible, not least because they're also scriptable in ways that allows you to add more and more customised shortcuts for the things you do regularly in a lasting way.

I've carried my current client-side set of configs and convenience-scripts through half a dozen laptops by now.

Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @06:16AM (#24340161)
nice read and I also recommend anyone to try this path, living 24/7 in the shell has not just productivity benefits, you are just closer to the bare metal and will learn so much more. Something we lost in the decades of GUIs
Re:First Impressions of GitHub Codespaces by dividedbyzero on Tuesday September 01, 2020 @09:19AM (#24341431)
It's the opposite for me. Not living in the shell 24/7, for me personally, doesn't just have big sanity benefits, it also makes me so much more productive.

I find shell environments incredibly limiting, I feel like my visual brain starves when limited to what feels like a visual desert to me for longer durations. Yes, there are a couple of things they absolutely excel at, and I use the shell for those, have one open all the time in a window – but everything else? Not my cup of tea. I'm a fairly visual person and I like manipulating things directly, I like visual cues, I like discoverable software, I'm into well-done(!) motion cues big time. I like using the mouse. I may have to hand in my hacker card after writing this.

I like how IntelliJ shows a million small annotations and cues that terminal just can't possibly support, how I can just stumble over features via the UI. I like how graphical text editors aren't just a featureless wall of text, that there is a UI for the eye to use for structure, that I usually have much more information immediately visible, and that the UI allows me to do things without having everything in my head or looking it up in huge manpages that often as not are hardly fit for for human consumption.

Lots of things I do wouldn't even be possible in a shell, like graphics/design work, 3d modelling, spreadsheets, and the rest wouldn't be much fun. Yes, I'm sure there is a way to do complex 3d modelling in emacs. No, I don't think that will work for me. Yes, I've tried vim and neovim and emacs, and I really don't like their paradigm.

As to what has been lost, I firmly believe I've gained much, much more, and I doubt I personally have actually lost anything substantial, but maybe we won't agree there. Not being bare-metal all the time is an advantage in my book; I've done some bare-metal and it isn't for me, huge respect to those who work with assembly all the time. A shell isn't very close to the metal for me, it's a really heavyweight, very idiosyncractic abstraction over bare metal, once you peel apart all the layers in between, it just makes it easier to manipulate other heavyweight abstractions directly. What I've learned in years of doing lots of work in shells is mostly limited to idiosyncracies of the shell I'm using (so far fish, sh, bash, a bit of zsh) and the various tools involved; especially macOS doesn't expose that much of its internals via the shell, not that much to be learned there.

Why stop at that level of abstraction, though? Why not put something on top that allows me to use all those areas of my brain that do complex visual and motion stuff? I strongly feel those are still way under-utilized, or rather badly over-utilized, or mis-used in general in all current mainstream GUIs; maybe that's why some people prefer theirs to be extremely simplicistic. Better use of motion might involve less motion than e.g. macOS currently has, but applied way more judiciously and effectively, possibly with a solid neuroscientific backing. Reality isn't a solid monochromatic wall of even-sized glyphs, why would UIs have to be?

Sadly, the only place where I feel motion in UIs is done well currently is the very rare game that gets it just right, but those paradigms wouldn't translate well to productivity UIs. But while not ideal by any means, I still find the macOS UI to be way ahead of any terminal UI in that respect; iOS even more so, but I can't use iOS devices for day-to-day work, not yet at any rate. I gather it's the other way around for some people, which is fine of course. You do you, and I stick to my animated GUIs, and I hope someone will figure out why we see these things so very differently some day, and we'll be able to make new things work better for all of us with that knowledge.

Another thing, discoverability and rich input. Take the Touchbar, fantastic thing – I'd absolutely love to have an external one that I can attach to my mechanical keyboard. With the touchbar I can do all sorts of stuff right away (in apps that support it) that I'd have to memorize arcane key combinations for otherwise; I hate doing that. IntelliJ supports the Touchbar pretty well. It can double as a sort-of analog slider, without any finger smudges on my main display like on Surfaces with touchscreens (though that's neat too – love to do this on the iPad). There are menus that contain pretty much everything an app can do, on macOS they're even searchable. I'm sure there are ways to replicate some of that in shell environments, but I doubt it would get very close – and then I wouldn't want to invest hours and hours to set it up like that, because, in the end, my visual brain would still starve. I've toyed with using my iPad and Pencil as a graphics tablet via Sidecar; I'll definitely do a lot more of that in the future. I wish there was a collaborative whiteboard app that supports this really well and also can get approved at my work. That would get close to whiteboarding my thoughs like I do all the time in the physical office, another thing I can't translate to a terminal workflow at all, I can't even translate that to a graphical workflow without a physical pen or similar.

I get that a higher-stimulus, "richer", more immersive, more physical user experience is the opposite of what some desire, but I believe there are lots of people who enjoy that sort of thing, when done well. I realize there are lots of upsides to shell environments as well (super stable software, highly portable, runs everywhere, relatively consistent, highly configurable unless you want anything not made of solid glyphs, etc. pp.) but those just don't rank all that high for me. Like, I have my Macbook set up the way I want it, I can move everything to another one just by restoring from backup, I don't need everything to be highly portable. I rarely work on remote machines – one of the upsides of doing everything as infrastructure-as-code, and when I do, it's via JupyterLab and the like.

Re:First Impressions of GitHub Codespaces by vidarh on Tuesday September 01, 2020 @10:54AM (#24342410)
> Reality isn't a solid monochromatic wall of even-sized glyphs, why would UIs have to be?

I work almost exclusively in a terminal, but I never work in "a solid monochromatic wall of even-sized glyphs". Well, I usually use even-sized glyphs, but certainly not walls of them, and I rely heavily on tools that use unicode creatively to annotate text and colours.

Terminals have been able to handle graphics of various levels for decades (e.g. Sixel and ReGIS), though unfortunately it's not as widely used as it could be. E.g. my repo contains a script in bin/ to spit out images to the terminal using Sixel, which makes it transparent to ssh.

But the point for me at least is not an objection to graphics, but an objection to not having a command line to manipulate everything. Including graphics when I use it. And an objection to being unable to access data and code remotely without taking special steps.

The terminals gives me that.

It's not at odds with graphics at all. But it's add odds with a focus on graphics at the expense of function. And it's at odds with accepting a world where your app and your user interface needs to live on the same machine.

Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @12:36PM (#24343609)
> graphics/design work, 3d modelling, spreadsheets,

here I agree. these just don't work in the shell. but too many programs are gui-based which shouldn't be. a shell is the foundation for coding and the reason, so many non-tech people think of coding of some wizardry is the lost of the shell. Remember DOS and that .bat files. Latter were not more than some batched commands and eventually a program.

Stuff like settings, task manager, text editors, any kind of servers, should be text based. Everyone is 100x times faster skimming through VSCode's text based settings than Blender's preferences. I am not against GUIs but less of them.

Re:First Impressions of GitHub Codespaces by jan6 on Tuesday September 01, 2020 @04:09AM (#24339560)
it IS trivial to port forward though, lol
Re:First Impressions of GitHub Codespaces by simonh on Tuesday September 01, 2020 @03:50AM (#24339487)
>... no setup...

Wow, that's a neat trick, how do you manage it?

Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @03:58AM (#24339524)
?

click "new vps" at your hoster (60sec), ssh to your new vps, git clone your tmux+nvim config from github (3s), you're ready to go

Re:First Impressions of GitHub Codespaces by onion2k on Tuesday September 01, 2020 @04:08AM (#24339558)
So it's "no setup" if you've already done all the work to make a portable setup that enables you to do work over ssh, but actually a ton of setup it you haven't.
Re:First Impressions of GitHub Codespaces by vidarh on Tuesday September 01, 2020 @04:31AM (#24339656)
You've done all the work to commit a setup that already works for you, for the sake of avoiding having to manually create one whenever you need to setup a new machine or vm.

It's one of those things that repays itself by the second install or so.

Re:First Impressions of GitHub Codespaces by desmap on Tuesday September 01, 2020 @04:13AM (#24339577)
shouldn't everyone who touched code on a server have some basic tmux/vim config, at least vim? it's no rocket science and doesn't have to be perfect
Re:First Impressions of GitHub Codespaces by onion2k on Tuesday September 01, 2020 @04:16AM (#24339587)
shouldn't everyone who touched code on a server have a basic tmux/vim config, at least vim?

No. Obviously not. There are millions of developers who don't work that way.

Re:First Impressions of GitHub Codespaces by andybak on Tuesday September 01, 2020 @06:09AM (#24340119)
Yeah. I still go with nano those rare times when I need to edit remotely. Vim just never seemed to fit my brain and I don't need to do this enough to make it work getting over the hump.

The infamous "can't work out how to quit Vim" might have soured my initial experiences. That's pretty much all I remember from the first few dozen times I accidentally launched it because it was set as the default $EDITOR.

Re:First Impressions of GitHub Codespaces by richbradshaw on Tuesday September 01, 2020 @04:31AM (#24339655)
I’ve been developing for a decade and have never used tmux and have use vim for probably ten hours.
Re:First Impressions of GitHub Codespaces by vidarh on Tuesday September 01, 2020 @04:32AM (#24339660)
The specific tools are not really the point. The same applies whichever tools you need - sooner or later you'll need to cleanly set up a new machine, at which point committing your configs pays for itself.
Re:First Impressions of GitHub Codespaces by andybak on Tuesday September 01, 2020 @06:10AM (#24340124)
I can't think of anything that I need in a config that isn't a) a luxury or b) specific to my local machine.

There's a few tweaks I miss when working in a remote shell but none are essential.

Re:First Impressions of GitHub Codespaces by vidarh on Tuesday September 01, 2020 @06:50AM (#24340366)
So you can think of things that'd be useful, you just see it as a luxury. But the point is it's not a luxury once you commit the configs and setup scripts and turn it into a single command to deploy anywhere you want it.

And what I found when I started doing that was that suddenly I was a lot less hesitant to let myself become dependent on time-saving tools because I knew they'd be available anywhere with ease.

I can't imagine suffering through a default shell environment or a default editor config any more.

But committing them is not just about remote machines, but about having a clean record of what is needed to set up any new machine I acquire as well.

Re:First Impressions of GitHub Codespaces by dividedbyzero on Tuesday September 01, 2020 @09:27AM (#24341507)
I've had to set up a new machine like, maybe four times in recent years I think. Except for one time (new employer) I just restored a new Macbook from a backup and was good to go. I don't edit code on servers unless in dire emergencies that are extremely rare (as they should), and nano will do fine for those. Everything is infrastructure-as-code and I like it that way. What work I do on remote hosts happens through e.g. JupyterLab.
Re:First Impressions of GitHub Codespaces by vidarh on Tuesday September 01, 2020 @11:01AM (#24342504)
I don't edit code on servers either, but I frequently need to debug systems, or do experiments or develop in containers set up for that purpose. As such it's not unusual for me to work with dozens of different environments in the course of even a week.

It's not just about having my editor available, but being able to trivially easily pull in the basic tools to do what I want, and that is especially important during emergencies, but it's also about convenience in other situations.

It sounds like you're lucky enough to deal with very simple environments. That's great. I'd still argue the cost in time of committing your config is so low that it'd be worth it. It takes pretty much one reinstall before it's paid for itself, or one instance of being somewhere without your usual environment.

Or one instance of doing something silly to a config and forgetting what you changed.

The nice thing about it is that it can start extremely light-weight - just literally a "git init" and .gitignore everything, and then gradually force add and commit.

Re:First Impressions of GitHub Codespaces by jacquesm on Tuesday September 01, 2020 @04:12AM (#24339576)
> I’ve been spending a lot of time getting Windows Subsystem for Linux working

I wouldn't spend a minute on it. Why bother with such an abomination when you can just use Linux the way it is intended to be used with less hassle and corporate superstructure that you most likely will never need.

Re:First Impressions of GitHub Codespaces by jayd16 on Tuesday September 01, 2020 @04:23AM (#24339617)
Well if you're actually asking... I do it so I can use Windows tools like Unity (Editor just runs the best on Windows) and good graphics drivers, as well as having access to bash and linux tooling.
Re:First Impressions of GitHub Codespaces by Shared404 on Tuesday September 01, 2020 @04:35AM (#24339674)
> so I can use Windows tools like Unity (Editor just runs the best on Windows)

Wasn't Unity a Mac exclusive tool to start out? I know they have support for Windows at this point, and would understand if they've refocused on Windows since then.

Re:First Impressions of GitHub Codespaces by hurricaneSlider on Tuesday September 01, 2020 @04:48AM (#24339722)
Unity feels like it runs best on Windows to me. Metal bugs caused quite a few Unity issues for me when I was developing on a Mac. That was a year or so ago, so maybe the situation has improved.

Also a lot of useful 3d content creation software is Windows only, or only supports CUDA acceleration, so implicitly rules out Mac from being a first class citizen (e.g. substance painter)

Obviously not every game is the same, or needs fancy tooling. But Windows feels like it just works for game dev.

Re:First Impressions of GitHub Codespaces by Shared404 on Tuesday September 01, 2020 @07:51PM (#24348488)
It doesn't shock me that it run's best on Windows, and you should of course use whatever works for you. I'm sorry if I implied anything else.

I have to agree. I love me some *nix (excluding Mac/iOS, actually), but game dev is the one thing I played with that just felt easier on Windows.

Re:First Impressions of GitHub Codespaces by jayd16 on Tuesday September 01, 2020 @01:14PM (#24344113)
Metal, Catalina's 32bit changes and other things have made everything but the latest version on Unity unstable on Mac.
Re:First Impressions of GitHub Codespaces by jacquesm on Tuesday September 01, 2020 @04:30AM (#24339652)
I didn't see a question mark in there.

If the Unity Editor runs best on Windows then maybe petition the authors to improve it? Otherwise you might end up in a Photoshop/Apple situation and we all know how that ended.

Good graphics drivers are available for Linux, and have been for years.

Access to bash tooling is the norm on any Linux system.

[dead]
Re:First Impressions of GitHub Codespaces by bachmeier on Tuesday September 01, 2020 @05:46AM (#24340016)
"Use SSH rather than WSL" is not the same as the Dropbox comment. Dropbox was dead simple to use, and it did something complicated, keeping files on various machines synced. WSL requires setup and there's friction while you use it. SSH is actually less setup than WSL if you're using a standard Ubuntu Digital Ocean instance.
Re:First Impressions of GitHub Codespaces by andybak on Tuesday September 01, 2020 @06:13AM (#24340147)
WSL has one advantage over SSH. I can continue working if my signal drops.

(Setup and friction are actually pretty low - but that's another discussion)