skysight-inc/HackerNews huggingface dataset:
Show HN: ActorCore – Stateful serverless framework that runs anywhere
Hey HN! Today we're launching ActorCore (https://actorcore.org/), a stateful serverless framework that enables deploying Cloudflare Durable Object-like workloads to any cloud.

If you're unfamiliar with stateful serverless: it's like the actor model, where each actor maintains its own isolated, persistent state. (Think Lambda functions with local storage & runs indefinitely.) It enables easily building long-running, realtime, durable, or local-first backends with the flexibility of serverless infrastructure. The most widely used implementation is Cloudflare Durable Objects, powering products like Clerk, Tldraw, Liveblocks, and Playroom.

A few months ago we launched Rivet Actors (https://news.ycombinator.com/item?id=42472519) as an open-source alternative to Cloudflare Durable Objects. After that launch, we kept hearing three common concerns:

- Vendor lock-in: Developers are hesitant to adopt a new programming model if there's no clear off-ramp. While it's straightforward to migrate a Postgres database, stateful serverless platforms can feel locked-in due to lack of viable alternatives.

- Ecosystem: Choosing a well-known database like Postgres comes with a mature ecosystem. Adopting a new model means rebuilding tooling and patterns from scratch.

- Conceptual gap: Many developers have spent their entire careers designing systems with intentionally separated state and compute. A model that merges the two can feel backwards at first.

We realized the best solution was to build a stateful serverless framework that can (a) be portable across clouds and (b) be easily extended – similar to how Hono created a unified API for traditional serverless functions across different providers. Thus, ActorCore was born.

Today, ActorCore supports running stateful serverless on Rivet Actors, Cloudflare Durable Objects, Redis, and standalone Node.js/Bun. The most common use cases include applications using collaborative, AI agent, local-first, and per-tenant database features.

State in ActorCore is an in-memory JavaScript object, with SQLite support coming later this month. State is stored in memory near your users on the edge, removing database round trips and minimizing latency due to physical distance. Additionally, state writes have tunable consistency, which enables both fully durable compute workloads and high-frequency state updates.

You may have noticed that this still leaves concern #3: the conceptual gap. While this isn't something we can solve with a framework, I've been spending ~40% of my time working on docs, content, and examples to help resolve this. ActorCore is also turning out to be community-driven as hoped, which enables more people to try and share their experience with stateful serverless.

We'd love it if you'd give ActorCore a try, read the roadmap, and/or let us know where we can improve anything. If you're hesitant about trying stateful serverless, I'd love to learn more in the comments. Looking forward to feedback!
This is the kind of pragmatic AI hack I want to see. It feels like sometimes we are forgetting why certain tooling even exists. To simplify things! No fancy vector DBs or complex architectures, just practical integration with existing data sources. Love it.
Human urine, a valuable resource as fertilizer for sustainable urban agriculture
Transformer Lab maintainer here. We'd love to build this! Please contact us on our our Discord https://discord.gg/transformerlab or Twitter https://x.com/transformerlab and we'd love to learn more and collaborate.
Get rid of the non CSPRNG function. Someone will use this to store coin and get robbed. Non-csprng has no place in this tool
Yes there is a weight on every connection. At least when I was at it gradients were talked about in reference to the solution space (e.g. gradient descent). The implication is that there is some notion of what is "correct"for some neutron to have output and then we bend it to our will by updating the weight. In Hebbian learning there isn't a notion of correct activation, just a calculation over the local environment.
Sorry to hear. I have never worked for Google or any corporation of that scale but I got my fair share of a harsh layoff two years ago (at a reasonably small company). The company used to run a hybrid shift, with specific days for remote and onsite. We got a mail (from the higher ups) a day before saying no employee should show up at the office the next day, under the guise of a fumigation exercise. The next day shows up, I am in a meeting with my colleagues (a regular standup), a fraction of my teammates receive an email with an meeting invite link. We join the meeting, our mics and cameras were automatically turned off by the host/organizer, the CEO's face spotlit in the meeting, he then delivered the news in a very cold way, the meeting ended, we were logged out of all company accounts in the next 15 minutes, that was the last team meeting we had :)
so, it doesn't tell you much.
I’ve been seeing more of this classist rhetoric on HN and I honestly don’t get it. If you truly care about workers, focus your energy on the corporations and politicians that are producing the system you are unhappy with. Belittling other, higher paid workers doesn’t advance anyone’s cause.

And FWIW, the jobless rate in tech is higher than most blue collar jobs and the national average. This guy seems good, but he faces a worse landscape for finding new employment than your fictional Joe Everyman.

Losing a job is hard for everyone, regardless of the type of job it was. Jobs are where most of our social interactions happen, and where many people’s goals and aspirations are kept. Having that ripped away hurts, regardless of the salary the job paid. Hopefully he was good at managing his money (I’ve known high paid workers that weren’t) and will land on his feet, but you don’t know his circumstances and calling him names is just being a dick.
This is basically what the OP is doing - just think of this of the cursor rule as a summary (aka a compression) of the session.

I did something similar for a small vibe-coded app. After a few back and forths to develop the first working version, I asked the LLM summarize the requirements and state of the app so far. I saved that summary into a `description.md` file, and can include it in a fresh conversation.

I was using simonw's llm so adding a new feature or making a change looks like:

`llm -f description.md -f code.py "Instructions for making another change."`
Funny how they're bad at this from start to end. Most of these comments talk about the "end" part, but don't forget: Google has a notoriously laggy hiring process with extreme delays and an unacceptably high level of silence on important issues from recruiters.

I have been ghosted so heavily from recruiters TWICE at Google when I was literally telling them "Hey I have offers from $x and $y and I need to decide in 2 weeks. Is there any chance I can get an offer from Google beforehand?" only to receive complete silence and had to go with a different offer. 1-2 months later, the recruiter gets back to me with an offer, I have to decline.

The most hilarious part about it: after I decline, I get interviewed by some team at G that tries to figure out why people declined. I guess they're expecting some teachable moment, some nuance and insight. My answer both times started with "lemme show you an email thread that is very one-sided..."
I've tried coding with AI for the first time recently[1] so I just joined that statistic. I assume most people here already know how it works and I'm just late to the party, but my experience was that Copilot was very bad at generating anything complex through chat requests but very good at generating single lines of code with autocompletion. It really highlighted the strengths and shortcomings of LLM's for me.

For example, if you try adding getters and setters to a simple Rect class, it's so fast to do it with Copilot you might just add more getters/setters than you initially wanted. You type pub fn right() and it autocompletes left + width. That's convenient and not something traditional code completion can do.

I wouldn't say it's "mission critical" however. It's just faster than copy pasting or Googling.

The vulnerability highlighted in the article appears to only exist if you put code straight from Copilot into anything without checking it first. That sounds insane to me. It's just as untrusted input as some random guy on the Internet.

[1] https://www.virtualcuriosities.com/articles/4935/coding-with...
What role does governmental industrial policy have your in thesis?
I don't think they create it, they just use some template that comes with it.
I don't even agree with the self-proclaimed legal experts in the replies.

Employers generally assume liability for torts (civil liability arising from wrong-doings) vicariously. For example if an employee somehow puts rat poison into a customer's burger, the employer is automatically liable for that, because they are responsible for the employee's actions. (See eg. https://en.wikipedia.org/wiki/Vicarious_liability )

But if on the other hand a recently laid-off ex-employee sneaks back to the restaurant and then adds rat poison to the burgers, the liability of the employer isn't automatic (you can claim they should have done better with their security etc., but it is probably a defense to say they did all reasonable steps to secure the facilities).

So yeah, I call bullshit. More likely is that the C-suite just cargo-culted some "layoff best practices" and it just became a thing you did without questioning.
if someone is democratically elected they can’t have en extreme ideology?
Previous thread,

https://news.ycombinator.com/item?id=31478795 ("The math prodigy whose hack upended DeFi won’t return funds" (2022) — 399 comments)
"Superior outputs" seems to have stagnated at Elon companies: From Falcon 9 to Starship, and from Model Y to Cybertruck, for example.
The difficult irony here is that you think your attitude is progressive, but it is regressive because it makes solidarity (and therefore the benefits of solidarity: unions, worker power, compression of the income distribution) impossible.
Code is not law. Law is law.
FWIW - that is what claude code does, at least how I use it. It uses the BashTool to call `gh`
> often

Often being about 30% of the time in my experience
I hate to say it...but this is how working for a company works. It's more prevalent at the largest ones and less so at the smallest ones, but it's just the norm.

In the US, it's at-will employment. You can leave, or be fired, at any time - for virtually any reason. (As long as it doesn't break discrimination laws) Investors only care about quarterly returns, and so you have to expect a publicly-traded company may let people go for that reason alone.

They're not your friends. They're not your family. You exchange hours of your life for money. That's all. It sucks, but that's just how it is. Google is no exception, it is one company like literally all others.
CodeRabbit V/S Panto AI|AI Code Review Benchmarking
This would be a shocking opinion, if we weren't in unprecedented times.

I wish we had more empathy and be kinder to people going through rough times, regardless of their wealth or position, or the duopoly they work for even, but it's also hard to completely ignore when the effect and impact is so huge.

Now, if you it makes you physically ill, I also wish you either find help or can get out of the situation you're in. Sincerely.
my cofounder has been pivoting across different ideas for the past 4 years now after their last company failed. while admirable, the inability to stick to idea/industry/persona, to me, seems like a massive red flag. we started the company for the sake of starting a company, ngl.

what does a good cofounder breakup look like?
why just human?
They would sell you for meat if they could.

I had my access hard cut off and laptop locked, a cold reminder that your relationship goes as far as the business will allow.

Always, ALWAYS build your homey network at your job, because that is your door to walking on to the next job.

Be sure to try to get the best severance possible, take time off, explore opportunities. You often won't have that kind of pressure off moment if you're serious about your career so take advantage.

I'm a hired gun for now for academia and a small startup and I've probably never been happier career wise. I work with non-fake employees, and solve problems that make money. No 401k for now, but my sanity is more valuable to me after the circus of the last year at my old place. (Fake employees in VP position, director position, both fired 1y after I left.)
It's probably a typo, but a user rather uses short lived Cert, not a CA. CA (certificate authority) issues a Cert. CA doesn't have to be (and likely isn't) in users full control.

Hosts answering to connections using that cert don't have to send anything back to CA. They just need rules "I trust this CA. If a user has a cert from it, and this precise combination of fields match, I consider this user's response trustworthy".
I've seen some contestants(?) plane at a slight angle too. I feel like this would also assist with achieving a cleaner result. I know I do this with my own push-style planer.
I use Linkding for my bookmarking. It has the ability to snapshot the links by using SingleFile, which is super handy cause it produces a single .html file that you can send or save separately if you want.

To save logged in content, you can either pass it cookies.txt with the login cookies it needs, and it works pretty well.
Alternatively, you can also use the SingleFile extension to snapshot what you want and upload it in place of the automated snapshot. This is also handy because the extension allows you to remove private data prior to screenshot, such as your name or username.

I personally have cookies in place for most common social media sites that need login (twitter, reddit), and if I need to snapshot something else occasionally, I do it manually and upload it to Linkding.

https://linkding.link/

https://linkding.link/archiving/

https://www.getsinglefile.com/
Show HN: PDF Diff Tool – Show differences between two PDF files visually
If you're on your laptop, there's already a great tool for diffing PDF tools: https://github.com/vslavik/diff-pdf

It has a great 'view' mode which shows the two PDFs overlaid in different colors:

diff-pdf --view a.pdf b.pdf

I wanted something similar I could use on mobile, even if it's not as good as vslavik's tool. This is it.
I wanted to offer that the (Rancher Desktop, lima, colima, etc) products also launch a virtual machine and install docker on it, so one doesn't need Docker Desktop to do that. My experience has been that the choice of "frontend" to manage the VM and its software largely comes down to one's comfort level with the CLI, and/or how much customization one wishes over that experience
Maybe, maybe not, but right now humans are the ones who are exploiting it.
It couldn't be more obvious that's a joke, though.
Americans are very proud of the innovations in the latest model of the Orphan Crushing Machine.
Perhaps it's simply because (1) LLMs are designed to be helpful and maximally responsive to requests and (2) human adults have, generously, decades-long "context windows"?

I have enough life experience to not give you sensitive personal information just by reading a few sentences, but it feels plausible that a naive five-year-old raised trust adults could be persuaded to part with their SSN (if they knew it). Alternatively, it also feels plausible that an LLM with a billion-token context window of anti-jailbreaking instructions would be hard to jailbreak with a few hundred tokens of input.

Taking this analogy one step further, successful fraudsters seem good at shrinking their victims' context windows. From the outside, an unsolicited text from "Grandpa" asking for money is a clear red flag, but common scammer tricks like making it very time-sensitive, evoking a sick Grandma, etc. could make someone panicked enough to ignore the broader context.
Lula is not far left by any reasonable definition of both "far" and "left"

> Did Lula not do that?

I'm not an expert and not that knowledgeable about the case but it seems to me the accusation -famously- stated things like "We have no hard proof" (...) "(but) we are convinced he did it"

Again - if the accusation states 'We have no proof', under assumption of innocence, yeah; he "didn't do it"
I don’t know if replacing Elixir is even one of the top 10 reasons Gleam exists. People don’t usually pick a platform and then pick a language.

Many times a language develops into an option by bundling features. In Gleam’s case, they bundled a certain type system, extreme developer convenience, and optionally features from BEAM.
Python is an interpreted language with a compiler
A hidden strategy: How SARS-CoV-2 uses fibrinogen to evade the immune system
Detatched Observations: Enqueue Phase
That's not Go-specific, it's just how static linking works. As nolist_policy advised, it's more useful and precise to intercept programs at the syscall (rather than library call) boundaries. Programs are free to do all sorts of insane stuff, there was e.g. a Scheme interpreter that kept growing the stack until it caught SIGSEGV, at which point it'd run a compacting GC and reset the stack pointer. ¯\_(ツ)_/¯

Regarding LD_PRELOAD, I highly doubt that this is required by POSIX. macOS (which is a certified UNIX) uses DYLD_INSERT_LIBRARIES instead. OpenBSD (which is known for their pedantic documentation) uses LD_LIBRARY_PATH, doesn't mention any standards, and refers the reader to SunOS 4.0. If this is somehow standardised, I'd love to read the actual document.
A piecewise function is definitely not what I'd call "complicated".
> if Google treats their most hardworking engineers like this they are creating a culture of minimal effort

This is bizarre to me because my impression from three years ago was that they were trying to correct from that, and it sounds like they overcorrected right back to it. I spoke with a Google engineer I think in 2022, he had heard rumors there were going to be layoffs on his team, and he had sent a message to a more senior team member that he hadn't heard from in months to let her know that she should, to put it delicately, maybe manage her visibility better. And she responded that she had lost interest in the job anyway, hadn't done anything except respond to emails and messages in over a year, and had 99% transitioned to managing a collection of properties she had been accumulating over the years, so if he heard she got laid off, he shouldn't feel bad for her. I'm pretty sure that was in 2022.

To see Google go from tolerating being ghosted by highly compensated senior+ engineers in 2022 to laying off people who were doing excellent and high-profile work in 2025 must be surreal for people inside Google. If this is all accurate, they swung the pendulum from one zone of encouraging laxity and disloyalty right through the healthy zone and into another zone of encouraging laxity and disloyalty with dizzying speed.
There are also color science packages like this one that let you do conversions to various spaces - https://www.colour-science.org/
There are more regulations around employees than contractors here also, which often makes it not worthwhile for short term workers. Those regulations just mostly aren't around when you may terminate employment.

E.g. the entire I-9 thing and other IRS paperwork, who (if anyone) is responsible for various insurances (unemployment insurance, workers comp, liability insurance, etc), minimum wage and overtime for hourly employees, etc. Many things depend on this distinction.

I can't speak to differences from Europe as I am not familiar with that side of the Atlantic.
Yeah well this comment thread is right at the bottom of the page, so it's not gonna happen anytime soon.

Top of the page indicates they're more interested in infighting (calling him spoiled).
Aside from "the right tool for the right job" kind of conversation, there's one inherent aspect to chasing the most popular language (given that you find an actual ranking that's put up meaningfully, which I don't think the TIOBE index is): you may find more people able and willing to work with it, which can sometimes be a feature.

I've been in a company which had a major refactor need, and they took the opportunity to slowly convert their backend from PHP to Go* because they couldn't find any good PHP developer (let alone any willing to work in PHP). For the actual project, it kinda worked, but for the recruitment, it went from not having any applicants / very mediocre people, to having way more people applying, and a few competent ones in that pool.

* As to whether that was the right choice, that's a completely different topic...
How does email support structured metadata? Are you talking about X headers?
The path to open-sourcing the DeepSeek inference engine
It's not just about whether you yourself use Google Translate, it's that - much more than anywhere else I've ever travelled - Japanese people will regularly use Google Translate to communicate with you, usually by typing or speaking into their tablet and then showing you the machine translation.
agreed - in hindsight, cofounder compatibility was low. i met them at a networking event and then started tinkering on ideas.
But first a Communist revolutionary. Interesting and also kind of unfortunate that those who seek fundamental change in political formulations seem frequently to thrash about like this. Moderate incrementalism doesn't get as much attention or press but seems a highly competitive alternative.
How this works in traditional finance is that the big funds would screw the small guy that beats them (especially if they're from a foreign country). They claim that they use unfair or illegal practices, but the reality is that they're not that different to their own.

Ultimately the rules are written by people who look legitimate, and/or those who capture regulators.
I've earned stock options from three startups and none of them ever went public. The only company that ever actually paid me equity was Amazon and it was a pretty big payout. You will earn a lot more with RSUs than options.
Large Language Models Improve Document-Level AI Translation
I'm only familiar with UK rules on the topic, and of course the UK is no longer in the EU, but here at least the standard for determining employment status is quite complicated. The ability to work for multiple clients is one of the factors, as it speaks to the control and mutuality-of-obligation tests set by IR35, but it would probably not (alone) be enough to determine employment status either way.

> If it was legal to work in the office of your only "client" 40 hours a week on a permanent basis, then any EU company could ignore the entire employment legislation of their real country by setting up a shell subsidiary in the US.

That wouldn't work because it would be an obvious sham designed mainly to avoid the EU company's responsibilities under employment law. Courts see through those shams very quickly.

Technical people -- including me -- like to try and reduce the law to a series of digital if/then/else tests, but reality is much more analogue. If you're one of a small number of highly-experienced remote contractors engaged by a US-based client with no local subsidiary, the authorities are likely to accept the arrangement, or at least not to spend significant amounts of time investigating it. If you're one of very many Uber-driver-like "contractors" working for a company that is obviously dodging its local employment law obligations, then they're much more likely to be interested.