Posts by Script Raccoon
opentummy.dev is still available
that's everything I need to know about this "competitor"
oh la la ๐
Issues and PRs are coming in for CatDat and I just LOVE everything about it. More motivated than ever!
We all want him
Does this include web sockets?
I
d
o
n
'
t
s
e
e
t
h
e
p
r
o
b
l
e
m
The German in me wants to sue every company that sends me newsletters I never subscribed to.
Of course since literally every marketing website looks like this.
Firing = not using it.
I am so excited that CatDat already got a few issues and pull requests. I have worked on a couple of them already.
github.com/ScriptRaccoo...
๐งโ๐ป
Two great new features!
๐ Introducing: CatDat - A comprehensive database of categories and their properties. Built with SvelteKit and SQLite. Made for mathematicians who love category theory.
๐ Link: catdat.app
๐ Demo: youtu.be/dQXbPxk__qA
#svelte #mathematics #categorytheory
btw the repo description is still "Router for SPAs using Svelte 3", so the search result is also not up-to-date.
In the first post I wrote that the app might crash. This is not the case here, and it can be prevented by using the method you described.
But even though it doesn't crash, I wonder if there is a better way to just accept the inconsistency.
Without using docker or some complex deployment strategy.
Assume we have pages P and Q. Both say something about an item X. Suppose P is prerendered and Q is not (for good reasons). Let's make a commit that changes the description of X in the db. Then this description update will be visible on Q a few mins before it will be on P.
I wonder why caniuse still lists browsers that don't implement any modern stuff anyway. Like Opera Mini and QQ browser, it's ALWAYS red when I look. Practically, there will never be 100% support because of these weird browsers. Maybe one can exclude them as a user of the page, I don't know.
I would love to know. For me it's loooots of manual work. I don't use scripts, because I disliked the result when I tried once. But yeah I also use two edit rounds (at least).
Specifically, in the deployment pipeline, I first update the remote database (1), then build the application (2), and then deploy it to Netlify (3). Currently it only takes like 2 minutes, but in the time between (1) and (3) the deployed app has inconsistent data.
This is the way to go when the schema changes. But I was referring to changes of the data. I have a Wiki style app (will be announced soon โจ) and the information on some pages could be different from the one on other pages, namely when the database update has finished, but the app update not yet.
This is harder than it looks.
Neues Tutorial ๐
youtu.be/kCtC2LYcJiY
Hier geht es darum wie man eine #svelte Anwendung in mehreren Sprachen umsetzen kann.
This reads like science fiction for web development but it's real. ๐