JaTochNietDan

Depends on how many years of support of TablePlus you want to pay for.

You're right, this probably wasn't worth it on a personal level.

But on a collective level, maybe.

Don't hide it, run with it

My understanding of native is also that it's essentially natively compiled to the platform, not that it's necessarily using platform native UI.

The goal here with this project is to be platform agnostic. TablePlus due to being developed for macOS is much worse on other platforms than on macOS where it shines.

I wanted to bring the same experience but make it platform agnostic.

Actually I use macOS primarily but I use Linux for my VPSs and home server of course. I should probably test it on there.

TablePlus is notoriously not that great on Windows due to not being as platform agnostic.

I wanted to make this as platform agnostic as possible while being ultra performant. TablePlus is awesome on macOS, not so awesome on other platforms. Let's bridge that gap and make it open source and free.

You're right, Linux is great and I use it for all my server hosting needs.

I built (vibe coded with direction) a free, open source alternative to TablePlus.

The goal is high performance and easy to use just like TablePlus but without that nagging window asking you to pay to have more than 2 active tabs.

It also runs in the browser for a fun demo since it can be compiled to WASM.

Feedback is super welcome and I'm continuing to iterate upon it and am already using it as my daily driver and ironing out the kinks. It works well enough™ already but expect a few janky things here and there.

Yeah but to be fair, that's what he's actually supposed to be doing.

Yeah, I don't know about you but I've got all my life savings in the safe haven that is Tesla stock.

I actually created something similar to this a while back when Reddit TV was taken down.

Would love if you guys could check it out.

It’s https://viddit.app

It’s really only meant to work on desktop though.

You sound like one of the most toxic people on the face of the planet. I just thought someone should tell you that in-case you're unaware of how horrific you are.

Fixed that and edited it up a bit.

I'm not really sure what you're saying at all? It seems like we have agreed but I simply cannot comprehend your example.

The point I was making is that we could all spend our time going as deep as possible with as little abstraction as possible and end up writing stuff in assembly because "it's important to know how something works".

There is always a cost/benefit with abstraction when it comes to getting things done.

I didn't make the site, it's a fork of the original website by Hubspot.

Ah, I've just removed the quotes. Thanks.

This is exactly it summarised. It's more frustration at the extra verbosity I had to put in to do something I'd become so accustomed to doing in a line or two.

I don't disagree that you should know core concepts of what you're writing. I write a lot of Go without any heavy abstraction libraries (i.e ORMs) and have done with others like PHP in the past too.

With abstraction there has to be a balance though. Sure, I concede that knowing how it works is actually important, hence why I've spent a lot of time doing things without libraries in the past, especially as I was learning. It actually enrages me when people who've only ever used ORMs make super basic mistakes when writing and executing SQL themselves for the first time, i.e selecting a bunch of relationships in a loop one by one, instead of getting them all in one query. Stuff like that is a good example of how only ever working with abstracted versions of your tech stack results in mistakes down the line that have costs, since the abstracted version doesn't explain these concepts to you.

However, when it comes to actually trying to get things done efficiently, abstraction can help a bunch. Writing a bunch of stuff from scratch every time is not particularly productive either.

The Github certificate takes a while to sign so I've turned off enforcement for the time being :).

I'm heavily inclined to agree with this. In fact, only this weekend I was working on a very simple one page tool and from the get-go I decided to adopt this "vanilla" only approach, i.e no JS libraries really at all.

Pretty quickly I found myself wishing I had just used jQuery or at least some other library to make stuff easier and get things done faster. When I finally got it completed in the end I wasn't sure why I bothered to struggle and waste so much time instead of just including jQuery and making things a bunch easier and less verbose. Sure, there may be other libraries worth using instead but the point against the "vanilla JS is all you need" argument.

I actually found the cited website in this post http://youmightnotneedjquery.com to be so strange as examples of why you may not need jQuery that it may be satire. I was surprised to find out that it was not satire. So I actually forked it and created https://youmightneedjquery.com, on which I may change some text in the future. It may not load for you yet as the DNS propagates.

You can find the fork on my Github account here: https://github.com/JaTochNietDan/youmightnotneedjquery

I'll make some changes later to show the satirical nature of it.