【Hacker News搬运】启动HN:Haystack（YC S24）-在无限画布上可视化和编辑代码

hackernews

Title: Launch HN: Haystack (YC S24) – Visualize and edit code on an infinite canvas

启动HN:Haystack（YC S24）-在无限画布上可视化和编辑代码

Text: Hi HN, we’re Akshay and Jake from Haystack (<a href="https://haystackeditor.com/">https://haystackeditor.com/</a>). Haystack re-imagines the IDE by putting it on a 2D digital whiteboard that automatically draws connections between code as you navigate and edit files. We designed it to match our mental model of how code works – as a graph of connected components. Here’s a demo of what it looks like: <a href="https://www.youtube.com/watch?v=5XADctpWNNs" rel="nofollow">https://www.youtube.com/watch?v=5XADctpWNNs</a>. You can download Haystack from <a href="https://haystackeditor.com/">https://haystackeditor.com/</a>.We used to work as software engineers at big companies, and when the explosion in AI code-generation tools started we were really excited about them. They gave us a huge speed boost in our day-to-day work. But something was missing: writing code had become easier, but navigating codebases remained painful. We found that we were spending more time on the latter than the former!Our vision of Haystack is an IDE that helps you navigate your codebase at speed. You should be able to type a vague description of the code you’re looking for (“Show me the code flow that triggers after we click the submit button”) and immediately see the right result. But we don’t think the traditional split-panel interface is the best fit for this type of rapid navigation. Inspired by the fluidity of design tools like Figma (Akshay used to work there!) and Miro, we realized that the canvas layout is a perfect way to represent and operate on code flows, and a great base for all the AI and collaborative tooling we want to build! This is how Haystack was born.You might have seen our original Show HN (<a href="https://news.ycombinator.com/item?id=41068719">https://news.ycombinator.com/item?id=41068719</a>) about two months ago. Since then, a ton of our users have told us that they’d love to contribute. We’ve made the decision to make the editor source-available so that folks can make contributions and so that they can examine the code to make sure they can trust it. Our repo is at <a href="https://github.com/haystackeditor/haystack-editor">https://github.com/haystackeditor/haystack-editor</a>.If you’re wondering why we’re going source-available rather than proper open-source: as a startup, we're going to eventually monetize and it’s too early for us to make the decision on whether going fully open-source is the right move. We want to own the distribution of Haystack until we can better understand the ramifications that open-sourcing would have, and whether it’s sustainable business-wise. We’d love to find a way to make proper open-source work, but it’s a one-way door, so we want to take our time to make sure we’re making an informed decision.We would love to hear about what you think about having a canvas in your IDE and the role visualizations have to play in software development!

嗨，HN，我们是来自Haystack的Akshay和Jake（<a href=“https:&#x2F；haystackededitor.com&#x2F;”>https:&quot；haystackdeditor.com</a>）。Haystack重新构想了IDE，将其放在2D数字白板上，当您导航和编辑文件时，该白板会自动绘制代码之间的连接。我们设计它是为了匹配我们对代码如何工作的心理模型——作为连接组件的图。这是它的外观演示：<a href=“https:”www.youtube.com“watch？v=5XADctpWNNs”rel=“nofollow”>https:”&#x2F；www.youtube.com；看？v=5XADctpWNN</a>。您可以从<a href=“https:&#x2F；haystackceditor.com/”>https:&quot；下载Haystack&#x2F；haystackceditor.com</一p> 我们曾经在大公司担任软件工程师，当人工智能代码生成工具的爆炸式增长开始时，我们真的很兴奋。它们极大地提高了我们日常工作的速度。但缺少了一些东西：编写代码变得更容易了，但浏览代码库仍然很痛苦。我们发现，我们花在后者上的时间比前者多<p> 我们对Haystack的愿景是一个IDE，帮助您快速浏览代码库。您应该能够键入您要查找的代码的模糊描述（“显示我们单击提交按钮后触发的代码流”），并立即看到正确的结果。但我们不认为传统的分体式面板界面最适合这种快速导航。受到Figma（Akshay曾经在那里工作过！）和Miro等设计工具的流动性的启发，我们意识到画布布局是表示和操作代码流的完美方式，也是我们想要构建的所有人工智能和协作工具的良好基础！Haystack就是这样诞生的<p> 大约两个月前，您可能已经看过我们最初的Show HN（<a href=“https:&#x2F；news.ycombinator.com&#x2M；item？id=41068719”>https:&quot；news.ymbinator.com＆#x2F？item？id=41068719</a>）。从那时起，我们的很多用户都告诉我们，他们很乐意做出贡献。我们已决定提供编辑器源代码，以便人们可以做出贡献，并检查代码以确保他们可以信任它&#x2F；github.com；haystack编辑器；haystack编辑器</a><p> 如果你想知道为什么我们要开源，而不是开源：作为一家初创公司，我们；我们最终会盈利，现在决定完全开源是否是正确的举措还为时过早。我们希望拥有Haystack的分销权，直到我们能够更好地理解开源的影响，以及它是否是可持续的商业明智之举。我们很想找到一种方法来制作适当的开源作品，但这是一扇单向门，所以我们想花时间确保我们做出明智的决定<p> 我们很想听听您对在IDE中使用画布的看法，以及可视化在软件开发中必须发挥的作用！

hn link

Url: https://github.com/haystackeditor/haystack-editor

很抱歉，作为一个文本模型，我无法直接访问或执行网络请求来抓取外部网站的内容。不过，我可以根据提供的GitHub链接来描述该项目的可能功能和内容。

根据您提供的GitHub链接（https://github.com/haystackeditor/haystack-editor），这个项目可能是一个编辑器工具，专门用于处理文本数据。以下是根据项目名称和常见实践推测的可能功能和内容：

1. **项目名称**：Haystack Editor
   - "Haystack"通常用来指代一个庞大的数据集或信息源，这可能意味着这个编辑器旨在处理大量的文本数据。
   - "Editor"表明这个工具是一个编辑器，可能是用来创建、编辑、分析或整理文本内容的。

2. **可能的功能**：
   - **文本编辑**：基本的文本编辑功能，如格式化、拼写检查、语法检查等。
   - **文本分析**：可能包含文本分析工具，如关键词提取、情感分析、主题建模等。
   - **数据可视化**：可能支持将文本数据以图表或图形的形式展示，以便于理解。
   - **多语言支持**：如果项目是开源的，它可能支持多种语言，包括翻译功能。
   - **集成**：可能与版本控制系统（如Git）集成，方便代码管理和协作。

3. **内容总结**：
   - 由于我无法访问GitHub页面，以下是对项目可能内容的推测性总结：
     - 项目可能包含一个用户界面，允许用户上传或输入文本数据。
     - 用户可以利用编辑器的功能对文本进行编辑和格式化。
     - 编辑器可能提供一些高级功能，如自然语言处理工具，用于分析文本内容。
     - 项目可能包括文档或示例，说明如何使用编辑器的不同功能和插件。

要获取更详细的信息，您可以直接访问GitHub页面查看项目的README文件、文档、示例代码和用户评论。如果您需要将非中文内容翻译成中文，您可以使用在线翻译工具或服务，如Google翻译、DeepL等。

Post by: akshaysg

Comments:

t-writescode: So where does paying for it come in? This needs to make money in some way, right?

t-writescode: 那么，付款从哪里来呢？这需要以某种方式赚钱，对吧？

tracyhenry: This has been a great idea for decades. I want Haystack to be successful just like many other attempts. The early execution seems promising. And I suspect there will be many challenges (e.g. when it's hard to figure out caller/callee,, inconsistent UX preferences across developers, etc). Kudos for taking this on!Btw I've always thought that this is even more powerful when the screen estate is more infinite than a 2D screen (like in a VR headset).

tracyhenry: 几十年来，这一直是一个好主意。我希望Haystack像许多其他尝试一样成功。早期处决似乎很有希望。我怀疑会有很多挑战（例如，当很难找出呼叫者时，开发人员之间的用户体验偏好不一致等）。恭喜你接受这个 顺便说一句，我；我一直认为，当屏幕空间比2D屏幕（如VR耳机）更无限时，这甚至更强大。

WuxiFingerHold: I have nothing intelligent to say, just that I somehow love this idea very much. Somehow visualizing complexity of any kind, helping understanding and refactoring it, is what I constantly have in the back of my mind. Probably a dream of my subconsciousness that is looking for a solution for the complexity (mainly) at my work life.

WuxiFingerHold: 我无话可说，只是不知怎么的，我非常喜欢这个想法。不知何故，我脑海中一直在想象任何形式的复杂性，帮助理解和重构它。这可能是我潜意识里的一个梦想，我在为工作生活的复杂性（主要是）寻找解决方案。

faramarz: Very cool. I imagined my organizations entire codebase being mapped like this and across different frameworks and languages.I don’t know if I missed this in the video or if it’s not yet possible, but that’s a lot of manual work, so instead of connecting the nodes, give a simple bot to run in the repo folder to automate the visualization.It’s super cool and I’m adding to my watch list.If I were you, i’d target enterprise organizations or local municipalities IT groups who are going through or planning their digital transformations. They have a need for way-finding and sense making across legacy and new work.If you play your cards right, Salesforce will come knocking in under a year. I see a lot of compatibility with their vision and product offerings.

faramarz: 很酷。我想象我的组织的整个代码库都是这样映射的，并且跨越了不同的框架和语言 我不知道我是否在视频中错过了这个，或者是否还不可能，但这需要大量的手工工作，所以与其连接节点，不如在repo文件夹中运行一个简单的机器人来自动化可视化 这太酷了，我要把它加到我的观察名单上 如果我是你，我会针对正在经历或计划数字化转型的企业组织或地方市政IT团体。他们需要在传统和新工作中寻找方法和意义。如果你打得对，Salesforce将在一年内到来。我看到他们的愿景和产品有很多兼容性。

hyggetrold: Does this project take any inspiration from Light Table?Potential feature request - take the visualization beyond 2D. Really complex systems are usually an intricate graph (polite way of saying ball of yarn) and just visualizing in the 2D plane doesn't seem to cut it in my experience.I would love to have something like concentric spheres of visualization - boundary services on the outer layer, core/domain services in the inner layer.

hyggetrold: 这个项目是否从Light Table中汲取了灵感 潜在的功能请求-将可视化扩展到2D之外。真正复杂的系统通常是一个复杂的图形（礼貌地说是纱线球），仅仅在2D平面上可视化是不够的；根据我的经验，这似乎不合情理 我希望有类似于同心可视化球体的东西——外层、核心的边界服务；内层的域服务。