st_asqi

6 ms·

1.
by st_asqi 2y ago
10 hours up and no comments? For shame, it's a good tool! I'm not a natural user of this product and have never used any snippet tools, so I'm commenting as an outsider. But I really like several things you've done: 1. H
2.
by st_asqi 2y ago
Nope still there, but you may have caught the server at a bad moment. Because Asqi uses the DB read/write, there's only one replica of the server and it has less than 100% uptime depending on indexing and user load.
3.
by st_asqi 2y ago
Looks like there's a grammar for it ( https://github.com/fwcd/tree-sitter-kotlin ) so I think it's on the table!
4.
by st_asqi 2y ago
Awesome, OK I believe I can make that work then. Very glad you mentioned Sorbet because I hadn't heard of it before but it will be cool to have it ship with Ruby out of the gate.
5.
by st_asqi 2y ago
For Ruby + Sorbet, it looks like Sorbet fits into Ruby syntax so we can reuse the same grammar, but you'd probably want the signatures to be considered as part of the methods. Working with the example from their website: sig {param
6.
by st_asqi 2y ago
Yeah the locking up is a big issue right now. It happens when you first load a repo and the client populates its local IndexedDB with all the RPC data coming down, which is 10-100k insertions and causes browser slowness. I've tried a c
7.
by st_asqi 2y ago
Hahaha "if it doesn't cause seizures, it's not really Asqi" - well we have a brand, that's for sure :) (seriously I have got to fix this soon my god) TTE is so freaking cool, I will hate myself if this doesn't
8.
by st_asqi 2y ago
This is absolutely constructive feedback, thank you again for writing it all up. I'll go through point by point and share my thoughts about each one. Re speed and compactness, thank you! These are two things I really value in UIs, and
9.
by st_asqi 2y ago
You're very welcome. I wanted to build a product I would use, and being hands-off about customer data is a big part of that. (I was trying to use another code search tool and bailed because it wanted me to sign into Github just to use
10.
by st_asqi 2y ago
YES - this was very much on my mind actually. I was thinking we really need section outlining for Markdown (and for diffs etc, so like "two people want to edit this paragraph" when we have collision detection later). It didn'
11.
by st_asqi 2y ago
Terminal over ssh? Hahaha don't tempt me :) I really like this idea. It's not at all what I had in mind for the product, but that's because it had never occurred to me. I'm going to give this some serious thought and see
12.
by st_asqi 2y ago
Thanks so much for writing this up, it's great! Let me get some coffee and I'll share some thoughts about where we are and where it's going.
13.
by st_asqi 2y ago
I wanted to say, this is really thoughtful comment and thank you. I love getting ideas like this about the business model and product/market fit. The second half of the product is a lot more about everyday features e.g. "whose bra
14.
by st_asqi 2y ago
Yeah you definitely don't need to install anything. I don't know how to deploy React apps apparently (will try to fix), but it's just a regular website and I would never ask users to expect anything else. Update: it's be
15.
by st_asqi 2y ago
Got it working again! Sorry about that, server crash possibly from being on HN :)
16.
by st_asqi 2y ago
It's actually pretty straightforward; we use tree-sitter for parsing and it takes me about 2-3 hours for each language. So I'm planning to add a lot more in the near future. If you have any that you find especially valuable, let m
17.
by st_asqi 2y ago
Hi, thanks for trying it out! The server crashed, sorry about that. I need to add a liveness check. It should be working now. As for comments asking to install React, it's a bug on my end. Create-react-app leaves a manifest.json file i