thejosh

php7 was such a great time period for PHP, honestly lots of great experimental projects around that time too (HHVM before that, etc).

nextest is one of those things I never have to think about, because it always "just works" and I have no dramas with it. <3

Bandwidth cost is also another major reason.

WOW.

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.

Yeah, performance depends.

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.

After running Snowflake in production for 5+ years I would rather have my data on something like Parquet/Iceberg (which Snowflake fully supports...) than in the table format Snowflake has.

It's not that deep

Everytime you want to query your data, you need to pay the compute cost.

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.

Sounds great until you're locked into Snowflake - so glad iceberg is becoming the standard, anything is great.

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).

"May your SaaS never be purchased by Salesforce."

Autocomplete++ is the killer feature for me, especially for more tedious thingsike SQL column naming.

It's one of those things that if you need to ask why, you'll never understand :-)

I would argue webapps killed them.

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. :-)

I'm not surprised. A few months ago I was reverse engineering their login flow (I was writing a driver for Elixir & Rust), and was getting MANY stack traces and weird bugs happening with their authentication flow, especially around OAuth.

Considering that when I asked about basic features, and bring told that the people interested/working on those left once Salesforce came in... Yeah.

I also love places that are named after someone and it's slightly amusing/horrifying.

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_...

to every random daemon that macos 100% needs to run RIGHT NOW.

I don't care about memory usage for editors as much I care about input latency and responsiveness.

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.

Also handy (regardless of framework, language, etc) is if you use feature flags, if you're using actual valid credentials against a service or a local testing service (eg S3 vs minio, etc).

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 :-).

Memory and CPU usage is still really high though.

Sane defaults are always good, (which firefox has, IMHO), but not allowing the user to tweak basic stuff is a pain.

Not sure if you mean the git commit "title" and the "body", but the way git works is that the first line is the summary/title and then a blank line, then the body/description.

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.

I switched to Firefox earlier this year, having used Chrome since 2008/2009, previously having used Firefox. Mostly out of laziness.

Can't believe how good Firefox is now, and how great it is on Android (addons, config).

Being able to control anything on the browser is fantastic. Want to increase a certain UI elements font size just a tad? Sure! Want to tweak every aspect of the UI? sure! Want a myriad of config options, sure go ahead! Love the concept of Nightly, has worked great for me.

For anything that doesn't need a UI, you're FAR better off having some remote server than trying to emulate, it's far to slow for ARM64<>x86-64 in both directions..

Many things are just so much easier with a remote server/workstation somewhere than trying to deal with VM shenanigans.

ARM64 visualised on the otherhand (Linux works great, macos seems good(?), haven't tried Windows) with UTM is pretty great.

I would also propose ease of use as a solution to our problems that the wolf in sheep's clothing took care of for us.

We basically handed over how we communicate to make it easier (Emails, Team Communication such as Slack/Teams, etc), essential internet infrastructure (Cloudflare, Amazon etc), banking, etc because it was easier..

My worst nightmare is somehow being locked out of my accounts, the only means is either emailing the CEO directly, posting on HN until it's hopefully solved or just moving to the country, and eat a lot of peaches.

Awesome thanks, will check it out!

The main benefit of Gmail and other big providers is the anti-spam, anti-scam, "Google knows best" approach works really well.

When I last helped manage a mail server for a small business (late 2000's) SPAM was an absolute mess. You can really see why Azure etc has consumed on-premise Exchange.

The massive downside is they are the deciders of who gets through their gates, and if you're on their shitlist, goodluck.

Here in Australia we have the ACCC (Australian Competition and Consumer Commission) which is designed to help consumers, we also have pretty good consumer laws - this has stopped various companies from expanding here due to not wanting to deal with our Government, however given Australians spend $$, they need to dance to their tune.

Wow! Thanks for sharing the insights.

Amazing how much data Netflix would have, but sharing it externally would hinder negotiations.

So you can't even get total views?!

Except Heroku has an issue of your backup etc is too large (despite paying for the correct size), it would cause the replica to go down and spin up a new one, and this process could take hours.

Damn this is fast and accurate! Crazy how far things are progressing.