thenorthbay
thenorthbay on Hacker News
Posted by
thenorthbay on Wednesday February 26, 2025 @03:38PM
from the ask-hn dept.
Hey HN,together with a friend we realized in our engineering jobs that e2e testing is often broken and not worth the effort. But AI Agents could change this massively.There are a couple of reasons why AI agents could revive the topic:- LLMs can automatically adjust tests to the evolving product by simply looking at the git diff and changes in the UI- It'll become much easier and cheaper to have...
Posted by
thenorthbay on Thursday July 18, 2024 @03:51PM
from the ask-hn dept.
I just can't help observe that my developer friends increasingly build on the "low-end", serverful platforms instead of serverless. Many call serverless overkill for the (commercial) apps they want to build. Will this be an ongoing trend?In recent years, many new serverless service providers have been released for everything (Neon – Postgres, Cloudflare D1 – SQLite-like DB, GCP Functions,...
Maybe not for editing per se. But for providing meta-functionalities to services built on top of revideo. Rendering, for instance, but maybe even reusable embeds, video watch analytics, download links, programatic re-rendering with webhooks and their configuration, etc.
What other functionalities could you offer?
Interesting stuff! Which use cases do you think developers will use you most for?
There could be really interesting abstractions that people might build on top of this. Like automatically creating and animating infographics, making background sounds, or video cutting and recycling. If you spin this 100x further an entire video creation studio might emerge.
Which parts of Video Infrastructure do you want to build first? Which other higher-level parts could be built by you or users? Where could this go?
that's pretty cool! Would be great to have it for TS to configure my own backend
Posted by
thenorthbay on Thursday April 25, 2024 @07:41AM
from the self-post dept.
Wouldn't it be cool to have a Supabase for SQLite?The core idea here is: let SQLite run next to your application on the server; but have all features a client-server database give you.What's the spec for this?- SQLite runs next to server as production database- That way, reads and writes are very fast- In dev, some sort of worker auto-copies the prod DB to the local repo. Production bugs can be...
I just did a quick search and struggled to find anything about the performance issues you referred to - can you link something so I can take another look?
Thanks for the suggestions.
Hey! Thanks for the feedback. I'd just be worried people might not be using the correct libraries since I think they still provide different functionality.
So exporting one Database that allows people to pick which driver they want to use might be a simple and user-friendly solution (incl. better-sqlite3) which people have asked for.
Yup! I doubt this project will naturally evolve into whatever you're describing. And that's ok! This project might help people who want to use SQLite like Firebase, with a similar API and experience but without letting network requests increase latency (see:
https://news.ycombinator.com/item?id=31318708).
Addressing main points like implementing atomic transactions (read and write operation on a doc) seems warranted since it exists in Firebase as well.
Yeah interesting. I'm wondering what happens when I'm starting to introduce things from "outside" the system that need async operations, like processing webhooks.
Just didn't find it quickly enough after some browsing. Also, using SQLite seemed so simple.
I'm using SQLites underlying Data Change Notification functionality. It's exposed by one of the libraries mine relies on.
If I understood you correctly, Documents in a database, and database as a file. If else please let me know.
Thank you for the feedback. Seems this is important.
Yup! I actually don't know about that. I figured this would be used for setting up newer, server-side Remix or Next projects rather than more dated ones. I could imagine that by keeping sqlite and sqlite3 up to date, people might also not be stuck on more dated versions of SQLite. The tracing/profiling functions were also only implemented recently in sqlite3 (node to C interface), in 2023.
If you use the library on a server in a node.js environment, wouldn't it be useful to fetch data (e.g. Remix / NextJS)?
Besides, I'm not sure if better-sqlite3 offers the listener functionalities I care about. Skimming the docs, it seems it doesn't.
I guess it was sufficient to not have that kind of accuracy in most of the application to deliver user value. There probably were parts of the application where we used transactions.
Could be a cool feature to build for this, though.
Interesting. Updating values via incrementing them is a use case I barely had in Firebase. I mostly only dealt with 1-time updates to values, e.g. by the user or scheduled jobs. In which scenario would the current design cause you problems?
Posted by
thenorthbay on Monday August 07, 2023 @04:14PM
from the show-hn dept.
https://www.npmjs.com/package/doculite
Hi!As I was working on a side project, I noticed I wanted to use SQLite like a Document Database on the server.
So I built Doculite. DocuLite lets you use SQLite like Firebase Firestore. It's written in Typescript and an adapter on top of sqlite3 and sqlite.Reasons:1) Using an SQL Database meant having less flexibility and iterating slower.2) Alternative, proven Document Databases only offered...