MurphyA/hacker-news huggingface dataset:
by Kerollmops | 2025-04-14 14:55:44+00:00
Meilisearch decided to use hybrid search and avoid fusion ranking. We plan to work on reranking soon, but as far as I know, our hybrid search is so good that nobody asked for reranking. You can read more about our Hybrid search in our blog post [1].

About streaming ingestion support. Meilisearch support basic HTTP requests and is capable of batching task to index them faster. In v1.12 [2], we released our new indexer version that is much faster, leverages high usage of parallel processing, and reduces disk writes.

[1]: https://www.meilisearch.com/blog/hybrid-search [2]: https://github.com/meilisearch/meilisearch/releases/tag/v1.1...
by pie_flavor | 2025-04-14 14:56:07+00:00
Unfortunately it is also false (if taken out of context; Anubis rounds the time to the nearest week, which is probably good enough if the next-nearest week is valid too). Clock desync for a variety of reasons is pervasive - you can't expect the 10th percentile of your users to be accurate even to the day, and even the 25th percentile will be five minutes or so off.
by snarf21 | 2025-04-14 14:56:11+00:00
It is all about purpose and hope and expectations. It is why 90% of the satisfaction of a vacation is from the planning. We highly underestimate the mental health benefits of a hobby. They are also a great place to make friends and connect with others, especially as we get older. People deep in a hobby will gladly spend hours helping n00bs and will talk your ear off about all the ins and outs. There are also lots of hobbies that have almost no barrier to entry, just the willingness to try something new.

We'd all be a lot happier if we spent more time on a hobby and less time streaming shows.
by adeptima | 2025-04-14 14:56:30+00:00
Meilisearch is great, used it for a quick demo

However if you need a full-text search similar to Apache Lucene, my go-to options are based on Tantivy

Tantivy https://github.com/quickwit-oss/tantivy

Asian language, BM25 scoring, Natural query language, JSON fields indexing support are all must-have features for me

Quickwit - https://github.com/quickwit-oss/quickwit - https://quickwit.io/docs/get-started/quickstart

ParadeDB - https://github.com/paradedb/paradedb

I'm still looking for a systematic approach to make a hybrid search (combined full-text with embedding vectors).

Any thoughts on up-to-date hybrid search experience are greatly appreciated
by mock-possum | 2025-04-14 14:56:31+00:00
LLMs are usually shit at this kind of wordplay, they don’t understand the rules - words that begin or end or include particular letters, words that rhyme, words with particular numbers is syllables - they’ll get it right more often than wrong, maybe, but in my experience they just aren’t capable catching wrong answers before returning them to the reader, even if they’re told to check their work.
by jacobr1 | 2025-04-14 14:56:52+00:00
Right ... the best way to think about MCP right now flipping the switch from every app/agent developer building their own client wrappers around 3rd party APIs to either the API providers building them or community maintained wrappers. But all that gives it is a large toolbox. Like NPM or PyPi or any Apt or any our package maintainer. You still need systems to orchestrate them, secure them, define how to use them, etc ... The next-gen of langchains will be all the much better for having a big toolchest ... but it doesn't negate the need for us to innovate and figure out what that will look like
Show HN: ActorCore – Stateful serverless framework that runs anywhere
by NathanFlurry | 2025-04-14 14:57:25+00:00
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!
by erikerikson | 2025-04-14 14:57:53+00:00
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.
by kwakubiney | 2025-04-14 14:58:02+00:00
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 :)
by yojo | 2025-04-14 14:58:29+00:00
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.
by ddkto | 2025-04-14 14:58:37+00:00
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."`
by _huayra_ | 2025-04-14 14:58:48+00:00
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..."
by AlienRobot | 2025-04-14 14:58:53+00:00
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...
by hnfong | 2025-04-14 14:59:19+00:00
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.
by Night_Thastus | 2025-04-14 15:00:04+00:00
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.
by makeitdouble | 2025-04-14 15:00:15+00:00
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.
by stuck12345 | 2025-04-14 15:00:20+00:00
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?
by anarticle | 2025-04-14 15:00:26+00:00
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.)
by szszrk | 2025-04-14 15:00:27+00:00
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".
by 5evOX5hTZ9mYa9E | 2025-04-14 15:00:44+00:00
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/
by rahimnathwani | 2025-04-14 15:00:48+00:00
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.
by mdaniel | 2025-04-14 15:00:57+00:00
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
by jcalx | 2025-04-14 15:01:18+00:00
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.
by gota | 2025-04-14 15:01:21+00:00
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"
by h506001 | 2025-04-14 15:01:30+00:00
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.
by rollcat | 2025-04-14 15:01:57+00:00
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.
by dkarl | 2025-04-14 15:02:11+00:00
> 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.
by amalcon | 2025-04-14 15:02:42+00:00
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.
by Ragnarork | 2025-04-14 15:03:04+00:00
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...
by gnfargbl | 2025-04-14 15:04:04+00:00
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.