I tried installing it using the recommended option, via Claude, it didn't work. I opened an issue and I've added what I have tried and what errors I did encounter.
Yeah, sure, have my keys. You seem like a trustable fellow. You know what? Also, take my credit cards, my bank accounts, yeah, why not? I trust you.
It's silly to think that someone is stupid enough to add their keys to your app, when you provide no guarantee. When your project is open source and can be self hosted, that is something else.
Nice, it looks wonderful. I've been using pdf.js and it gave me a lot of headaches.
Another issue with pdfs is generating them, I'm still looking, years later, a library that you can pass a template or something and it generates a pdf. A simple interface to generwting pdfs, I couldn't find any. I was curious if you have plans on also implementing a Pdf generator.
Thanks! Yeah, I really get that, pdf.js gave me a ton of headaches too. Honestly, that’s part of why I started building this. I just needed something that didn’t fight me every step of the way.
Not planning to build a PDF generator just yet, but you're not the first to mention it. If more folks are looking for that kind of thing, I’d definitely consider it. Appreciate you bringing it up!
One way to generate PDFs, and it's kind of round-about, using HTML to then convert to PDF with Chromium. You can make the HTML using templates and you get access to CSS, too.
How does this compare to Sideberry extension(which is only for Firefox, it is free and open source)? Being cross browser, might not matter in 90% of cases, because from what I've noticed, people usually use one browser.
That’s a good question! I didn’t know about Sideberry—it looks really interesting, and I’ll definitely check it out in more detail.
I agree, many users stick to one browser. My goal with cross-platform support is to eventually make TabDock available to more users, but for now, it’s only available on Chrome and browsers that support Chrome Web Store extensions.
In terms of how it compares, TabDock doesn’t just store your tabs in a list. The core idea is that you track entire windows, so if you make changes, your saved workspaces update automatically with the auto-save option or manually with the save button. This allows you to quickly switch between projects and only have the windows open that you’re actively working on. That’s probably the main difference, and I’ve also added some extra features like a cool new tab page, a Kbar, and searchbar commands to boost productivity.
I’m always open to feedback and ideas for improvement!
I've noticed that having a screen recording or tab recording feature is very useful. I wanted to do a demo of my web app and looked for a while for a tool to be simple, I ended up using clipchamp.com.
I will definitely add that, I have a lot of cool things too add so stay tuned :D Psst, i havent mention that anywhere, but I want to add 3d animations, so your video will look like its in 3d, that will make those marketing kind of videos about websites or someting else that look flat look super cool, like some sliding animation from bottom to top, some zoom in and out, close ups from different points of views etc ..
I'm curious about the latency between a backend app that runs on different cloud provider than aws(eg hetzner), because I've noticed that they run on aws(it shows up when choosing the region for your database). Has anyone used this and connected from a different cloud provider? Have you noticed big latencies?
You will generally run into different types of latencies in this case since you have the general connection latency when those are getting established plus the regular physical/network latency between where the database is located and your own servers.
For connections, since a TLS handshake is required, the impact of physical distances can have a greater impact on the connection time. The following article: https://sking7.github.io/articles/44961356.html actually provides a good 3.5x-4x figure which correlates with some connection tests I've completed.
In other words, if an initial TCP packet takes ~100ms to get from the database to your server, then establishing a TLS connection to the database will probably be around 400ms.
Once the connection is established, running queries over an open connection is generally going to be quicker, at least for simpler queries. More complex queries will still take whatever time they need to process on the database end before they can start sending results back so results will generally vary there.
But going back to that 100ms example...if the amount of data being returned from a very simple query is minimal than the response time here would be very close to that 100ms figure over an already open connection and likely would go up from there depending on the complexity of the query and amount of data needing to be returned.
Since the connection hostnames are publicly accessible and TLS is always required for connections you can easily test from your own provider's location. So long as the general physical location isn't too far away from a supported region, the latency overall shouldn't be unusable.
I may have mangled some terminology/analogies above but hopefully that helps provide a bit of a ballpark for you. If you have specific to/from regions in mind I might be able to try and collect some specific numbers for you!
I haven't spent time optimizing TLS between a database client and server, but in HTTPS, using TLS 1.3 without early data (or TLS 1.2 with somewhat optimistic handshake handling) gets you to one added roundtrip, TLS 1.3 early data gets you down to zero added round trips. Early data isn't always appropriate, because there's potential for replays, but the latency improvement might be worth considering for some selects.
I'm not an expert on the TLS 1.3 but the 0-RTT feature seemed like it wasn't implemented by a lot of clients so the new QUIC protocol used in HTTP/3 seems to be the workaround for that. The following recent comment and the first video linked actually had some great related info that I was recently reviewing on that topic:
https://news.ycombinator.com/item?id=32572825
I don't know if the MySQL protocol itself though be able to utilize the TCP-based TLS 0-RTT functionality or not however so connecting via a regular client may still end up with a lot of the back and forth handshaking.
The newer serverless driver for JavaScript has some opportunities to take advantage of QUIC within HTTP/3 in the future as Matt mentioned over here recently:
https://news.ycombinator.com/item?id=32513043
So that will be interesting to continue seeing how it evolves/improves over time.
It's depends on how far the two data centers are from one another. But the big cloud providers have data centers in similar locations since they usually want to be near an internet exchange[1]. For example most companies that provide cloud services have a data center in Virginia, USA. So if both data centers are in the same region then you can get numbers in the sub 5ms range. As long as you're not crossing the ocean the latency should be fine.
