It's much smaller and likely to be largely untested in production (since it just lost the MyProject name), but both run on Node so there are some similarities.
I believe they'll settle on splitting out Youtube - which I believe makes perfect sense and from a rev/valuation perspective, would be a top 20 company.
I found the post interestingly personable, something that I don't often find with Google. I've used Google Scholar for many years, before I used Elsevier and it was a gamechanger.
I use Budibase for a few projects. I chose it after deciding I couldn't accept Retool's pricing and that I wanted something open source. I have only a few minor complaints:
- The SQL Server plugin is a little halfbaked. It doesn't work properly with failover clustering and I had to punch in the IP address for a specific primary node, which then breaks when the cluster fails over to a different primary node. The "port" field is broken and you have to leave it blank or you get a type conversion error in their connection code. Going through a REST API seems to be the more well-trodden path.
- Google login in the open source edition is clunky, and there's no good way to tell users to use it. There's a separate pair of login/password textboxes on the same page that draws the user's attention; we have to teach users to click on the Google login button which then opens in a new window. In our case we don't even need authentication, but there's no way to remove it and offer a login-free experience.
- You can't really hide that you're running in Budibase. Despite my best efforts, my users call all my apps "Budibase" instead of the actual name that I gave to them. And nobody knows how to pronounce "Budibase"--native speakers tend to come up with "bootybase" instead of "buddybase."
The development experience is delightful. I really like it. I wish I could design all my full-code UIs in Budibase rather than having it attached to a low-code platform.
Thanks for your question! Basemulti differentiates itself in several key ways:
1. Lightweight and Easy Deployment: Basemulti doesn't require Docker and can be deployed to Vercel with a single click, making it incredibly easy to get started.
2. Flexible Field Types: We support a wide range of field types including email, single/multi-select, and relational fields, offering more flexibility in data structuring.
3. Universal Database Compatibility: Basemulti works with any MySQL, SQLite, or PostgreSQL database, whether new or existing.
4. Non-Invasive Integration: When connecting to an existing database, Basemulti creates a virtual layer for all configurations. This means you can add Airtable-like interfaces and APIs without altering your original database schema or affecting existing operations.
These features make Basemulti particularly suitable for teams looking to quickly build on top of their existing data infrastructure without the overhead of traditional no-code platforms.
Consider using a low code platform to test your thesis first. Use a platform like Budibase or something, that's open source, you can self-host and use your own database for security reasons.
They are already gone on Firefox. I had to reengineer one system to make it work. So if you’re care about compatibility, third party cookies are already effectively gone.
Isn't it the opposite? Most of Google's competitors in the ad space are very dependent on third party cookies but Google itself can get browsing information from Chrome directly.
AFAIK this is why the UK's competition authorities were hostile to Google removing third party cookies.
It’s unclear - competitors rely on 3p cookies, but abuse them. Google getting rid of them in theory levels some of the playing field - smaller companies can compete with larger ones because larger ones can no longer track users across every site where they have a pixel installed (IE fb’s massive advantage of having a pixel on virtually every website means only they know every single site you visit).
But in practice, the engineering lift and complexity of the solutions is absolutely massive, so many companies simply will not be able to play ball. Additionally, because the internet will be more private the sketchy companies doing things like fingerprinting will cease to exist. Google has never said they will kill off competing solutions that are not privacy safe (UID2), but have explicitly said they will stop any fingerprinting, cross site tracking, etc.
Annoying but I felt exactly the same. I'd advise you to rename the project - it's still early days and the longer it goes on the harder it will be to change - I've felt this pain.
Also, yes, I will take on that risk. As anyone who has ever been at the receiving side of an issue tracker knows, not all feedback is equal. I appreciate taking the time to provide feedback, though, but I always reserve the right to not act on it.
Is it feedback or opinion then? Your two sentences do not agree.
If 7 people tell you that "go kite" is not a great name for an important database system, I don't know what to tell you other than "consider the feedback".
reply