konsalexee

Or even Vercel/Netlify

IFF this holds true, this is going to be the biggest biohacking supplement of the next decade for sure.

Making this bold assumption as I don’t see yet a valid way to remove plastic from the modern supply chains. It’s embedded in every aspect of our lives so this will be huge if it holds true.

Super fun game! When are you gonna sell this to NYT games to play alongside with world daily? lol

Finally the Confluence pages were really bad.

Thankfully at least LLMs could figure out things t help me setup SXT LTE 7

Three Body problem, which I think it's even greater than its Netflix adaptation

Hey Hackers,

We are building Cherry, a tool designd to solve the "spam crisis" currently hitting open-source maintainers.

With the rise of LLMs and agents, the volume of low-quality, automated PRs is making it impossible to find the good contributions.

How we want Cherry to work: - Connects to your repo: We monitor incoming PRs. - Whitelists the good bots: Dependabot, Linear agent etc., get a pass. - Verifies the humans: We intercept new/unknown contributors and ask them to verify their intent and understanding of the code before the PR alerts the maintainers. - Silences the rest: Low-effort scripts and drive-by spam get filtered out.

We are trying to walk the line between stopping spam and remaining open to new developers. It’s a hard problem.

We’d love to hear your thoughts on how to solve this without discouraging legitimate junior developers. What kind of heuristics do you currently use manually that we could automate?

Author here of the original post, it is Tahoe indeed I should update the post!

I’ve been working on Hopp (a low-latency screen sharing app) using Tauri, which means relying on WebKit on macOS. While I loved the idea of a lighter binary compared to Electron, the journey has been full of headaches.

From SVG shadow bugs and weird audio glitching to WebKitGTK lacking WebRTC support on Linux, I wrote up a retrospective on the specific technical hurdles we faced. We are now looking at moving our heavy-duty windows to a native Rust implementation to bypass browser limitations entirely.

Being honest, that was one of the main deal breakers. Profile management, so we do not have work tabs spilling over into our personal space.

It was indeed long supported, but not a smooth experience. Have anyone tried the new profile management out?

Not sure if Hacktoberfest will be the same again

In this pipeline, aren't alternative approaches like turbopuffer efficient?

Meaning no much pruning in the space, but utilizing Object storage for long term retention, and cache-hit staying in nvme?

Curious how it compares as companies like Linear and Cursor are using it but not sure if it would help in this case.

Wow did not know this, thanks for reporting, will probably then skip the video and add something more light-weight.

Pair programming though is not only editor interactions. Debugging through logs, drawing etc are happening outside an IDE.

Before starting Hopp and searching for alternatives, one of the things I really liked was Zed's paradigm around collaboration, with its Collab panel and Channels.

The streaming quality was also quite good with Zed. VSCode and JetBrains pairing features were a pain, as you needed to share a URL. The experience in general was not optimal. Not something you want to do multiple times a day.

With Zed, the only drawback was that the scope is always IDE (view mode also for whole screen). But from my experience, pairing is more than your IDE. It's terminal, debugging your unnecessarily complex AWS setup, fiddling with Grafana dashboards, etc.

If you enjoy Tuple, we just silently open-sourced Hopp (one of the maintainers here), we are still in Beta era, but would love some feedback!

There is also code example with Envoy

Amazing work mate! Your work makes me want to get involved with astrophotography

That's how you profit

Those grandparents are the best.

I think eventually all OSS projects/repos will suffer with this.

My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio

I think the title is stating this: "Postgres LISTEN/NOTIFY does not scale"

That means for moderate cases you do not even have to care about this. 99% of PostgreSQL instances out there are not big "scale".

As a sr. engineer is your responsibility to make a decision if you will build for "scale" from day zero or ignore this as you are mindful that this will not affect you until a certain point.

The parrot on the OGs shoulder is the goal (besides raising the ARR lol)

I love it! Amazing work.

A slider to do a bit of time-travelling if possible would be also a nice to have

Start with: “How do you spend most of your time?” Not “What do you do?” It opens people up beyond job titles.

This is something that feels alien in SF people. A fundamental difference for example from Greece and people living in SF is this.

- Greek opening question: "Which city are you from?" - SF opening question: "Which company do you work for?"

It was really enjoyable to read. And I also do not read a lot of fiction, with my last book being the Hitchhiker's guide to the galaxy series.

My verdict is that Project Hail Mary was way much more engaging in terms of story-telling. The concepts were cool, and tbh I look forward for the movie and see if the adaptation will be nice

Long story short, I didn't want to make that analysis/distinction because it would miss the point.

They excel in their respective areas based on the architectural decisions they've made for the use cases they wanted to optimize for.

PlanetScale, with their latest Metal introduction, optimized for super low latency (they act like they've reinvented the wheel, lol), but they clearly have something in mind going in this direction.

Neon offers many managed features for serverless PostgreSQL that were missing in the market, like instant branching, and with auto-scaling, you may perform better with variable workloads. From their perspective, they wanted to serve other use cases.

There's no reason to always compare apples to oranges, and no reason to hate one another when everyone is pushing the managed database industry forward.

↑

I second this!

It is always about the trade-off between those two parameters.

Of course an increase in both is the optimal, but a small sacrifice in performance/accuracy for being 200% faster is worth noting. Around 10% drop in accuracy for 200% speed-up, some would take it!

What is the full stack you are using? What parts also require scaling up? DB, bandwidth orrr?