Author here: yeah the end result is that you wouldn’t actually want to do it in practice. Who wants to build a load of linear algebra into GHC, after all? But it was pleasing to show that you could make the algorithm subcubic if you really wanted. to.
I think something that's probably under appreciated if you don't read/write Kanji– bad penmanship is incredibly hard to read due to the complexity of the characters. Good penmanship is extremely valued in Japan, so that need for precision tends to bleed over into an overarching valuing of stationary and related accessories.
Author here: I think you are projecting quite a bit. We do in fact hire a lot of people who maintain things, and even pay quite a lot for OSS development on things like the compiler and libraries we care about. But we still have business objectives to achieve, and sometimes it makes more sense to write things that better suit our needs.
Author here: I have a bunch of drafts that I haven't gotten around to publishing for quite some time, and I'm on parental leave, which affords me a little more time than usual to get things published. I don't have a lot of additional ideas left in the tank.
Well, I didn't get LLM vibes from it at all, and the article is deeply relevant to the engineering I am working on at the present (migrating a monolith to a highly event-sourced workflow-based distributed application), and I deeply appreciated this work!
Funny how that guy claims to be able to spot "sensationally dramatic contrasts" yet doesn't understand the concept of drafts, or saving writing for later.
Too many smartasses commenting on the skills (or lack thereof) of others just because of "AI".
I'm not really sure why you'd say that OpenAPI isn't a JSON Schema document: there are published JSON Schema files on the official OpenAPI website.
See for example:
I set up spec-kit first, then updated its templates to tell it to use beads to track features and all that instead of writing markdown files. If nothing else, this is a quality-of-life improvement for me, because recent LLMs seem to have an intense penchant to try to write one or more markdown files per large task. Ending up with loads of markdown poop feels like the new `.DS_Store`, but harder to `.gitignore` because they'll name files whatever floats their boat.
I usually just use a commit agent that has as one of its instructions to review various aspects of the prospective commit, including telling it to consolidate any documentation and remove documentation of completed work except where it should be rolled into lasting documentation of architecture or features. I've not rolled it out in all my projects yet, but for the ones I do, it's gotten rid of the excess files.
First I hear of spec-kit, that looks very promising, I’m interested in trying it. My approach is to combine beads with superpowers skills
https://github.com/obra/superpowers I’m wondering how does it compare to this, gonna give it a try, thanks!
Probably. But it is important to understand that this will matter to fewer and fewer people over time.
Because they don't edit the data to make a new objective truth that survives scrutiny, they edit the data to demonstrate their power over data.
People referring to the archived data will simply be denied access to the conversation moving forward; "our opponents keep fighting old battles when the world has moved on".
It works. And it will continue to work shockingly well even when the underlying phenomenon asserts itself in ways that are predicted by the archive data. Look at how Florida is torn between climate change denial and the actual reality of sea-level rises affecting the Keys.
And there are plenty of people who can still be liked, or appreciated at least, who also were racist and misogynist, or whatever other moral defect you like. It's okay to show affection for someone who didn't perfectly fit the strictures of what a specific type of virtue signalling labels as correct.
On the contrary. My worldview has been and still is shaped by an ever changing learning curve of the world's nature. That includes being flexible enough to show some affection even for that which doesn't fit rigorous dogmas of conduct. Can you say the same about your labels?
To be fair, I absolutely would take ocean liners for this purpose if such a thing existed.
The closest that you can get on this front is basically seasonal route switches for cruise liners. The thing is, cruise lines price gouge on WiFi, so I'm not really able to work while taking the slow route, and I'm also having to pay food, lodging, etc.
The latency itself / limited freedom for a week or two, I don't mind. But it's the other expenditures and tradeoffs that are rather hard to stomach.
I mean this nicely, I don't really feel like anything on the landing page besides one paragraph is actually helpful to readers understanding what problem you're trying to solve.
I think it'd be useful to focus on this more:
> Voiden turns your API definitions and docs into dynamic, purpose-built interfaces — no fixed UI, no rigid templates. Everything is composed in one place and rendered down to Markdown, tailored to the API it serves.
Hmm, I appreciate this, for real. We'll have some more discussions on how to optimize the landing page.
Curious, how do you feel about the tagline stuff?
Happy to learn anything else you'd be willing to add here. We're all for making it crystal clear, no fluff, just making devs lives easier, which also means not wasting their time to understand whether they need it or not.
Not GP, but the tagline above the fold doesn’t tell anything related to the actual value prop. Modular, extensions etc are implementation details. Git-native? I had an “idea” of what that meant, but had to scroll down to confirm.
Not sure how else to reply to this one, but it is the same thing as in its definition. Think less of client-server, think more of Postman, but without gazillion tabs and with docs at the same place with your API endpoint definition, headers, body, etc.
I just downloaded it and tried it and I still don't understand what it does.
It seems to be some kind of wysiwyg editor? With elements specific to API docs?
But then why does that make it an "API client". I'm guessing "API" specifically means HTTP API here. But "client" is completely throwing me. An API client is just software that talks to an API. So what's with the wysiwyg stuff?
The Jupyter comparison isn't completely off base if you'd like to rationalise it that way. Similarity would be blending the code and the docs in a single file, where you can then also execute something.
By definition, API Client is a devtool that makes it easier for devs (& co.) to design, test, document, and debug APIs. If it's confusing, we can take it to Postman, but it's an industry standard, been that way for a long while.
> By definition, API Client is a devtool that makes it easier for devs (& co.) to design, test, document, and debug APIs. If it's confusing, we can take it to Postman, but it's an industry standard, been that way for a long while.
That's not the definition of "API client" I'm familiar with. In fact it feels like a very specific definition of "API client" - which is a broad term that I am familiar with.
(Why does it sometimes feel like I am not getting the memos that everyone else is getting? It's like when a new job description for an old job suddenly appears and everyone pretends that what it's always been called!)
Maybe you thought of an SDK-like client/wrapper for calling certain APIs, so it sounds natural to call it an API client?
Here you can check a list of currently OSS API clients (competitors to Voiden - the tool I posted about) https://github.com/stepci/awesome-api-clients Will join the list soon after we go OSS too. :)
I guess "API client" is often shorthand for "API client library" but that seems less of a stretch than using it to mean "App for calling, testing and documenting an API". A quick Github search seems to indicate that the former usage is more common in any case.
It's an expression. Meaning it's not just allowing you to use some git sync workaround, but actually use it as if you would in your terminal, respecting all of its commands and conventions.
reply