Any application that can be written in JavaScript, will eventually be written in JavaScript. - Jeff Atwood
210 karma · joined August 11, 2011
Hope the acquisition works out. I used to work for FileMaker, and from the business perspective, their products are complementary to each other.
I think Dolt is closer to Neon/Xata. But still there are differences.
IIUC, Dolt is bringing the database feature to Git, while Neon/Xata is bringing the Git feature to database.
Speaking of Bytebase, if Dolt is really good at versioning schema migration, Bytebase value proposition will be a bit less attractive, but not much. It's similar to the Git story, regardless how powerful Git is, people still need GitLab/GitHub for the developer workflow on top of the mere versioning.
If you are looking for schema change management tool, then you can check out Bytebase (bytebase.com). But it can't answer questions like "which collections contain links to bigmongo.user.id?"
>> it feels like a disingenuous strawman argument to claim that declarative schema management requires `mysqldump`
The article explicitly said it's a hybrid approach and never intended to claim this way. Otherwise, it would be an obvious mis-statement.
Our initial launch does use "state-based", but we later change it to "declarative". You can check the product here https://demo.bytebase.com/project/blog-102#gitops
Of course, it's always a bit confusing to have multiple ways to reference the same thing. So be it.
We at Bytebase also recognize this and have spent over 2 years to build a solution for team to coordinate the database migrations better.
It's technically a roll forward, while to most users it's more nature to say rollback/revert
As for the schema management part, we at bytebase.com have also built an OSS product to tackle this specifically.
bytebase.com could be what you are looking for.
Disclaimer: I am one of the authors.
I knew it was doomed.
Disclaimer: I am one of the authors.
(Author here) We definitely need Figma, because we don't have designers and Figma empowers non-designers design.
1. We don't have a sales team. 2. Our content is all markdown based and stored in Git, so we can't use their CMS and analytics.
We end up managing CMS in a table.
While wearing the marketing hat, I would say intercom is useful to some extent. We probably won't have those customer conversations if we don't have that small bubble.
We are building a dev tool for database development workflow, which is not a big market. We are also based in Shanghai, thus unlike valley-based shops, we don't have many viable ways to engage (like private introduction, offline meetup).
Internally, we also struggle between the experience and the leads, and as this topic is raised up here again, it will surely bring up another round of team debate this week.
https://www.bytebase.com/zh/blog/database-review-2021-byteba...
We don’t list them on the blog front page because most Chinese audiences consume the content on WeChat.
>> I find it hard to believe they're actually using all these tools on a regular basis.
We do rely on all mentioned tools, though for some tools, we only use them occasionally due to their nature (e.g. we don't need to visit Pulley every day to manage equities).
>> Excalidraw (???)
Oh, Excalidraw Plus
>> Their docs appear to be using Docusaurus which comes with Algolia out of the box, so ???
The Algolia part is correct, while we are Vue based, so we built our own and also implement some special markdown syntax to facilitate tech writing https://www.bytebase.com/docs/document-write-guide
>> The R&D team of just over 10 members releases a new version every two weeks, and each version has 100 to 150 PRs submitted.
It's an open source project https://github.com/bytebase/bytebase. And most are small PRs. Here is our review guide line: https://github.com/bytebase/bytebase/blob/main/docs/code-rev...