lostintangent

10 ms·

91.
by lostintangent 7y ago
I’d love to hear more about your thoughts on draft tours! Currently, you can record as many tours as you want per codebase, and so you could record one that was scoped to just key API calls, and have n-number of other ones with more detail,
92.
by lostintangent 7y ago
Thanks for the feedback! In addition to CodeTour, I’m in the process of building out a couple of other tools (see below) to support better team collaboration, onboarding and knowledge retention. So I’m focusing on VS Code first, and iterati
93.
by lostintangent 7y ago
Trying to codify the “tour” that a developer would have to otherwise discover themselves, is exactly what I’m trying to help with. This just seems like such an important phase of learning, that is currently way too manual. Regarding the com
94.
by lostintangent 7y ago
Thanks! I took inspiration from the way I’ve seen some devs “document” their PRs: submit the PR, add a description, and then seed the PR with a handful of comments that call out the most relevant “markers” for reviewers to look at. I’ve alw
95.
by lostintangent 7y ago
I’m working on a tool that allows developers to record and playback interactive, guided walkthroughs of a codebase, directly from their editor. It’s called CodeTour, and it’s currently available as a VS Code extension: https://ak
96.
Show HN: Record and playback interactive walkthroughs of your codebases(twitter.com)
7 points by lostintangent 7y ago|1 comments
97.
by lostintangent 7y ago
Correct! We designed LSIF to be a complement to LSP. LSIF is basically a way to persist language server state, so that LSP queries (e.g. what are the definitions for this symbol?) can be answered without needing an active LSP server running
98.
by lostintangent 7y ago
Hey! I definitely remember you :) It’s always satisfying to run into the same folks across different projects, over the course of multiple years. I’m glad to hear the examples worked out of the box! We’ve been iterating on the docs and API
99.
by lostintangent 7y ago
Low/no-code authoring is definitely something we’re interested to explore. Once we’ve solidified the core Playwright library, we plan to build (and collaborate with the community on) tools that can simplify automation tasks even furthe
100.
by lostintangent 7y ago
Playwright allows you to connect to existing browser instances, but it currently requires you to get the “debug URL” of the browser instance first: https://github.com/microsoft/playwright/blob/v0.11.1/doc
101.
by lostintangent 7y ago
Out of curiosity: why does the fact that Playwright is a Microsoft-sponsored OSS project discourage your interest? The team is working very hard to be open/transparent/available ( https://github.com/microsoft/p
102.
by lostintangent 7y ago
As part of our goal to enable better developer ergonomics, we’re very keen to explore “better”/higher-level APIs and additional extensibility points. For example, we allow you to define custom “selector engines” ( https://git
103.
by lostintangent 7y ago
Great! Let us know if you end up having any questions/comments/feedback: https://github.com/microsoft/playwright .
104.
by lostintangent 7y ago
Desktop support is definitely on our long-term roadmap! We’re simply starting web, since it’s an area we think we can make big improvements to, before moving on to the broader developer landscape. As we build out Playwright, we hope to lear
105.
by lostintangent 7y ago
Awesome! Please don’t hesitate to let us know how we can improve. We want to make web automation not only more reliable, but also more enjoyable. So we’re keen to hear how we can continue to push that goal forward :) https://gith
106.
by lostintangent 7y ago
Each of the page operations (e.g. click) automatically wait for the specified element to become visible before being performed. That way, your automation code is declarative about what you want to do, and to what element(s), and you can all
107.
by lostintangent 7y ago
Playwright is a new alternative to Selenium, and besides being cross-browser, is focused on performance, developer ergonomics and reliability (death to flakiness!). Might be worth checking out? https://github.com/microsoft&#
108.
Show HN: Taking interactive programming tutorials within VS Code(twitter.com)
5 points by lostintangent 7y ago|0 comments
109.
Show HN: Creating Interactive D3 Data Visualizations Within Visual Studio Code(twitter.com)
3 points by lostintangent 7y ago|0 comments
110.
by lostintangent 7y ago
Yep! You can run the “GistPad: New Secret Gist” command, or right-click the “Your Gists” node in the Gists Explorer and select “New Secret Gist”. Let me know how that works for you! “Secret” is the term that GitHub uses (as compared to a pr
111.
by lostintangent 7y ago
If you’re using VS Code, you can checkout GistPad, which allows managing code snippets, mini-docs, and interactive/CodePen-like playgrounds, all backed by GitHub Gists: https://aka.ms/GistPad . Disclaimer: I built GistP
112.
by lostintangent 7y ago
Thanks! Let me know if you get a chance to check it out, and have any feedback ( https://github.com/vsls-contrib/gistpad ). I’m iterating on it pretty quickly, and am looking for more input about other developer’s use ca
113.
by lostintangent 7y ago
If you’re interested, I built a snippet manager for VS Code that uses GitHub Gists for persistence. That way, you get a productive, in-editor experience, while still being able to keep your own data/code, and can benefit from the exist
114.
Show HN: Browse and edit CodePens entirely within VS Code(twitter.com)
8 points by lostintangent 7y ago|0 comments
115.
Show HN: Using VS Code and GitHub Gists as a Web Development Playground(twitter.com)
10 points by lostintangent 7y ago|0 comments
116.
Show HN: VS Code + GitHub Gist = Developer Micro-Blogging (aka a “GistLog”)(dev.to)
1 points by lostintangent 7y ago|0 comments
117.
Show HN: Live Share Spaces – A Virtual Team-Room Within VS Code(marketplace.visualstudio.com)
5 points by lostintangent 7y ago|0 comments
118.
Show HN: GistFS – Using VS Code and GitHub Gist as a Cloud-Based Scratchpad(github.com)
8 points by lostintangent 7y ago|0 comments
119.
by lostintangent 7y ago
Yes to #1 and #2. For #3, we’ll be adding a “Basic” SKU soon, that includes 2 cores and 4 GB RAM. Would that be sufficient for your use cases? You can track the progress of this enhancement here: https://github.com/Microsoft
120.
by lostintangent 7y ago
Correct. Though we’d love to hear feedback on this experience.

More ›