One issue I found is that for new projects, it is much harder to market now. shownew is flooded and subreddits have turned up their spam filters high so quality projects will have trouble getting eyes without significant social activity before wanting to share. So the bar for introverts writing (not vibing) good OSS feels like it has gone up in an unfortunate way.

Ah good reminder to see if I should repatch with revanced. Not that I actually use YouTube on my phone much, I mostly catch up on SmartTube on weekends. But great to be in control.

Interesting - I was surprised to see a note on Wefunder, though the opposite direction that Canada residents aren't allowed to use the platform to invest. For context, no problem from Japan.

It sounds like Canada has some unique regulations here, wouldn't have expected that.

Agree completely, just curious to understand better this

> "you do you, but the supply runs out next week".

What's the supply referring to here? Not able to follow what this is saying.

it means you are the master of your own domain but when it gets bad and you want vaccine now that there is none left, remember your choice, you were the architect of that portion of fate.

One big reason I tend to build on GCP instead of AWS is it's much easier to use with Terraform. GCP's APIs are generally defined as a semantic unit while AWS has ad-hoc resources that get strung together by the console or CLIs, not the APIs. An example is a k8s cluster in AWS takes a dozen resources while in GCP it's just one.

While there are then third party (I think) Terraform modules to try to abstract the AWS world into an easier to use interface, they can't really solve the problem that in the end Terraform manages resources and orchestrating changes including deletion across a dozen of resources is much harder than a single one.

GCP is huge so I wouldn't be surprised if there are also problematic units there with less good definition. But I would still argue that there are cloud providers that provide a reasonable view into their infra fo IAC.

Not to say it is the quip but I have had buggy builds with bun that requires sticking to esbuild, I think it was bundling prettier with many plugins into a single JS file.

I always do that sort of thing in Docker so never considered it could be a Linux-specific thing, maybe so.

I think it's common to have dev not production secrets there, and am reading the blurb about production secrets as non-local secrets. Even dev keys are a pain if they get leaked.

The idea seems nice with a simple yet effective implementation. While I think I currently have a shell script syntax highlight plugin reading env files, it's definitely overkill. Now if only this could protect from random npm packages reading your env files...

Thanks @pjjpo, exactly. My bad to confuse people, no we don't put real prod-prod credentials in .env. We use mechanisms to ensure separation of secrets. Thank you for saying that it's a simple yet effective implementation. If you try it and let us know your feedback.

This implies there's some kind of shared resource out there on the network that your devs are developing on. Why not make all these resources part of your local dev stack, served on localhost, and use dummy credentials? You can even commit them because they're not sensitive.

Ok ok, it is indeed keys to AI APIs. I know it's not kosher to admit to that on HN anymore but it's the reality for me at least. Unfortunately local models just can't support development of products using them.

Haven't used Nova for a while and at first was curious if this was good for bringing it back from unmaintenance. The heavy focus on sustainability and marketing in this blog makes it seem unlikely though.

Switched to Pear when Nova got unstable after a Pixel upgrade and I noticed it hadn't been updated in years. Been working well though will keep any eye on any other recommendations that show up in this thread.

I don't upvote often and you got it. This is a great explanation of what seems to be going on.

I was happy to see them give this clear headline

> Linux isn’t especially complicated on a daily basis, but you have to be willing to solve your own problems

That being said, given the huge uptick in Linux articles lately, I can only believe Canonical is funding something here. It's just too sudden of a surge.

I'll probably still game on Linux, but who knows if that will last after a few more "freeze on resume" situations. These just don't happen on Windows and most Linux sentiment seems to be coming from anti-Onedrive feelings, which is fair, but the popups are easy to click through. Random Linux instability, not so.