frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Show HN: Remote MCP server testing tool

https://check-mcp.mocha.app/
1•bluesnowmonkey•40s ago•0 comments

Cascading retrieval with multi-vector representations

https://www.pinecone.io/blog/cascading-retrieval-with-multi-vector-representations/
1•gk1•4m ago•0 comments

Earn $200 by referring only. FREE

https://waitlister.me/p/trading-platform-of-the-future
1•DavidvsGoliath•5m ago•0 comments

What a bumble bee chooses to eat may not match its ideal diet

https://phys.org/news/2025-07-bumble-bee-ideal-diet.html
1•PaulHoule•5m ago•0 comments

Shutting Down Clear Linux OS

https://community.clearlinux.org/t/all-good-things-come-to-an-end-shutting-down-clear-linux-os/10716
4•todsacerdoti•8m ago•1 comments

Nuxt Joins Vercel

https://vercel.com/blog/nuxtlabs-joins-vercel
1•rattray•12m ago•1 comments

The Kap Programming Language

https://kapdemo.dhsdevelopments.com/examples.html
2•thunderbong•18m ago•0 comments

A Software for One

https://www.jasonthorsness.com/30
2•jasonthorsness•18m ago•0 comments

Women Are Falling Behind in America's Return to the Office

https://www.wsj.com/lifestyle/careers/return-to-office-gender-gap-236392aa
4•bdev12345•19m ago•0 comments

Astronomer launches internal investigation after viral Coldplay video

https://www.cnn.com/2025/07/18/entertainment/coldplay-concert-kiss-cam-astronomer-investigation
2•bb88•19m ago•0 comments

Build your CV on Subreply as a LinkedIn alternative

https://subreply.com/lm
4•lcnmrn•23m ago•0 comments

Curse Not the King

https://daringfireball.net/2025/07/curse_not_the_king_cbs_colbert_trump
2•Bogdanp•24m ago•0 comments

The Physics of Dissonance (MinutePhysics) [video]

https://www.youtube.com/watch?v=tCsl6ZcY9ag
1•jerf•29m ago•0 comments

Billionaire Gabe Newell: pitching VCs makes no business sense

https://www.pcgamer.com/gaming-industry/multi-billionaire-gabe-newell-says-the-whole-startup-culture-of-pitching-vcs-for-capital-makes-no-business-sense-a-great-way-of-destroying-money-and-wasting-peoples-time/
6•e2e4•29m ago•0 comments

Ccusage: A CLI tool for analyzing Claude Code usage from local JSONL files

https://github.com/ryoppippi/ccusage
12•kristianp•30m ago•2 comments

Fuzzing macOS Userland (For Fun and Pain)

https://marqcodes.com/fuzzyingforfun.html
1•N3Xxus_6•31m ago•0 comments

Free Online Minesweeper

https://www.freeonlineminesweeper.com
1•avonmach•32m ago•0 comments

DHH – I Hate TypeScript (3 min video)

https://www.youtube.com/watch?v=tyjUH5TLSTM
3•rmason•38m ago•0 comments

Show HN: Interactive Bash tutorial that runs in the browser

https://sandbox.bio/tutorials/bash-script
2•raboukhalil•40m ago•0 comments

Show HN: Castream – Native iOS/Android IRL multistreaming app

1•acabralto•41m ago•0 comments

There Is No Antimemetics Division – A Novel (2025)

https://www.penguinrandomhouse.com/books/783041/there-is-no-antimemetics-division-by-qntm/
2•Duanemclemore•44m ago•1 comments

First earthquake, then fire: UC San Diego researchers test steel building

https://www.kpbs.org/news/science-technology/2025/07/17/first-earthquake-then-fire-uc-san-diego-researchers-test-steel-building
2•littlexsparkee•46m ago•1 comments

Ask HN: What are your favorite open source AI agent implementations?

2•kanodiaashu•47m ago•0 comments

Node.js 18 is being deprecated

https://vercel.com/changelog/node-js-18-is-being-deprecated
1•ananddtyagi•51m ago•0 comments

EPA says it will eliminate its scientific reseach arm

https://www.nytimes.com/2025/07/18/climate/epa-firings-scientific-research.html
42•anigbrowl•52m ago•6 comments

Vibe coding? AI assisted coding? I prefer being an AI micromanager [video]

https://www.youtube.com/watch?v=3gnfOnhC1EA
5•godot•58m ago•0 comments

"Pitch in " Anti-Litter PSA (1973) [video]

https://www.youtube.com/watch?v=Sba0GzhZ088
1•petethomas•1h ago•0 comments

Agents Built from Alloys

https://xbow.com/blog/alloy-agents/
2•azhenley•1h ago•0 comments

US EPA cutting workforce by 23%, closing research division

https://www.reuters.com/legal/government/us-epa-cutting-workforce-by-23-closing-research-division-2025-07-18/
15•pseudolus•1h ago•1 comments

I'm Rebelling Against the Algorithm

https://varunraghu.com/im-rebelling-against-the-algorithm/
3•Varun08•1h ago•0 comments
Open in hackernews

Rust Devs Think We're Hopeless; Let's Prove Them Wrong (With C++ Memory Leaks)

https://www.babaei.net/blog/rust-devs-think-we-are-hopeless-lets-prove-them-wrong-with-cpp-memory-leaks/
27•zdw•2mo ago

Comments

eptcyka•2mo ago
Memory leaks are by far the least interesting class of defect that Rust helps with - leaking memory is safe.
genter•2mo ago
Until the kernel kills you for being OOM.
YZF•2mo ago
That's still safe.

EDIT: Safe in the sense you're not writing into memory you don't own, e.g. write after release, buffer overflows etc.

scotty79•2mo ago
Program that no longer runs is the safest.
aquariusDue•2mo ago
For true safety we must prevent it from being written in the first place /s
dmit•2mo ago
That's the true meaning of backward compatibility. The [backward] refers to the time scale.
drivingmenuts•2mo ago
stomps butterfly

I've just saved untold generations from certain calamity.

** 6,000,000 years later **

Butterfly King: This chimpanzee-descended motherfucker ….

airstrike•2mo ago
I'll add that even safety itself is not the sole reason why some people prefer Rust. There's a lot to Rust besides that and sometimes it's not about memory safety as much as it is about steering you into patterns Rust devs perceive as better overall.
jayd16•2mo ago
Possible attack vector, though.
andrewflnr•2mo ago
The least interesting attack vector. You can fix it by rebooting.
Arnavion•2mo ago
And in fact is not even something that Rust does differently from C++. Memory releases in Rust are handled by dtors just like they are in C++. What a weird article.

(The only difference is that Rust defaults to moving while C++ defaults to copying, and Rust moves don't leave a moved-out object behind while C++ does, so the dtors in Rust are simpler and called fewer times than the equivalent C++ code.)

dmit•2mo ago
Yes, the only difference.
api•2mo ago
The problem with unsafe languages is not that you can’t write safe code in them with skill and discipline.

The problem is that programmers don’t always do that, either because they are not that experienced or they are in a hurry.

The real danger is when code is long lived and worked on by multiple people. One bad commit after a late night hacking session and now there is a zero day just waiting to be discovered.

Safe languages don’t rule that out but they make it profoundly less likely.

bluGill•2mo ago
I write C++ all the time and I still cannot convince many developers to use unique_ptr over new. It isn't that hard to write code that doesn't leak but if you bypass the language features it cannot help you.

for that matter though I've seen rust programmers put everything in unsafe.

on_the_train•2mo ago
There's static analysis which can effectively force these things. C++ problems are self-inflicted
bluGill•2mo ago
There is but we have code predating c++11 that isn't worth rewriting. So the static analisys is off. We do use lots of static analisys but that one is too hard to fix all the old code that we have decades of proff works and isn't leaking (much?)
andrewflnr•2mo ago
I mean, a sufficiently safe language would rule it out. Either one not expressive enough to express memory unsafety (i.e. GC or fully linear types with no escape hatches) or one that requires a machine checked proof of safety to compile. These options just happen to be too big of a pain in the assembly for today's appetite.
api•2mo ago
There are lots of languages where true memory bugs are impossible. As you say they are higher level and usually GC.
andrewflnr•2mo ago
Right, the interesting case would be the formal proof. Though, I suspect there are fewer high-level languages where memory bugs are actually impossible than you would naively think. I've segfaulted Python by accident, only using the standard library (concurrency shenanigans if I recall). You can probably do worse if you try. To make a truly memory-safe language, you would need to carefully design and implement the standard library, disallow all native code extensions, and probably more I'm not smart enough to figure out. So, not Java, not Python. Maybe some Schemes?
shmerl•2mo ago
No, C++ is hopeless. No need to bend over backwards to try to disprove it. It's not only about memory safety, some of it is about legacy stuff and backwards compatibility it's forever stuck with.
tom_•2mo ago
This only works with the VC++ CRT, which is potentially a bit limiting!

Also, the DEBUG_NEW thing is useless in practice since, from memory, it stops you using placement new, and dependencies typically don't participate, so a zillion unlabeled leaks is the usual result from the common case of you failing to call some dependency's free function.

And the allocation IDs (and therefore _CrtSetBreakAlloc) are pretty worthless in practice for multithreaded programs, because the allocation order isn't deterministic.

I use the LEAK_CHECK_DF flag in the programs I write (and the CHECK_ALWAYS_DF is worth investigating too), but the only point is to indicate whether there are leaks on exit, yes/no. If no, great; if yes, well that's useful information, but the actual output is almost never helpful. (Though occasionally I do somehow introduce a leak from something that happens before the first thread is created.)

yusina•2mo ago
It's 2025 and we are still discussing memory leaks. The very existence of this article is an indication that C++ (used like that) has an issue. Non-kernel programmers should not even be able to create memory leaks by mistake.

Well, unless they are doing something incredibly stupid including stepping over several explicit warnings of "don't do this unless you are very sure about what you are doing".

teleforce•2mo ago
It's really a shame isn't it? It's 2025 and we still have no programming languages that have impeccable GC for automatic memory management rather than forcing programmer to wrestling and fighting for manually managing the memory [1].

Auto industry kind of solved this automation mechanism for example with the new high performance Toyota GR Corolla has a new automatic gear transmission that's proven as fast if not faster than the manual version [2]. The same goes to F1, the epitome of car racing performance.

[1] Understanding Memory Management, Part 5: Fighting with Rust (101 comments):

https://news.ycombinator.com/item?id=43882291

[2] 2025 Toyota GR Corolla's New Automatic Gearbox Democratizes Fun:

https://www.caranddriver.com/reviews/a62672128/2025-toyota-g...

linotype•2mo ago
I’ve seen way more comments from C++ developers complaining about Rust developers insulting them than I’ve seen Rust developers actually insulting C++. It’s weird to see how attached people are to programming languages, though it’s weird to me too how attached people are to ICE/drivetrains.
sunrunner•2mo ago
I think that's because the Rust developers are having too much fun sitting on their high horse shouting about how great the horse is to need to spend time yelling about the people _not_ on the horse, while the C++ developers don't have a horse to yell about so need one to yell _at_ instead.
squirrellous•2mo ago
It’s about jobs and livelihoods, even if not everyone will admit it. It’s easy to emotional when the argument boils down to “your skills are now outdated, go learn a better one”.
fithisux•2mo ago
c++ is a huge language, with lots of backwards compatibility.

I think c++ should keep the good modern things and fork (restart) from there by breaking backwards compatibility, c++23 will be frozen with some fixes.