davideweaver

davideweaver on Hacker News

Re:Show HN: I left VSCode to build an IDE to handle many projects/agen... on Wednesday July 29, 2026 @09:18AM (#49097138)

Will do. Thanks for the feedback

Re:Show HN: I left VSCode to build an IDE to handle many projects/agen... on Tuesday July 28, 2026 @11:00AM (#49084977)

No, sorry. I wasn't involved with the VSCode team. I was just a hard-core user. Bad wording :(

Re:Show HN: I left VSCode to build an IDE to handle many projects/agen... on Tuesday July 28, 2026 @10:36AM (#49084613)

yes, worktrees can manage that. there is full support for worktrees in Silo, whether the agent creates them or you manually create them for the workspace. worktrees show up in the file explorer and the git explorer

Show HN: I left VSCode to build an IDE to handle many projects/agents workflow

Posted by davideweaver on Tuesday July 28, 2026 @08:21AM
from the show-hn dept.

https://github.com/silo-code/silo

VSCode was my daily driver for years, but once I started running several coding agents across multiple projects at the same time, it got in the way. One workspace with terminals in the bottom tray, no idea which agent was doing what and I found myself needing all the code editing tools less and less.So I built my own IDE around that workflow. Terminals are a first-class citizen, every project...

( Read More... | 7 comments | 8 points | on HN )

Show HN: Chalk: a Mac app for technical diagrams with a built-in MCP for Claude

Posted by davideweaver on Tuesday July 21, 2026 @04:45PM
from the show-hn dept.

https://chalk.appkit.studio

Hey HN. Here's a Mac app I'm working on for making diagrams. It comes with an MCP server so Claude can make and edit diagrams directly. Still in progress, but I'd love some feedback.

( Read More... | 1 comment | 4 points | on HN )

SlipScript: First Server-Side Scripting?

Posted by davideweaver on Tuesday October 23, 2012 @11:42AM
from the daveweaver.net dept.

http://daveweaver.net/personal/slipscript/

( Read More... | no comments | on HN )

Re:You Really Should Log Client-Side Errors on Wednesday April 04, 2012 @08:54AM (#3797299)

There are definitely a lot of issues to overcome when logging errors from a javascript client (as pointed out in the comments to this post). Regardless, the information you can get from it can be really helpful and you should be doing it.

One of the problems we find with js errors is that they don't contain a lot of information by themselves, especially when you're just trapping window.onerror() with minified source. We like to augment the client-side errors with server-side errors/activity as well. If your logging solution supports being able to track errors and activity by a session (username, ip address, etc) you will have a much better time tracking down what caused a specific js error. Putting all the pieces together gives a much better picture.

Try a logging solution that enables you to track more. I run loggr.net, so I am partial to that, but there are other good solutions out there like newrelic.com, loggly.com.