Author here - thanks for all the support (and bug reports)!
I built pretty.fish with the belief that Mermaid diagrams don’t have to look like they’re from the 80s and to avoid squinting at Mermaid diagrams that coding agents create in tiny windows.
Having them on canvas also makes it easier to keep a track of, and even visualize agent steps as and when they are are being taken (if you connect an MCP you get a pretty nice view of agent building its knowledge graph for eg for a problem).
Didn’t expect it to take off like this—there are still rough edges (pan/zoom, mobile), but I’m working on smoothing those out soon.
- Write Mermaid diagrams with a live preview.
- Arrange multiple diagrams on an infinite canvas.
- Group diagrams into multi-page projects.
- Better themes
UPI is great in terms of UX, but I don’t think it’s super reliable – especially big public banks go down all the time. The UPI base service had multiple incidents in the last 1 month too.
One would’ve thought that after looking at modern day computers that being able to run a wire through two computers being able to transfer data quickly, reliably, easily would be a 101 feature these boxes offer.
> 1. Track re-exports and cross-package references
This should already be tracked — play around with the member visibility widget on the sidebar for e.g. For convenience, I've inlined the types from re-exports, but might be a good idea to indicate they were re-exported.
Pointing to the canonical source can also limit the usefulness in a few cases (e.g. d3 is just a bunch of re-exports), and users may not care about internal package organization.
> 2. consider supporting the @packageDocumentation tag
Organizing by @category and @packageDocumentation should already be supported. e.g. See the functions in —
https://tsdocs.dev/docs/lodash-es/4.17.21/index.html
I created this because I found myself peeping inside type declaration files too often, and the only way to do that was by installing the package first.
tsdocs.dev helps you check the API surface of a good number of JS libraries and their past versions — usually a quick search away.
There's something powerful about speed and being able to answer questions in seconds that usually take minutes.
edit: The server might be overloaded with requests as we prime up our caches, but do visit back after HN's done hugging us to death.
You can show your support and help cover a part of server costs if this (or bundlephobia.com) saved you time.
If I understand correctly, the limited amount of "expressiveness" a quantum computer has restricts its ability to solve useful problems.
Couldn't you simply express useful problems as a function of problems that the quantum computer can already solve? Doing so might be extremely in-efficient, but give that there's so much performance leeway, it still might end up being similar to super computers of today?
Question: Is Vite really a serious tool built for production apps? The design decisions don't give me confidence.
As your app starts to grow, you'd definitely not want 1000s of modules loading in your browser.
Seems like something that gets you from 0-60 quickly, and becomes a pain after.
Similarly, the different choice of bundlers in development and production would well lead to difference in behaviour / hard to catch bugs.
I really like the defaults Parcel comes with, it is very quick to get started with Parcel.
However, the promise of zero config is made possible in part by "magic" (strange conventions), and by having configuration spread across multiple files (package.json, . parcelrc, custom plugins which for some grave reason you can't use until you publish them to npm)
I really wish Parcel had sane configuration — I want to like it so much, but alas, it falls pray to the pendulum effect.
I wish Google had a toggle switch that isn't slowed you real user generated content... Like filter out all sites that are in Alexa top 10 for the category, and just show geniune niche blogs and forums with rich informed discussions.
It's impossible to get accurate information about travel, hotels, locations. Results are often filled with listicle crap that each copy each other and contain outdated pop content.
I've become so used to suffixing these queries with "forum" or "reddit" to get articles written by real humans.
I built pretty.fish with the belief that Mermaid diagrams don’t have to look like they’re from the 80s and to avoid squinting at Mermaid diagrams that coding agents create in tiny windows.
Having them on canvas also makes it easier to keep a track of, and even visualize agent steps as and when they are are being taken (if you connect an MCP you get a pretty nice view of agent building its knowledge graph for eg for a problem).
Didn’t expect it to take off like this—there are still rough edges (pan/zoom, mobile), but I’m working on smoothing those out soon.