Hope you don't mind, but as others are pointing at wiki type sites, I'll plug my own (also using Vercel and cursor)...
https://ont.fyi it's a work in progress ... feedback wanted (no matter how painful), focusing on enabling adding in your own data at present, lots of ideas and work to be done
It will probably really wind the old git up reading that despite all he his best efforts, I never even realised it wasn’t allowed, wanker (that’s just in case he reads this)!
Problem with VSM, is where is the practical evidence of it working, if it's so great surely there would be more uptake of it?
I mean it sounds like a reasonable model, I'm sure there is a lot of nuance to it, but getting it up and running at an existing enterprise would be a very difficult to do, and at great risk without some solid case studies showing significant ROI.
next.js reminds me of Ruby on Rails, main pain point is they keep changing how they do things, but docs, examples etc can't keep up so I'm constantly seeing the wrong answers to my problems.
An example of this is how they implemented sitemap.xml, but half arsed doing a sitemap index properly (which really wasn't much work), so they will end up doing it properly in some version, in the mean time you have to work around the framework (it would be better if they didn't even have this feature), and when the release a proper implementation new users will struggle to find the answers on how to do it.
This all adds friction to upgrade, I'd like to move to v15 as it has a feature I really need, but they have changed the bloody confusing caching system, not sure it's worth the work. Creating web frameworks that are volatile is fine if your just building short lived projects, but not anything more complex and longer lived, this is the same pain and why I gave up on RoR.
Only Ruby-on-Rails was kinda good for some time. Next.js is one of those frameworks which put all of their stat points in Thought Leader Marketing and none in solving problems.
I would argue that Next.js pre app router was a solid and helpful framework for rendering React components on the server side (as long as your setup wasn’t too complex or you were using their own hosting service anyway). But in the recent years they really seem to have screwed up the ease of use and reliability. Nowadays, I wouldn’t recommend Next.js to anyone anymore.
What would you recommend? I’m building a fairly complex app with lots of state management. Next seems to be a good way to go, but I’d be interested if there are any better alternatives.
Just use react.... That's what I do - it is so much easier than trying to fight with Next.js.
I have a large application and I use next.js for the landing pages (landing, tos, privacy, blog, login, etc..) - but for the core application after login, I just use vanilla react with react router. For me I keep these as separate applications as I don't want to load the entire app just for the landing page or login box.
Every time I need to work in the nextjs part of the app I always run into problems and have to read the docs and troubleshoot, sift through which part of the docs apply to my setup versus the app router.
If your entire application needs to be indexed as a static site (e.g. content based versus a web application), then vanilla react isn't a good fit - so it depends on your needs.
Unrelated - but shout out to https://nx.dev. I always prefer using this for all of my projects - made it super easy to have my node backend, react frontend, nextjs landing page, chrome extension, cron jobs, etc.. all in the same codebase where I can share code between all of them via non-publishable libraries.
This approach doesn't work if you need to SSR any of the content of those components.
This is also a terrible solution UX wise. Your users will see some content and after some time (more or less noticeable, depending on resources, network conditions, etc) the rest of the components start to pop up, cause layout shifts and overal jankiness.
You either use and embrace one of these frontend frameworks or you don't and do progressive enhancement using HotWire, Alpine, Unpoly, Livewire or whatever.
The sprinkling of components is the worst of both worlds.
We may be talking about different things. I don't mean that you literally serve it as a static site, I'm illustrating React is just a view library.
The comment you responded to was about not needing NextJS and you said it's impossible to just use React if you need multiple pages or need SSR.
How so? You can have an MPA with React. If you have a server (Even if it's not NextJS) then you can do SSR. Then you can hydrate with React and manipulate as needed. This is what NextJS does.
I didn't interpret the OP to be saying "You don't need a server."
The approach is not to capture all pages you view, rather you can add the pages etc you want in order to reduce the amount of noise/rubbish. It constructs a knowledge graph from these documents, and then a graph rag approach ontop to enable chat.
The core graph is based on wikidata, you can have your graphs either private or public if so they are published like those you can see on the site now.
Lots to do, but making ing good progress, if this sounds like something you might want to use please sign up.
After debating for a few days, I joined the waitlist. My Gmail username is the same as my HN username.
The website does a poor job of conveying what the product is exactly, which is the reason that I did not sign up sooner. You might want to approach the text of the site from the premise that the user has no idea what you are presenting.
Thanks for the feedback, and for joining the list.
I agree with your points, my plan is to get a basic version in front of some people and shape it on their feedback. Plan to have it available in a couple of weeks.
It’s not AI, it’s a collection technologies and practices within the domain of AI, symbolic and sub symbolic. Arguably classic search is another technology/approach/algorithm with the domain of AI.
