Hello,
I installed Ubuntu a few months ago on my work laptop and I’ve been running and loving it since.
However, I am used to VsCode, so this is what I am using in Ubuntu as well.
So I am curious, what kind of coding so you do? And what is your workflow.
I am an embedded firware developper and mainly use C. I am cross compiling my code in VsCode for a FPGA from Xilinx (dual core arm + PL)
Never dove into make files and cmake more than what I needed in the past, but I had an opportunity to learn CMake and build a project from it.
So my workflow is :
- Code in VsCode
- Build in CMake
- Transfer the app through scp on the target with a custom script (target is running petalinux, which is yocto + Xilinx recipes)
- Use gdb server to debug the code.
It’s a pretty simple workflow, but I’d like to know what you guys are running so that I can maybe upgrade my workflow.
$mod+enter vim enter Ctrl+p [type a part of the name of the file I want] O [write code]
I tend to prefer Jetbrains editors (CLion, Rider, WebStorm) for projects, and just nano/micro for config editing and such…
For python:
- Pycharm with integrated git For web dev and game dev:
- vscode with GitHub desktop or integrated git, XAMPP if I’m doing back end
I mainly write C. I really like Intellij Clion because it uses CMake as project files. It also makes tools like valgrind, perf and gdb available without having to go to the terminal.
I’m an old school emacs guy, I prefer that for c++/python/etc and run KDE Neon because I like KDE and I’m used to ubuntu (and Kubuntu has some issues). For c++ I use CMake, google test. Not really a fan of docker etc. but I have used Kubernetes and docker in the past. Those types of containers just create new and more complicated problems than just testing on the target platform, but in some niche cases it can be useful.
I can’t stress enough how awesome emacs is, but it takes a serious investment to get efficient with it.
CLion for Rust/C++, VS Code for web dev stuff
I mostly write rust now, but this workflow was finetuned over years. Use 2 terminals each on a diferent monitor, one runs neovim and the other is for building/running. If the project is a bit more complex, I will run it in a docker container( maybe mount the /etc/shadow and frieds so all artefacts are created using the same user as in the outside) . Developed a bunch of tools over the years to optimise this:
- a ‘package manager’ in bash so I have a folder for each project/context. One for work, one common, one for the server stuff like this. All are in PATH.
- parterm - remote control for the terminal so i can start a build from neovim in a different terminal.
- ‘ndock’ - at work I use a bunch of branches, this script will set up a few envs and then start a docker in a folder coresponding to that branch.
At my old job had to work on a remote vm so I setup sshfs for a while, but was slow and just moved all my tools there.
I have a pattern where i put all my projects in ~/dev/<project><branch> and all info related to a task in ~/dev/<project>/bugs/<issue_nr>. This is usefull because I can have scripts the work similar for different projects with small changes. For example to run my binary with the config for a issue i just do
ndock <branch> nr <issue nr>This will start docker or connect to an existing one for that branch if available, compile the code, run my binary with the config present in the bug folder. In the last few month started running it with rr to be sure i can debug any random issue.
Transfer the app through scp […]
I use an ad-hoc while loop in a shell with
inotifywaitto wait for changes in the watched directory and thenscpit.That’s clever. I’m not used to shell scripting yet, but I really like that it is easy to automate things in Linux. If you can run it in terminal, you can script it.
Java dev, running opensuse Tumbleweed with KDE.
IntelliJ IDEA, maven, git, postman
Kate for quick edits and note taking works very well
Konsole is my terminal of choice
Teams for Linux because I have to
docker on the command line because there’s no docker desktop for Linux. There is for windows and MacOS tho, although Linux is literally the thing where it runs on the kernel and whose concepts the whole thing is based upon. Fuck them.
Kind of sad to see still lack (for Linux in general) of apps that are often used in companies. E.g. Teams and docker desktop
Have you checked out podman desktop or rancher desktop?
If any of those can be used with docker, I’m sold!
I cannot move to podman because our projects are shared and the rest of me team is on Windows or MacOs and they all use docker desktop. We also use docker compose files.
I have now and I’m loving podman desktop! All I wanted was a quick and easy way to stop/start/delete running compose clusters, and podman desktop detected all my running docker compose containers and displayed them with the familiar tree-like UI with individual or global controls to play/stop or delete.
Thanks! :)
Sweet, I’m glad the recommendation is working for you!
Teams for Linux sucks and is not maintained anymore. Devs recommend using the web app and this is what I’m using in Chrome, works really well. Otherwise I’m also on Tumbleweed KDE :)
There’s an unofficial cliënt that I’ve used in the past. Works well even on Wayland (where screen sharing can be an issue sometimes): https://github.com/IsmaelMartinez/teams-for-linux
If I’m not mistaken, this app is just a wrapper for the web app.
I had a lot of issues with wayland and that app.
Indeed this is the description I find on Discover:
Unofficial Microsoft Teams client for Linux using Electron. It uses the Web App and wraps it as a standalone application using Electron.
The advantage compared to teams.microsoft.com (at least when I load it in Firefox), is that it has many more features, since I guess it’s using an “Edge” user agent, which unlocks stuff that is not enabled for FF. For example, I can have 1:1 calls (yeah, I know…) and blur my background or even set a background pic, all things I can’t really do on FF.
On the other hand, screen sharing works unreliably (at least in a Wayland session, X11 is fine). I’ve reported a bug to KDE since I assumed it’s a kwin issue, but I should test it with a gnome wayland live medium as well…
- Code in VSCodium
- Code in Kate to keep thing fresh
- Code in Nvim because I still need to learn it
- Cry while debbuging a React app because the error messages aren’t very good
- Wish I were working with Svelte or had enough backend experience to switch to being a backend dev
- Play with terminal configs and shell scripting to distract myself from my woes
- Rinse and repeat.
Aside from the (not so much) jokes, give VSCodium a try, it’s to VSCode what Chromium is to Chrome, and works just as well.
I will look into VSCodium. I’ve heard a little about it, but I couldn’t tell you what is the difference between the two.
There is, or was, also code-oss. Can’t remember all the differences though
Microsoft develops vscode as open source, but compiles it with proprietary telemetry tooling.
VSCodium compiles from the same source code but without the telemetry
Then i will definitely switch. Are the VsCode addon compatible with VsCodium?
They are, but some might not be available from the extension store. Usually copying from vscode extensions folder works with no issues in my experience, but search the Codium store first just in case.
Copilot doesn’t work on VSCodium from my experience.
I usually hack stuff together with vim and tmux (I know, it’s redundant but Ctrl b is just a reflex at this point) when on a remote machine, but I use vscode at work and recently discovered the remote mode for Linux development… It’s pretty awesome, like not anything you can’t set up with vim or emacs, but it’s seamless remote development if you already like to use vscode
I would like to do remote dev directly on the target, but it only has64Mb qspi Flash and 512Mb of RAM, so I can’t install any modern development tools without exploding my 64Mb.
I cross compile with arm-linux-gnueabihf-gcc so I at least don’t need to use the awful Xilinx IDE.
Since we’re not sure yet if we will keep our current hardware for 1.0, but not tying my project to a vendor tools, I can easily switch my custom scripts for the new hardware.
Hmm are you compiling code? Sounds like the kind of platform that shouldn’t host its own build tools. For that kind of setup I would consider building a remote dev box that can push to / debug the target platform? Maybe even control power to reset the dev board.
I cross compile then push the program through a scp and start gdb-server with a script.
The remote dev box is a good idea because I can use any computer to access it and still be able to push code. I will look into it.
Bspwm/sxhkd on Artix Linux with runit init.
Neovim, lots of plugins and custom shortcuts and commands. Espanso text expander for even more functionality.
St terminal with zsh. Lots of aliases and shell scripts add lots more functionality.
JavaScript Developer with some docker integration.
