pastelsky
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.
Pretty Fish: A better mermaid diagram editor
Atlassian acquires DX, a developer productivity platform for $1B
It’s 2024 and it doesn’t really work!
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
> 3. Relative links to things like CONTRIBUTING.md currently break Yeah, this is known, thanks! https://github.com/pastelsky/tsdocs/issues/9
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.
TSDocs: Type Documentation for JavaScript Packages
Tsdocs.dev: rustdoc style documentation for JavaScript libraries
So you don't have to rely on library authors to provide upto date reference docs for different versions of their library
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?
https://github.com/pastelsky/network-idle-callback
Helpful for progressively hydrating features in a page, or loading assets for next interaction
I wonder if processing emoji characters has any different performance characteristics than other UTF characters.
WhatsApp is now a spammers’ paradise in India
Configuring JavaScript tooling is a mess
Configuration management in JavaScript tooling ecosystem is broken
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.
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've become so used to suffixing these queries with "forum" or "reddit" to get articles written by real humans.
Ask HN: How flaky are your builds?
For those who work on large monoliths with > 50 active developersMaintaining master build success rate above 80% seems to be a big problem at this scale.More processes and check help, but only to an extent, and have side effects.I'm interested in hearing what percent of feature / master builds you run are flaky?How does your build champions ensure that a failed build doesn't end up blocking...
ITs going to have a tough time justifying purchases.
In some cases, actors that make such unscrupulous content viral can have as big or bigger part to play than the content creator themselves.
Content becomes more dangerous the more viral it becomes — the content creator usually has little control over virality, and is usually not the most "popular" figure in the chain.