MurphyA/hacker-news huggingface dataset:
by vlovich123 | 2025-05-21 14:17:43+00:00
Rust provides all the safety guarantees of managed languages with none of the performance drawbacks. It’s precisely intended to replace C/C++ because the unsafe parts of Rust are used very sparingly and result in significantly fewer bugs and security vulnerabilities.

Safe abstractions for dealing with uninitialized memory efficiently are important in very niche scenarios to get optimal code out of the compiler and for reducing the ability to make a mistake when writing such code.

Reaching for C to do this is an emotional overreaction instead of calmly dealing with a small corner case that already has workarounds even if it does involve using unsafe
by terts | 2025-05-21 14:17:43+00:00
Hi! So for Roto, our introspection needs are actually fairly limited. We only need the `TypeId`, the type name, the size and the alignment. which Rust can give us without any additional traits. It's not possible currently to - for example - access struct fields and enum variants. That is something that I plan to add, but that might require a crate like `bevy_reflect` or `facet`.

Rust is giving me just enough information to pull the current version of. More powerful introspection/reflection is not possible without derive macros. If you're ok with derive macros though, you could look into the 2 crates I mentioned.

Hope that answers your question!
by sbarre | 2025-05-21 14:18:08+00:00
Yep maybe I've been lucky but in my 30-year career, I've worked at over a dozen companies (big and small), and I've always been well-treated and respected, and I've never felt the kind of dynamic you describe. But that isn't to say that I don't think it exists or happens. I'm sure it does.

It's everyone's personal choice to put their own lens on how they believe other people think - like your take on how "leadership" thinks of their employees.

I guess I choose to be more positive about it - having been in leadership positions myself, including having to oversee layoffs as part of an eventual company wind-down - but I readily acknowledge that my own biases come into this based on my personal career experiences.
Show HN: Super (YC W18) - Turn company data into answers & agents for your team
by christophepas | 2025-05-21 14:18:42+00:00
Hey there, Chris here

We're known for our straightforward yet powerful Knowledge Base, Slite(YCW18).We launched our AI-powered search in Feb 2023 and after getting great response and usage, we dove deeper into solving the challenge of knowledge retrieval in daily work.

That's why we're now launching our second major product, Super(https://www.super.work).

Super seamlessly connects your existing tools, providing accurate answers, streamlined workflows, automated digests, and much more.

You might wonder: Why not just link your apps together using something like an MCP? The problem is that MCPs can't handle complex knowledge retrieval effectively. MCPs are basically LLMs equipped with API toolbelts. If you've ever tried asking a complicated question through an MCP, one that needs data from multiple different tools, you've likely faced frustrating delays. MCPs slowly make API calls one after another, causing long waits while they collect data from each endpoint.

By contrast, Super quickly searches through all the data that actually matters from all of your tools simultaneously. This means you'll get your accurate answer in seconds, not minutes.

The limitations of MCP-based solutions become clear when you try to deploy them reliably within a team. They either won't index your critical content effectively, won't do it fast enough, or won't cover all your tools at once. Properly chunking, embedding, querying, and filtering data from various sources is still essential. MCPs triggering APIs can't match this integrated approach for speed and accuracy.

Moreover, Super understands the value of running multiple tasks simultaneously through LLMs. For example, one step may involve identifying search filters, while another simultaneously uses an LLM to aggregate and refine information. This parallel process quickly shapes the final, accurate answer for users.

Additionally, MCPs aren't designed for enterprise-grade use. Businesses need standardized experiences, fine-grained user permissions, and consistent access controls across multiple tools. Super addresses these requirements by indexing data beforehand while still respecting each user's access permissions.

Super offers: - Perplexity-like search experience on your team data - A growing selection of integrations with popular data sources - Customizable AI assistants tailored to your specific needs - An extension to embed Super directly into external websites you're already using - A clear path for your company to adopt AI strategically, rather than letting individual employees scatter across different, incompatible tools.

And of course... It does comes with its MCP, which makes your agentic workflows actually able to properly tap on your data.

Here's a quick video showing Super in action: https://www.youtube.com/watch?v=L5A6BRW90K4

Have you hit such walls with standard MCPs? Have you try building your own solutions?
by nixosbestos | 2025-05-21 14:20:26+00:00
Because virt-manager, virt-viewer and everything SPICE related is hot, steaming, unmaintained shit.

I've reported so many bugs it's not even funny. Audio is completely broken in my VMs now. It breaks regularly, restarting the viewer session used to fix it, now it just produces garbled ear piercing audio. No responses. No responses to issues where i ask for packaging guidance in case we don't configure it the way they expect.

It's truly unfortunate. And I'm betting that KDE is probably just using virt/spice components, but at least it won't be GTK3 near-abandonware.
by bossyTeacher | 2025-05-21 14:21:42+00:00
Every week, one of Google/OpenAI/Anthropic releases a new model, feature or product and it gets posted here with 3 figure comments mostly praising LLMs as the next best thing since the internet. I see a lot of hype on HN about LLMs for software development and how it is going to revolutionize everything. And then, reality looks like this.

I can't help but think that this LLM bubble can't keep growing much longer. The investment to results ratio doesn't look great so far and there is only so many dreams you can sell before institutional investors pull the plug.
by dinfinity | 2025-05-21 14:21:58+00:00
The study tested transformers, not LLMs.

They trained models on only task specific data, not on a general dataset and certainly not on the enormous datasets frontier models are trained on.

"Our training sets consist of 2.9M sequences (120M tokens) for shortest paths; 31M sequences (1.7B tokens) for noisy shortest paths; and 91M sequences (4.7B tokens) for random walks. We train two types of transformers [38] from scratch using next-token prediction for each dataset: an 89.3M parameter model consisting of 12 layers, 768 hidden dimensions, and 12 heads; and a 1.5B parameter model consisting of 48 layers, 1600 hidden dimensions, and 25 heads."
by austin-starks | 2025-05-21 14:22:12+00:00
TL;DR (Too Lazy; Didn’t Read):

Google I/O 2025 showcased impressive AI advancements including Imagen 4 and Veo 3 that outperform competitors in image and video generation Google demonstrates a strong financial position with Q1 2025 revenue of $90.2B and net income of $34.5B It is reasonably valued with a P/E ratio of 19.03 (lower than other FAANG stocks, including Apple) Innovative “Other Bets” like Waymo self-driving taxis are already operational and expanding Thus, I’m investing some of my NVIDIA profits into GOOGL despite regulatory risks and search advertising dependencies
by dr_dshiv | 2025-05-21 14:22:12+00:00
One reason to take these expected cost reductions more seriously is because it DOESN'T fit the desired narrative for OpenAI. Ideally, from a front-runner competition perspective, it would NOT be possible to create the same level of quality at < 1/10 the cost/energy within a year. But, distillation and other approaches seems to make this possible. There is a LOT of room for optimization with LLMs.
by nixosbestos | 2025-05-21 14:22:23+00:00
Ah yes, I'm so desensitized to the utter terrible quality of the virt* stack that I forgot that they merged "hidpi support" that was categorically worse than it being unscaled, and then just said "fuck it" for like a decade.

It's stunning that apparently not a single dev working on it has ever owned a hidpi screen apparently.
by ggandv | 2025-05-21 14:23:01+00:00
I’d argue. The CCP isn’t ideologically opposed to democracy but rather capitalism. Capitalism is an inherent feature of democracy. They despise capitalism (the Communist Party) even though they will play the long march and use it to subvert and destroy non-Communist ways of life.

Edit to add link: https://en.m.wikipedia.org/wiki/Ideology_of_the_Chinese_Comm... (“views on Capitalism”)
Ask HN: How do you promote your personal projects with a limited budget?
by javafactory | 2025-05-21 14:23:05+00:00
Hi everyone,

I’m the one who posted about my project here yesterday.

To be honest, I’ve always focused on development, and this is my first time launching something — so I’m really struggling with promotion. How do you get people to notice your product?

It’s an open-source IntelliJ plugin that automatically generates repetitive Java code. I believe it could be genuinely useful for many developers, especially those who like to streamline their workflow.

I’m not looking to make money from it — I just want more people to try it out. (I’m honestly afraid it’ll just disappear unnoticed.)

Are there any other good places (besides Reddit) where I could talk about my project? Even basic suggestions would be greatly appreciated. I'm really new to this area — I feel like I know less than an elementary school student.
by palmotea | 2025-05-21 14:24:20+00:00
> Leaving the supposed gains in programming speed aside for a moment, have you been paid 24x for that 24x productivity? Have you even been paid 1.1x for that week of work?

Don't be silly! The passive, hardworking owners are the ones that deserve all of that profit. Those are just the new expectations. He shouldn't be greedy, and should be happy that he just gets to keep his job.
by z2 | 2025-05-21 14:24:27+00:00
As a another data point, on E4B, my Pixel 6 Pro (Tensor v1, Oct 2021) is getting about 4.4 t/s decode on a picture of a glass of milk, and over 6 t/s on text chat. It's amazing, I never dreamed I'd be viably running an 8 billion param model when I got it 4 years ago. And kudos to the Pixel team for including 12 GB of RAM when even today PC makers think they can get away with selling 8.
by JPLeRouzic | 2025-05-21 14:24:53+00:00
I have interacted with Chinese people in IT for a few months, and they worked 5 days per week. I don't know how many hours they made per day.

Another interesting stat is that they live longer on average than US people.

And until recently, men retired at 60 and women at 55 yo.

https://www.bbc.com/news/articles/cpd9v48yn8ro
Show HN: Tinker with Meta's "tokenizer-free" patcher
by lucalp | 2025-05-21 14:25:38+00:00
If the future is that we tend towards replacing current tokenisation, I wanted to build intuitions around one of the core contribution of Meta's Byte Latent Transformer: entropy-based patching.

What are it's strengths and weaknesses? No better way of doing that than via tinkering with visualisations in a HF space so thought I'd share!

A few things that emerge as a result that you can try yourself:

1. robustness - high entropy means more compute will get dedicated to those bytes which include cases like low resource languages, spelling tasks etc

2. compute efficiency

2a. low entropy means less compute spent for those bytes

2b. in-context learning applies to tokenisation! It induces low entropy regions later on in the sequence and has to waste less compute!

I'm writing a blog post on an expanded version of this, updates via https://lucalp.dev or https://x.com/lucalp__
by bell-cot | 2025-05-21 14:25:56+00:00
I might take the article seriously if it openly admitted that anti-rust coatings on rebar have been a thing for a century-ish, then talked honestly about which applications this new tech was actually better for.

One clear downside to stainless-coated rebar: During construction, rebar is very commonly welded. Welding stainless ain't just the same tools & techniques as welding conventional rebar. Plus, welding stainless gets you into chromium hazmat territory.
by sbarre | 2025-05-21 14:26:02+00:00
Another great comment, thanks! Like I said elsewhere I agree things are more complicated than I made them out to be in my short and narrow response.

I agree with all your points here, the broader context of one's working conditions really matter.

I do think there's a difference between sitting back and watching things go bad (vs struggling to compensate for other people's bad decisions) and actively contributing to the problems (the "malicious compliance" part)..

Letting things fail is sometimes the right choice to make, if you feel like you can't effect change otherwise.

Being the active reason that things fail, I don't think is ever the right choice.
by ramses0 | 2025-05-21 14:26:04+00:00
I've been using vim forever, and often use "advanced" editing techniques: macros, .-repeat, :g/.../norm ..., occasional templates.

For certain projects I'd used `vscode` (with the vim plugin!), and there's definitely some helpful bits. The biggest helper for me is/was the `F2-rename-symbol` capability. Being able to "rename" securely in the whole file (or function), and across the project is super-useful.

Working with Cursor and the autocomplete is (often) pretty shockingly good. eg: when I go to rename `someVar` to `someOtherVar`, it'll prompt to `<tab>` and:

* rename the function call * edit the log lines * rename the return object value * ...etc...

In vim, I'd `*` to automatically search for `someVar`, then `cwsomeOtherVar`, (change-word), then `n.n.n.` (next, repeat, etc.)

...so my overhead (by keystrokes) is `*` (search), `cw` (change word), (`n.`) next-and-change. Five "vim" characters, and I mentally get to (or have to) review each change place.

In straight `vscode`, I can do `F2-rename` and that'll get me replace _some_ of the variables (then I still have to rename the log lines, etc).

With Cursor, I make the `cw...` and it's 90%+ accurate in "doing what I probably also want to do" with the single `<tab>` character.

It gets even more intriguing where you'll say `s/foo/fooSorted/` and it automatically inserts the `\*.sort()` call, or changes it to call `this.getFooSorted()` or `this.getSorted( foo )` or whatever.

For "cromulent" code, cursor autocomplete is "faster than vim". For people that can't type that good, or even that can't program that good, it's a freaking god-send. Adding in the `Agent...` capabilities (again, for "cromulent" code)... if you're just guiding it along: "Now, add more tests" => "Now 50% more cowbell!" => "Whoops, that section would be more efficient if you cached stuff outside the loop."

Even then, I have to have some empathy with the AI/Agent coding, "Hey... you messed up that part (btw, I probably would have messed up that part the first time through as well...)". We can't hold them to gold standards that we wouldn't meet either, but treating them as "helpful partners" really reduces the mental burden of typing in EVERY SINGLE CHARACTER by yourself.
by tastyfreeze | 2025-05-21 14:26:34+00:00
In 1900 a 20 dollar coin contained 0.9675 ounces of gold. An ounce of gold was legally defined as $20.67. No free floating gold price. A dollar coin contained 1.672 grams of gold.

1900 $1 is equal to 2025 $172

So a single dollar today will buy 1/172 of what it would in 1900. That is inflation. Not an inflation adjusted curve. Just the drastic devaluation of the dollar.
by WorldMaker | 2025-05-21 14:26:36+00:00
I think it is still useful as a function call syntax. There's a variety of data structures that people convert JSX to already, including direct-to-DOM. Choosing a blessed one seems harder than a function calling convention, and a function calling convention resembles other language things like tagged templates.

I agree that the current "auto-imports" to find that function are nonsense and far too React specific. But the current "global" approach isn't actually "require a global" it is "requires a variable in scope" so it works with "Bring-Your-Own-Import" just fine. We just need a better standard for what that BYOI function is called by default. `React.createElement` is obviously silly. I've been happy in my own projects standardizing on `jsx` as the function name. (It resembles the auto-imports, too, even if I still don't understand why React thought it needed an extra underscore.)

I think the biggest tweak that would be nice if we are also wishing for ponies would be a way to set that function per block of JSX like the way that you can tag a template. That would make it far easier than the current per-file or per-project configurations.

jsx<foo bar={qux}><zoot>bla</zoot></foo>

That doesn't look terrible. Not great either. But I'm sure the big problem with it is that it makes the `jsx < foo` less than versus `jsx<foo />` tag parsing a lot harder.

ETA: New idea, what if it was a fake dot tag .< operator?

jsx.<foo bar={qux}><zoot>bla</zoot></foo> react.<foo bar={qux}><zoot>bla</zoot></foo> snabbdom.<foo bar={qux}><zoot>bla</zoot></foo>

Maybe?
by gopalv | 2025-05-21 14:27:18+00:00
> those rates amortize and distribute the cost of storm recovery

Not exactly when it is a farm out there away from a town.

My experience is from a different era (90s) and a different kind of farm, but I spent a bunch of summers in one, which had power outages whenever the monsoons picked up.

The trouble was that there was a single line feeding the farm from about 6km away, so if that went down a single farmowner complained - the rate payers who were in a denser urban area always got priority, because there were 600+ people who shared a transformer.

The generator ran a lot when winds knocked power out, but the generator only ran when there was a big power need like running the well pumps or one of the winnowing mills. Even the winnower had pedals, because work doesn't stop.

Every bathroom had a light with a 30 minute battery in it, which came on when the power went out - I guess if they had LEDs those same batteries would be 6 hour lights.

They would have killed for solar + storage, because shipping fuel in for the generator was one of those annoying things you had to keep doing over and over again.
by bluGill | 2025-05-21 14:27:40+00:00
Unfortunately it ends before it gets to the good stuff. It has me interested that maybe PBT can find some bugs that unit testing wouldn't - however I'm not sure how to write a PBT that would catch those bugs. The obvious tests that drive PBT advocates to drink are not interesting - unit tests will catch all the errors and because there is no randomness they will catch the errors faster in general. However how do I write a property for non-trivial functions it not clear at all, and the article stops.
by Yannael | 2025-05-21 14:27:41+00:00
I put together a small interactive tool on Hugging Face Spaces that lets you compare the political compass of four models (OpenAI GPT-4o, DeepSeek DeepSeek-chat-v3-0324, X-ai Grok-beta, MistralAI Mistral-large-2411) on a set of 62 political questions.

The interface scores models along economic and social axes using political quiz data (Libertarian/Authoritarian, Left/Right), aiming to reproduce works like https://davidrozado.substack.com/p/new-results-of-state-of-t... or https://trackingai.org/political-test.

The purpose of the interface is more pedagogical (I do trainings on AI for the public at large) than political, and to offer a way to raise awareness about political biases between models or languages for non expert crowds.

It is still interesting though to observe how current state-of-the-art LLMs often lean left-of-center, and that some models (notably OpenAI's and DeepSeek's) seem to display _stronger left polarization_ when prompted in *French* as opposed to English.

The project is open-source on GitHub, and it should be easy to adapt it to other languages or even other ideological scales. Contributions or feedback welcome! https://github.com/Yannael/ai-political-bias
by cddotdotslash | 2025-05-21 14:27:51+00:00
I wish X would allow you to mute lists of people. I keep a list for insufferable VCs, and it would be nice to mute the whole list at once.

Maybe a feature request for your extension: take a list and mute everyone on it, and periodically check for new additions and mute those too. That way I can have the list be the source of truth, rather than commenting on every person I mute individually.
by silloncito | 2025-05-21 14:28:05+00:00
$Let M=Max(X,Y)$. If $X$ and $Y$ are independent then: $F_M(k) = P(M \leq K) = P((X \leq K) and (Y \leq K))$, so that

$P(X \leq K) x P(Y \leq K) = F_X(K) x F_Y(K)$. So $F_M = F_X \times F_Y$
by IanCal | 2025-05-21 14:28:05+00:00
I agree on the UX. A few basic things seem totally broken.

The flow of connecting a github account works, then disconnects, sometimes doesn't work, sometimes just errors. I can't install things that I could yesterday and my environment is just... broken? I have two versions of a repo and it works in only one.

Speed is a big thing. Not the llm stuff so much, but the setup and everything around it for each step.

Not having search cripples some cases where O3 seems incredible.

but there's a lot of places this feels like it can land tasks that often wouldn't get done. A near infinite army of juniors who can take on the lots of tiny tasks in 15-20 minutes is great. Fix some typos, add a few util functions (a task I have right now running), I even just asked it to add new endpoint to a server and it added it, migrations needed, tests and more and seems alright.

The ideal workflow in a way here is that the people asking for these things get to tag the ticket to codex/whatever, they run off and do the thing, PR lands and discussion and changes happen there, demo envs are setup and then someone can check and approve it.

edit -

To be fair, I also used firebase studio and that was worse. Blank screens, errors in the console, when I refreshed and moved around and got an actual page, it ended up failing to setup firebase. UI for editing and code totally failed after that and the explanations for how to fix it I was linked to I couldn't do.
by gustavoaca1997 | 2025-05-21 14:28:13+00:00
IMO Humans are better at understanding abstract things, taking into account not only technical requirements but also non-technical requirements. It would be horrible if I would need to argue with an AI about priorities, security concerns, etc.

Too many edge cases. Managers are working with people and we are complicated.

Will the AI Manager fight correctly about my promotion or my bonus? Will it make sure I have a good work-life balance? Will it considered I did an extraordinary job vs an underperforming job?
by abendstolz | 2025-05-21 14:28:29+00:00
match Plugin::instantiate_async(&mut store, &component, &linker).await { Ok(plugin) => { match plugin .plugin_guest_oncallback() .call_ontimedcallback(&mut store, &callback_name) .await { Ok(()) => debug!("Successfully called oncallback for {plugin_path:?}"), Err(e) => warn!("Failed to call oncallback for {plugin_path:?}: {e}"), } } Err(e) => { error!("Failed to call oncallback for {plugin_path:?}!: {e}"); } }

See the "call_ontimedcallback"? It's not a string. The compiler ensures it exists on the Plugin type generated from the .wit file.

If of course I put a wasm file in the plugin folder that doesn't adhere to that definition, that wasm file isn't considered a plugin.
by lm28469 | 2025-05-21 14:28:30+00:00
> I don't really think it's a good physical exercise

The problem is that most people don't do anything physical at all and walking is one of the easiest way to get started. Any type of activity is beneficial, you need to move for your lymphatic system to work properly and walking is perfect for that, your feet/lower legs basically are lymph pumps: https://www.mdpi.com/2813-3307/2/2/4