OUseful.Info

blog.ouseful.info · Personal blog · on HN since 2010

Tony Hirst writes about data tools, Jupyter, R, SQL in the browser, and educational uses of computing, including ChatGPT experiments.

What HN saysHN links it for his experiments with ChatGPT and search, diagram generation, and teaching computational essays, and for browser-based SQL databases.
19HN people shared it
9linked it in comments
12stories submitted
67story points
3 years agolast shared
2010people per year2026

Most-shared posts

  1. 1
    Generating Diagrams from Text Generated by ChatGPT
    3 people · 2 points · first shared 2023 · discussion on HN
  2. 2
  3. 3
  4. 4
    Google Lock-In Lock-Out
    1 people · 9 points · first shared 2013 · discussion on HN
  5. 5
    Docker as a Personal Application Runner
    1 people · 3 points · first shared 2016 · discussion on HN
  6. 6
    Using Google Spreadsheets Like a Database
    1 people · 2 points · first shared 2010 · discussion on HN
  7. 7
  8. 8
  9. 9
  10. 10
    Some Recent Noticings from the Jupyter Ecosystem
    1 people · 1 points · first shared 2017 · discussion on HN
  11. 11
    Running PostgreSQL and Jupyter Notebook within a browser
    1 people · 1 points · first shared 2023 · discussion on HN
  12. 12
    Spotting Potential Battles in F1 Races
    1 people · 1 points · first shared 2015 · discussion on HN
  13. 13
  14. 14
    Data scraping wikipedia with google spreadsheets
    1 people · first shared 2011
  15. 15
    Feed
    1 people · first shared 2023

What HN people wrote when they linked it

lioeters · 2022-10-06
It probably wouldn't be suitable for a blog or classic CRUD app. The use cases I've heard about are more for education and online editor/IDE. For example: interactive documentation that runs code in the browser with an ephemeral/temporary database, possibly imported from the user's desktop. For teaching programming languages in the browser, with the compiler compiled to WASM, so the student doesn't have to set up a local development environment. Or a database explorer that's a purely static site with no server, neither remote nor directly on user's computer - just virtually in the browser, which is a more secure sandbox. You could have a folder of HTML, CSS, JS that's a full-stack application with client UI and server (theoretically). Further reading: • SQL Databases in the Browser, via WASM: SQLite and DuckDB - https://blog.ouseful.info/2022/02/11/sql-databases-in-the-browser-via-… • Pyodide - https://pyodide.org/en/stable/ - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly. • Client-side WebAssembly WordPress with no server - https://make.wordpress.org/core/2022/09/23/client-side-webassembly-wor… • Stackblitz - Instant development environments - https://stackblitz.com
anyfactor · 2023-02-23
bjterry · 2023-02-06
Perplexity.ai processes Bing search results through GPT-3. It works really well, and you can see the prompt they use at https://blog.ouseful.info/2022/12/09/combing-chatgpt-and-search/
kragen · 2022-07-04
If someone were to try to do a bulk download of the data (well, or whatever they thought was the most significant data) through the API for preservation purposes, might it put an undue load on your server infrastructure? Some kind of bulk data download might be useful insurance there. There seem to be some interesting efforts to run SQLite in the browser so that server infrastructure only has to provide bulk data access, with precomputed indices to avoid full table scans; I wonder if those might be applicable here: https://blog.ouseful.info/2022/02/11/sql-databases-in-the-browser-via-… (though of course if you aren't using SQLite as your backend now it might be a headache) Such an approach, if it were feasible, would have the advantage that bulk data downloads wouldn't look very different from normal use.
jgamman · 2019-05-08
and a more jupyter-centric agree/reply by Tony Hirst: https://blog.ouseful.info/2017/11/15/programming-meh-lets-teach-how-to…
endisneigh · 2022-05-22
> The point of much of the "SQLite hype" is that there are many applications where read load is high and queries complicated, but the write load is low to non-existent. In situations like these, you can make do with a smaller DB than Postgres. Sure, but my point is that unless you know for sure your app will stay the same forever, why not just use Postgres or something more flexible to begin with? With things like Supabase, Hasura, and Managed Postgres why even bother with SQLite? Just seems like you're causing your tech team inevitable pain when you have more writes than expected and have to migrate off of it. Both Fly.io and Cloudflare's solutions are a good example of this. If you're going to use another service, why even bother with SQLite? I totally get the SQLite use case when you're using it directly like with X-Range-Requests (https://phiresky.github.io/blog/2021/hosting-sqlite-databases-on-githu… or SQLite.js and a WASM app (https://blog.ouseful.info/2022/02/11/sql-databases-in-the-browser-via-… but idk. tldr: if you're using a service, why bother with one backed by SQLite instead of Postgres? The underlying data store will be abstracted away anyways. One scales decently, and the other, not so much.

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close