- wg0Why not use SQLite then as database for package managers? A local copy could be replicated easily with delta fetch.
- Could you elaborate on the storage engine and processing pipeline if not confidential?
- The authentication account should have a permanent stable identifier that should be the provider's responsibility to issue and manage.
Everything else including email and username should be changeable (provided there's no conflict with other accounts)
- So essentially - it only works with Latin script? Because without fonts, every other script is NOT going to render.
- Echo is really great framework. Blazzing fast and great documentation.
- This evangelism around HTMX is bit misplaced.
First - simple use cases sure great. But imagine you have to update some element out of the from tree. Now you need to have OOB swaps and your HTML must contain that fragment.
Not just that your server template code now has to determine if it is HTMX request and only render OOB fragments if so.
Even at decent size app, soon it turns super brittle.
Yet to talk about complicated interfaces. Let's not go complicated just think of variants in an E-commerce admin panel.
3 variants with 5 values each these are 125 SKU rows that must be collapsed group wise.
htmx can do it but it's going to be very very difficult and brittle.
So it is surely very useful but it is NOT the only tool for all use cases.
- Charging for the self hosted runners - That's close to flat $90 per month for a machine that you host yourself no matter how small or large the machine is.
- Very well written but I can't understand much of this article.
What would be one good primer to be able to comprehend all the design issues raised?
- Gut gemacht!
- Thanks. It was a stupid most idea for MOST shops. I think maybe it works for AWS, Google and Netflix but everywhere in my career, I saw 90% of the problem was due to microservices.
Diving system into composable parts is a very very difficult problem already and it is only foolish to introduce further network boundaries between them.
Next comeback I see is away from React and SPAs as view transitions become more common.
- Thank you! That's great and it is possible but... With some limitations.
The idea is from sign up form to a D1 Database that can be accessed from the worker itself.
That's not possible without updating worker bindings like you showed and further - there is an upper limit of 5000 bindings per worker and just 5000 users then becomes the upper limit although D1 allows 50,000 databases easily with further possible by requesting a limit increase.
edit: Missed opening.
- If anyone from cloudflare comes here - it's not possible to create D1 databases on the fly and interact them because databases must be mentioned in the worker bindings.
This hampers the per user databases workflow.
Would be awesome if a fix lands.
- I love Google's product managers. I love product managers in general but Google's product managers are at a whole another level. And it shows.
- Okay could you please share your thoughts as a user:
- What databases you want to work with?
- What functionality you want from such a UI?
- What database size we are talking here?
Asking because I am tinkering with a similar idea.
- - Have written Rails and Django both
- Have written SPAs (React/Svelte)
- Have written Go based services
Each has their on pros and cons.
- Can someone remind me how we ended up in the SPA era and why exactly? Was it about not seeing the loading spinner? Or there were more reasons to it?
- This look really neat and great! Amazing job!
BTW just looking at other variations on the theme:
Feel free to add more.
- Yes but I believe it would be a safe and lighter choice. The rug pull on deno is more imminent than elsewhere.
- Great! Just wondering maybe Bun (different JS engine) could do the job for plugins.
- Is it 400mb? Could be V8 for plugins.