ppezaris

Worth mentioning that the author speculates that this happens not for a nefarious reason, but in a binary tree search to locate your zoom cookie.

author here.

CodeStream aims to simplify and amplify your code review process with the following changes:

  - all in-ide
  - open source
  - cloud or on-prem
  - supports vscode, vs, atom, jetbrains (more soon)
  - end-to-end workflow tool
    - grab a ticket from trello/jira/etc. and it'll create a branch for you
    - while you're editing, comment on code without having to copy/paste to slack/etc.
    - get feedback on a wip with press of a key (codestream packages diffs for you)
    - teammates request changes? amend your review
    - when you're ready, create a pr on github, gitlab, bitbucket, and merge.

any feedback appreciated.

About 20 years ago I slept an average of three hours a night for three years straight. No ill effects that I could discern. Just another anecdote; not suggesting that the plural of anecdote is data.

The main missing feature, and the one that enables rich integrations, is a webview.

oh my sides.

Find a partner and start a business where the value you create from writing software accrues to you, rather than to the firm who hired you to write code.

Thanks very much! Let me know if you have any specific feedback about it.

Thanks for the feedback.

Noted!

there's one other aspect i've learned from having built and studied communications systems over the last two decades, which is that you shouldn't underestimate how many edge-cases there are when barriers are reduced.

in 2004 nobody shared photos of their lunch with their friends, not because it wasn't possible, but because it wasn't easy. last week i witnessed a teenage girl in a restaurant spend the entirety of a 30-minute dinner taking and sharing selfies. perhaps 100 in total.

it's my sincere hope that a reduction in friction gets us all talking about code more often.

if we do nothing else, i hope we can improve lack of documentation/comments for some people, with one simple enhancement: allow you to ask a question.

currently, all code comments are declarative, requiring you to pay into the system now, not knowing if anyone will ever benefit from your effort.

with question-driven comments, you get answers to exactly those parts of the codebase that aren't clear, as it should be.

well that's the hope anyway.

We do plan to include what support we can in vim, given the limitations of the UI. It's certainly one of our most-requested editors.

Quick question on vim usage. Do you live in your terminal, and fire up vim, edit the file, and quit? Or do you leave your vim process running all the time (or nearly all the time)?

Yes, absolutely. I made this short video to demonstrate how: https://www.youtube.com/watch?v=D4HCiiQvMuY

VS code is available now. Other editors to follow, based on the great work of the LSP project. https://langserver.org

Which one?

Thanks! We implemented codestream with a rather unique 4-tier architecture which we hope will make it easier to port to many editors.

React UI

Editor extension (initiates webview)

LSP agent

——cloud or on prem——

API/mongo

Hopefully this means most of the work happens in the three layers that are common across editors, and only the extension code needs to be ported.

What am I missing? You seem to be taking the YC-specific unicorn numbers and dividing them by the much broader A16Z "fundable" numbers. Apples & oranges, no?

We're actively looking into it using docker. Would that work for your infrastructure?

In approximate order: vscode, atom, visual studio, jetbrains (intellij, webstorm, etc), sublime.

We also plan to publish our marker API so that fans of a particular editor will be able to create a client, should they be so motivated.

Hi, I’m Peter the CEO of CodeStream. I’ve been an internet entrepreneur for the last 23 years and I am very fortunate to have worked with the same management team during that time, with two eight-figure and one nine-figure exits under our belts. Commissioner.COM (now CBSSports.com) was the first to bring fantasy sports online. Multiply introduced the first social network news feed. And Glip, which launched the same month as Slack with a very similar product, is now the app serving RingCentral’s nearly three million paying customers. These three companies all had something in common, which is enabling group conversation and collaboration at scale.

Understanding code is one of the hardest problems in software development. At CodeStream, we think we have a novel approach to address this by first making it easier for developers to talk about code, and then capturing those code-based conversations and homing them where they belong -- with the code.

How we deliver the first phase of this functionality, and why we think it’s important, is outlined in the link above.

[sorry if you saw this yesterday; I had a glitch in posting it the first time]

Thanks for the post and the questions! CodeStream CEO Peter here.

1) from the teams we speak to, code review is generally a somewhat formal process, and almost always involves code that is changing in the current sprint. with codestream, we want to enable continuous collaboration by making it possible to comment on (and soon create an issue on) any block of code at any time, whether it changed this sprint or not. so rather than trying to compete head-to-head with code review tools, we see codestream as complementary. with integration possibilities, perhaps even more.

2) the major difference between github PR comments and codestream-enabled comments are that a) codestream is in-editor (although there are some early plugins for PRs now), b) codestream is real-time (as compared to the email-like transactional semantics of web-based comments), but more importantly c) codestream comments allow you to talk about any part of the codebase at any time, not just what's changing in a given sprint, and d) codestream comments don't get buried when the PR is merged, they persist as annotations on your codebase even as your code changes. we're excited to see how this enables new modes of communication about code, although to be honest we don't yet have an idea what % of discussions that will represent. we hope a lot!

3) in the beginning, it's all human-driven. the next phase will introduce integrations with defect tracking tools such as trello, jira and asana, so that you can more easily create an issue on a block of code you're looking at in your editor. the third phase will be bot-driven or system-driven alerts which, given our integration into the editor, will be able to preserve context (repo, file, line, range), and optionally persist, and therefore hopefully become more powerful.

relevant: https://news.ycombinator.com/item?id=9076788