Hacker News Reader

Comment by hnthrowaway0315 | Hacker News Reader

I can't imagine people enjoying web based IDEs. I used to work for a company that has everything made internally, including IDE -- they used the same method OP described -- using VSCode on web. The experience is horrible.

I guess maybe it was fancy back in mid 2010s, but my experience was a couple of years ago.

View on HN

From the article: “ Cider was a light client that opened much faster than traditional IDEs. All the magic happened on a backend that indexes the entire codebase, so that all the data was ready whenever someone opened the webpage. ”

Sounds like all other editors were slow compared to Cider.

OK, this was probable me telling other people I have never worked in a large repo without telling other people that...

It is basically VS Code Web. Try https://vscode.dev/ to see how you feel. If you don't like it you won't like cider.

I have used something like that (mentioned in my original reply ^). It was even worse -- there were about 3-4 plugins available.

Basically that company (a well known social media company, not FB) tried to implement everything on their own. Infra is their own (kinda makes sense because it is so huge), IDE is their own, communication is their own (which has an interesting feature that if someone screen shares an internal doc, other people can click a link to access that doc, too, very useful).

I was very jealous about their tooling team (that's what I call real programming), but nevermind I quit after a few months due to some unrelated reason.

To be fair, that is a blessing. Large monorepos are a terrible idea.

I have always had this itch to work on some real life serious system programming projects, with the most recent wave OS kernels. I completed the MIT xv6 labs (a very small repo) and did a few Linux device driver labs (very large repo and it was the first time I experienced compilation time > 5 minutes).

I got burnt out after a while, so that kinda wrapped up my experience working on large repos.

thats just a large project tho? not necessarily a mono repo.

A mono repo doesn't necessarily mean large compile times, because it depends on the projects and their dependencies within that repo.

Large monorepos have tradeoffs that may or may not make sense for a particular use case. Google's monorepo--in its form as a monorepo, not just the software it contains--is one of its biggest assets and creates enormous leverage.

And an enormous set of problems that must be managed. But multirepos have their own set of issues, and which set of problems you want is highly situation dependent.

Pretty much. Also it’s not that slow and you can’t just checkout all of g3

It's not bad, but I also don't see the point. It always felt more cumbersome than using Vim, even laggy sometimes despite having a fast MBP.

Reply on news.ycombinator.com