ghukill

Hear hear!

> I see a glint of the next evolution - mostly small, independent, human-centred (perhaps AI supported). It's tiny right now, but there's a good chance that the specific future I'm thinking about is already here just not evenly distributed yet.

This. AI has helped me realize some really engrossing and satisfying coding projects I may have otherwise not done. The flip side is that they wouldn't have worked if business-as-usual / do-same-but-faster-with-AI was imposed upon me.

Use of AI can be highly personal and symbiotic, just as it can also be dehumanizing and parasitic.

I look forward to new ways of working both individually and structurally that yet may emerge, and it will require creative elbow grease to materialize.

I also empathize with, and support, those that feel the experience has shifted beyond something they care about, enjoy, or want to participate in. As I'm sure we all do, I have very good friends who lead very different lives from me. AI can be seen negatively as a wedge, or perhaps more positively as a tech/pasttime/activity that we yield in unique ways, making (keeping!) unique in the process.

If interested in WARC, recommend also checking out WACZ: https://specs.webrecorder.net/wacz/1.1.1/

>> "Hell, at this point, GPT-3 is probably a better approach to knowledge processing than trying to piece together something actionable from a half baked information graph born of old programmers' utopian fever dreams."

Greatest thing I've read on HN. As a librarian and developer, can confirm. At least in most cases...(slipping back into fever dream)....

I don't miss the assumption that all developers are "guys".

And one hundred thousand people finally just got a good night's sleep...

I would propose a potential user as someone interested in some of the meta considerations and patterns of statistical reasoning, aka machine learning. There are is a vast amount of particulars the second hand on my watch operates (e.g. vibrating quartz, digital), but I can use that mostly reliable device to investigate higher level phenomenom, like calculating distance of planets by timing their movement. This library opens a direct line to these algorithims such that one might intuit, and apply, their high level behavior; as I could not time planets if consumed with the fidelitity and reliability of resonating quartz, it would slow my ability to explore this kind of reasoning if concerned with the minutiae.

That said, all points taken. If this sparks interest in someone, as is stands, it would be on them to dig in to all the considerations you've outline.

I love it. Pasted in the column headers to `iris.data` from the Iris website. Voila, up and running per instructions on Github. For prototyping / exploring ideas, for the syntactical layman, but conceptuallly familiar, what a boon.

Are there queries that SPARQL can perform over a triplestore that cannot be done with SQL over normalized data? Perhaps not.

But data normalization to that end is a moving target, while a bag of subject-predicate-object statements are quite doable. This, I believe, is a uniquely powerful characteristic of linked data / graph query languages and protocols.

To that end, agree with the comment above that GraphQL is mighty exciting.

Let the record show - this is how people will "bookmark". It's bringing in marked up data from the page, effectively treating websites as little interesting nuggets of data. We won't don't save links to aggregators, we save links to articles, nuggets. The UI is clunky, but it'll get better. Hierarchy is toast, and doesn't scale, welcome to your bag-of-visited-memories-websites-past.