I’m gonna send you a reply to your article some time later. I am too tired right now.
My short review is that you want to separate the backend from the frontend. Backend processes your request and emits a JSON response. Frontend, be it CLI, web client or a smartphone app, just sends your request and shows the response in a human-friendly way. I did it in a similar fashion for my project.
I just looked up into my search history and saw I am either:
not confident with the website address I remember;
looking for an API documentation;
looking for some real-world projects (when choosing one of several frameworks/ways of doing things);
confused AF and needy for hints (especially for large problems or life/long-term choices);
looking for images/visual ideas;
looking for what my old friends do now (am I a boomer?).
Well, for the last two I cannot think of any solution. Problem (2) can be substituted with in-reference search (cppreference.com, lib.rs, docs.rs, developer.mozilla.org). However, sometimes I want to be sure that I am using the real link to the real thing, not the scam one. For example, I sometimes want to get access to the official latest GLSL specification, or sometimes overhyped people tend to name things by their marketing brands. Like, I ask ‘What is X?’ (WhatsApp, for instance) and I get a response ‘X is … just X, it’s really good’ and when I need to find what is X, I usually search on Wikipedia, because on the web search I would only see the promotions of X.
Excellent post, and I love your sites minimal, old school design. I finally found the right corner of the internet where people actually think about this kind of thing! It’s so frustrating how over the years search engine results just give you bloated, pointless articles that exist only to rank high in SEO and get ad revenue.
I too have been using the site:reddit.com method, but it sucks to essentially only have one for-profit website as the one I use to research things.
I made a blogpost about that, and I promise you’ll see no ads, no cookies, no JavaScript, just the blogpost.
I’m gonna send you a reply to your article some time later. I am too tired right now.
My short review is that you want to separate the backend from the frontend. Backend processes your request and emits a JSON response. Frontend, be it CLI, web client or a smartphone app, just sends your request and shows the response in a human-friendly way. I did it in a similar fashion for my project.
I just looked up into my search history and saw I am either:
Well, for the last two I cannot think of any solution. Problem (2) can be substituted with in-reference search (cppreference.com, lib.rs, docs.rs, developer.mozilla.org). However, sometimes I want to be sure that I am using the real link to the real thing, not the scam one. For example, I sometimes want to get access to the official latest GLSL specification, or sometimes overhyped people tend to name things by their marketing brands. Like, I ask ‘What is X?’ (WhatsApp, for instance) and I get a response ‘X is … just X, it’s really good’ and when I need to find what is X, I usually search on Wikipedia, because on the web search I would only see the promotions of X.
(I’m out, wait for chapter 2)
omg i love your blog theme/layout
nice work
Excellent post, and I love your sites minimal, old school design. I finally found the right corner of the internet where people actually think about this kind of thing! It’s so frustrating how over the years search engine results just give you bloated, pointless articles that exist only to rank high in SEO and get ad revenue.
I too have been using the site:reddit.com method, but it sucks to essentially only have one for-profit website as the one I use to research things.
Thanks! Stay tuned because I’ll probably add some kind of webring to the blog soon
Full text RSS would make it even more readable!
Finally got it working, but it’s a little hacky. It works in my two RSS readers, can you confirm it works for you too?
Works great! Thank you!