However, I believe (based on vague memories) that there used to be a ton of issues on the fastapi repo that were basically support requests. Going throw some closed issues, it seems that these were closed and/or converted to discussions.
992 karma · joined December 24, 2020
Socials: - github.com/mosheduminer
Interests: Books, Hiking, Outdoor Activities, Philosophy, Robotics, Web Development
---
However, I believe (based on vague memories) that there used to be a ton of issues on the fastapi repo that were basically support requests. Going throw some closed issues, it seems that these were closed and/or converted to discussions.
> In the event that Zed pre-screens, refuses or removes any Content, you acknowledge that Zed will do so for Zed’s benefit, not yours.
is such an outrageous thing to write in the terms. On the other hand, claiming this is standard boilerplate strains credulity.
In any case, seeing this definitely colors how I see the rest of it.
Of course, this is just my imagination, it may not actually be anything like that. But I will double down on the thrust of my original comment, which is that although autism is not simply a "disease" because the self has developed differently, doesn't necessarily mean that we want it to stay.
Whether it is correct or not to see it _entirely_ in a disease model (which it's not clear to me, how should the study have been done with a hybrid model?), I have to disagree with the suggestion it shouldn't be seen as an issue.
https://forum.snapcraft.io/t/what-happened-to-signal-desktop...
SolidJS is a framework at the abstraction level of react, vue, svelte, or marko, with an API that adopts certain philosophies from react. It is an entirely incompatible framework, however, and not just a drop in renderer (though easier to port to from react due to api similarities).
Use case is when a repository requires compilation to build the docker image, and I don't want that happening on the production server.
Personally, I was interested in Synth from the perspective of generating large mock data sets for use in a data pipeline.
That said, I think it'd be really difficult to work around Elder.js' opinions.
Dealing with the changes that occur to data over time can be complex. SirixDB simplifies it somewhat by recording the system time of every transaction. I'm actually writing a blog post to show some of the problems with changing data, and how SirixDB can be used to assist with the problem.
SirixDB also uses functionally persistent data structures to efficiently share data between revisions, preventing storage bloat.
I've been working (on and off) on the ecosystem/tooling for SirixDB for over a year now. I do almost all of the ecosystem work, and for the most part, there is only one dev on the core. While I think that SirixDB is at least feature ready, I don't think anything will ever come of the project. I wish the project would get some users though, that would be exciting :).