5 ms·
>”Histoire is a tool to generate stories applications (or "books").” What a clever naming scheme! Nobody reads stories or books anymore, so when they see the w
by dimmke 3y ago
>”Histoire is a tool to generate stories applications (or "books").”
What a clever naming scheme! Nobody reads stories or books anymore, so when they see the word “story” they’ll automatically assume you mean UX Story! This isn’t ridiculously confusing at all.
- nonethewiser 3y agoI assumed it was a writing tool that fit into a developer workflow. Git integration, build step, etc. And to be clear when I say write I mean like a novel or blog post. Like with the English language.
- dimmke 3y agoYeah I was being sarcastic this is bad
- nannal 3y agoThank you for helping me understand what this application is. I think,
- swyx 3y agothis is unfairly negative, Storybook started calling it stories and before them, PMs and UX researchers, to the point that it was an industry understood term long before Histoire came along. the overloading is unfortunate but happens all the time - we don't complain about "bug" or "fork".
- forward-slashed 3y ago"Bug" and "fork" are industry standard terms, "stories" are not. Plenty of frontend developers exist who don't know the term. Overloading is fine. Ambiguous use of an overloaded term is not. What is one to think of when they see words like "write", "stories", and God forbid, "book"? Storybook stories, of course.
- stevage 3y agoAgreed. So it's basically a tool for documenting components, with an obnoxious name. Even the use of french. Why French? Because it's really so exotic?
- the-printer 3y agoWho knows man, maybe it's their mother language or something.
- dmix 3y agoJust because you got confused by a headline doesn’t mean the copy on the website itself isn’t relevant to their target audience. I’m a front end dev and understood it immediately (you can infer the meaning/context from “powered by Vite”). At most you can critique the HN headline drawing in randoms, which is a legitimate complaint, but I don’t see a problem with their copy especially for a brand new OSS project. Marketing sites are usually an after thought that improve after the first year. Unless, you know, you think this new volunteer project should be selling you on using well documented component libraries or something.
- nwienert 3y agoI'm a frontend dev who is familiar with Storybook and I didn't realize this wasn't about publishing an actual book, even after clicking around to a couple pages, until I came back here. So yea it's pretty valid feedback.
- dcre 3y agoSame. I use both Vite and stories and it took me a solid 30 seconds of scrolling around to figure out what they were talking about.
- dimmke 3y agoI actually have to agree with the parent. They were right to take me to task. After all, Vite and Storybook are ubiquitous tools of the trade in front-end development, which is a domain of programming famous for its rock solid stable tooling and methodologies. Sarcasm aside, I actually do like Vite quite a bit. And I still think my main point stands that a framework that exists to document components co-opting the word “book” is ridiculous.
- nwienert 3y ago+1 forgot to mention I'm speaking at Vite conf, love Vite and still was confused heh