Comments URL: https://news.ycombinator.com/item?id=46977490

Points: 2

# Comments: 1

Okay, this is really, really cool and is exactly my niche, as you mentioned it's kinda a combination of things like Stylus/uBlock Origin filters and custom filters/etc. This is really needed, as for example GitHub code preview is completely and utterly fucked, to put it lightly. Showing symbols, not being able to select code properly without weird visual glitches happening..... requires a bunch of scripts to fix. (https://github.com/orgs/community/discussions/54962).

What's your funding plan? You mentioned paid plan, but what's the actual benefit for users that they would pay for this? (I totally would, FWIW).

Do you foresee companies who need to build special widgets for whatever reason for random websites they use as kind of "Extension light" alternatives - your product reminds me of Retool (https://retool.com/), but for website tweaking.

Very cool product, love the ability to do "extra things" which will fix a whole bunch of websites I use everyday that I CBF'd either making an extension to fix or battling the uBlock/stylus filters.

Discoverability will also be needed, kinda like [karabiner elements complex modification rules](https://ke-complex-modifications.pqrs.org/)

edit: no firefox support, sadpants.

I think a hybrid approach works best (store on Snowflake native and iceberg/tables where needed), and allows you the benefit of Snowflake without paying the cost for certain workloads (which really adds up).

We're going to see more of this (either open or closed source), since Snowflake has acquired Crunchydata, and the last major bastion is "traditional" database <> Snowflake.

It's not that deep

If instead you can write to something like Parquet/Iceberg, you're not paying for access your data.

Snowflake is great at aggregations and other stuff (seriously, huge fan of snowflakes SQL capabilities), but let's say you have a visualisation tool, you're paying for pulling data out .

Instead, writing data to something like S3, you instead can hookup your tools to this.

It's expensive to pull data out of Snowflake otherwise.

The trap you end up in is you have to pay snowflake to access your data, iceberg and other technology help with the walled garden.

Not just snowflake, any pay on use provider.

(Context - have spent 5+ years working with Snowflake, it's great, have built drivers for various languages, etc).

Most applications now adays are just electron wrappers.

WebApps also allow a much more flexible update schedule, and other benefits.

Downside: apps now need gigabytes of memory for simple apps. Upside: Linux is now a lot more easier to use as a lot of things are web based. :-)

Harold Holt was the Australian Prime Minister in the 1960's, and went for a swim and went missing (yes, there are many, MANY local conspiracies this :)). So what did we do? Named a swimming pool[0] after him (construction actually started before his death, I believe).

[0] https://en.wikipedia.org/wiki/Harold_Holt_Memorial_Swimming_...

Jetbrains (IDEA IntelliJ, Pycharm, etcetc) put a lot of effort into making their IDE low latency as it was getting to a point of being almost ridiculous. Their editor is built in Java, and they run on their own runtime as they have so many hacks and tweaks to make it work as a desktop app as well (font rendering, etc).

Pavel Fatin has a [great article](https://pavelfatin.com/typing-with-pleasure/) about typing latency and his work around implementing this in IntelliJ, well worth a read.

Enabling this for non-technical users really helped also report any issues they would see, it was great for testing environments.

Plus you would probably end up needing all this information anyway if you do any error tracking, so it probably exists somewhere already :-).

I really like this approach, a nice short message with a summary, followed by a longer description in the "body".

One feature I really like from GitHub is you can set an option when merging a Pull Requests that when merging the commit title will be the Pull Request title, and the body of the PR as the message.