News for hackers. Stuff that matters.
Re:A History of IDEs at Google by mghackerlady on Wednesday May 13, 2026 @02:07PM (#48125352)
How many new googlers use vim or emacs do you think? I can imagine at least a small amount of new vim people since vim will always be popular, but I would love to know if more than a handful of new googlers a year use emacs
Re:A History of IDEs at Google by tipsytoad on Wednesday May 13, 2026 @02:55PM (#48125924)
I joined gdm recently, and previously used (neo)vim exclusively. Begrudgingly Cider-V is very, very good. It might be possible to get by without it, but the system is so locked down you’re going to make a lot of sacrifices. (very few authorised extensions, codebase is so large it’s going to break whatever tools your used to using anyway, no git)

I’m well thinking I may as well trade my brick of an m5 pro for a 13” chromebook, it’s a strange time.

Re:A History of IDEs at Google by skirmish on Wednesday May 13, 2026 @03:29PM (#48126324)
> codebase is so large it’s going to break whatever tools your used to using anyway, no git

There is Jujutsu (with Piper backend) officially supported, and that is better than git. But of course, you will not be grepping the source code, there is code search for that.

Re:A History of IDEs at Google by kccqzy on Wednesday May 13, 2026 @05:16PM (#48127702)
When I was there all the cool people used mercurial. Git5 was creaky and didn’t work well but hg worked brilliantly. The cool people used hg to do stacked CLs so they were productive even when blocked by code review.

Fun fact: This particular version of hg with its extensions actually originated from Meta.

Re:A History of IDEs at Google by tipsytoad on Wednesday May 13, 2026 @05:31PM (#48127909)
We can use jj now, thank goodness. But I still miss my old git workflows + lazygit
Re:A History of IDEs at Google by kccqzy on Wednesday May 13, 2026 @09:59PM (#48130264)
I’m no longer at Google and I use jj for my git repo at my current workplace. It’s great as it’s similar to hg but slightly more convenient (no need to manually `hg evolve`). It’s also great that it’s a skill that’s transferable to the world outside google3.
Re:A History of IDEs at Google by mghackerlady on Thursday May 14, 2026 @09:06AM (#48134847)
have you tried fossil? I really like it for personal projects
Re:A History of IDEs at Google by laurentlb on Wednesday May 13, 2026 @05:51PM (#48128103)
For security reasons, the VSCode marketplace is not accessible, but many (in the 3-digit range) external extensions have been imported. One technical limitation is that some extensions are not designed for the web (e.g. try to run local things).
Re:A History of IDEs at Google by barrkel on Wednesday May 13, 2026 @02:19PM (#48125488)
I've switched to emacs and I no longer use IDEs. This is because I do all my edits, as a personal policy, via LLM. I mostly use emacs for magit (I work on a git-on-borg repo).
Re:A History of IDEs at Google by kccqzy on Wednesday May 13, 2026 @05:13PM (#48127662)
There is an internal website that tracks statistics of tool use, where “tool” is defined liberally and includes emacs. It would be tracked if you just (require 'google) somewhere in your initialization code.
Re:A History of IDEs at Google by top_coder on Wednesday May 13, 2026 @05:26PM (#48127858)
Famously Jeff Dean uses emacs. Emacs integration to internal systems (source code, code search, LSP, build, etc) was super solid when I was there ~2020.