frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Noncoders using AI to prompt their ideas into reality. It's called 'vibe coding'

https://www.nbcnews.com/tech/tech-news/noncoders-ai-prompt-ideas-vibe-coding-rcna205661
1•Kerrick•18s ago•0 comments

Chrome Web Store Keyword Research Tool

https://webextension.net/tools/webstore-keyword-analysis
1•trungpv1601•4m ago•0 comments

How Cursor and Windsurf Work Under the Hood

https://diamantai.substack.com/p/the-hidden-algorithms-powering-your
1•vantiro•4m ago•0 comments

Scientists turn lead into gold for first time, but only for a split second

https://abcnews.go.com/Technology/scientists-turn-lead-gold-1st-time-split/story?id=121762241
1•mraniki•6m ago•0 comments

NetworkOcean

https://www.ycombinator.com/companies/networkocean
1•n2d4•8m ago•1 comments

Computers That Can Run Backwards (2017)

https://www.americanscientist.org/article/computers-that-can-run-backwards
1•todsacerdoti•9m ago•0 comments

Apple's Widget Backdoor [video]

https://www.youtube.com/watch?v=NdJ_y1c_j_I
1•lurkersince2013•9m ago•0 comments

Universal flu vaccine project puzzles scientists

https://www.npr.org/sections/shots-health-news/2025/05/13/nx-s1-5384934/trump-universal-flu-vaccine
1•geox•12m ago•0 comments

Wearipedia Find Wearable Performance

https://wearipedia.com/
1•husamia•15m ago•0 comments

Ask HN: Anyone else use a single gigantic .txt file as a notetaking solution?

3•superconduct123•17m ago•0 comments

Horoscopes for children, but each one just tells you to get your kid vaccinated

https://sproutsign.com
1•matt_kirkland•20m ago•0 comments

DeepSeek’s ‘tech madman’ founder is threatening US dominance in AI race

https://www.bloomberg.com/news/features/2025-05-13/deepseek-races-after-chatgpt-as-china-s-ai-industry-soars
2•blumpy22•22m ago•1 comments

Can a Photograph and AI Help Predict Who Will Survive Cancer Treatment?

https://www.nytimes.com/2025/05/08/well/biological-age-faceage.html
2•bookofjoe•34m ago•1 comments

Sotheby's – Modern Evening Auction – Tue May 13 25 [video]

https://www.youtube.com/watch?v=bnKW3ydMsMQ
2•handfuloflight•38m ago•0 comments

Zillow to bar publicly marketed listings not shared via MLS

https://www.realestatenews.com/2025/04/10/zillow-to-bar-publicly-marketed-listings-not-shared-via-mls
3•gscott•39m ago•0 comments

Eating ginger/turmeric/cinnamon can interfere with prescription medication

https://theconversation.com/why-eating-too-much-ginger-turmeric-or-cinnamon-could-interfere-with-your-prescription-medication-255527
1•gnabgib•42m ago•0 comments

Live Real-Time Translator

https://talkpersona.com/translate/
2•JM_SG•1h ago•0 comments

Chris Hadnagy vs. DefCon Dismissed with Prejudice [pdf]

https://storage.courtlistener.com/recap/gov.uscourts.wawd.329575/gov.uscourts.wawd.329575.119.0.pdf
4•healsdata•1h ago•0 comments

Now you can Airbnb more than an Airbnb

https://www.airbnb.co.uk/release
2•mellosouls•1h ago•1 comments

What It Takes to Ship

https://krishna.github.io/posts/what-it-takes-to-ship/
1•kenshi•1h ago•0 comments

Post-Labor Economics Lecture 01 [video]

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

'Accessibility and Rust' live podcast recording session at RustWeek

https://gribnau.dev/posts/rustweek-accessibility-and-rust-podcast/
1•foresterre•1h ago•0 comments

LLM Interviews: Vector DBs

https://mburaksayici.com/blog/2025/05/06/llm-interviews-vector-dbs.html
3•mburaksayici•1h ago•0 comments

Major world system dust particle kalpas

https://www.nichirenlibrary.org/en/dic/Content/M/44
3•debo_•1h ago•0 comments

Map of Palaeohispanic Coins and Inscriptions

http://hesperia.ucm.es/consulta_hesperia/mapas.php
14•brendanashworth•1h ago•0 comments

Cognitronics and the Longest Running Voice in Telephony [video]

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

IterGen: Iterative Semantic-Aware Structured LLM Generation with Backtracking

https://arxiv.org/abs/2410.07295
1•tough•1h ago•0 comments

ROCODE: Integrating Backtracking Mechanism and Program Analysis in LLMs for Code

https://arxiv.org/abs/2411.07112
1•tough•1h ago•0 comments

SRLCG: Self-Rectified Large-Scale Code Generation, CoT, Dynamic Backtracking

https://arxiv.org/abs/2504.00532
1•tough•1h ago•0 comments

AI #115: The Evil Applications Division

https://thezvi.substack.com/p/ai-115-the-evil-applications-division
1•paulpauper•1h ago•0 comments
Open in hackernews

How (memory) safe is Zig? (2021)

https://www.scattered-thoughts.net/writing/how-safe-is-zig/
22•vortex_ape•3h ago

Comments

90s_dev•2h ago
> But it does not nearly approach the level of systematic prevention of memory unsafety that rust achieves.

Unless I gravely misunderstood Zig when I learned it, the Zig approach to memory safety is to just write a ton of tests fully exercising your functions and let the test allocators find and log all your bugs for you. Not my favorite approach, but your article doesn't seem to take into account this entirely different mechanism.

nine_k•2h ago
I suppose you can even ship the test/logging allocator with your production build, and instruct your users to run your program with some option / env var set to activate it. This would allow to repro a problem right where it happens, hopefully with some info helpful for debugging attached.

Not a great approach for critical software, but may be much better than what C++ normally offers for e.g. game software, where the development speed definitely trumps correctness.

KerrAvon•1h ago
What that means, though, is that you have a choice between defining memory unsafely away completely with Rust or Swift, or trying to catch memory problems by a writing a bunch of additional code in Zig.
TimSchumann•1h ago
I’d argue that ‘a bunch of additional code’ to solve for memory safety is exactly what you’re doing in the ‘defining memory safety away’ example with Rust or Swift.

It’s just code you didn’t write and thus likely don’t understand as well.

This can potentially lead to performance and/or control flow issues that get incredibly difficult to debug.

ajross•1h ago
Weird that Swift is your totem for "managed/collected runtime" and not Java (or C#/.NET, or Go, or even Javascript). I mean, it fits the bill, but it's hardly the best didactic choice.
90s_dev•53m ago
What if -- stay with me now -- what if we solved it by just writing vastly less code, and having actually reusable code, instead of reinventing every type of wheel in every project? Maybe that's the real secret to sound code. Actual code reuse. I know it's a pipedream, but a man can dream, can't he?
nanolith•2h ago
There is a third category of memory and other software safety mechanisms: model checking. While it does involve compiling software to a different target -- typically an SMT solver -- it is not a compile-time mechanism like in Rust.

Kani is a model checker for Rust, and CBMC is a model checker for C. I'm not aware of one (yet!) for Zig, but it would not be difficult to build a port. Both Kani and CBMC compile down to goto-c, which is then converted to formulas in an SMT solver.

DrNosferatu•1h ago
Any good primers on SMT solvers?
dnautics•1h ago
There isn't a real one yet, but to scratch an itch I tried to build one for Zig. It's not complete nor do I have plans to complete it. https://github.com/ityonemo/clr

If zig locks down the AIR (intermediate representation at the function level) it would be ideal for running model checking of various sorts. Just by looking at AIR I found it possible to:

- identify stack pointer leakage

- basic borrow checking

- detect memory leaks

- assign units to variables and track when units are incompatible

pizlonator•1h ago
> it seems impossible to secure c or c++

False. Fil-C secures C and C++. It’s more comprehensively safe than Rust (Fil-C has no escape hatches). And it’s compatible enough with C/C++ that you can think of it as an alternate clang target.

nzeid•1h ago
I love this shameless self-promotion. ;)

Fil-C is in the cards for my next project.

pizlonator•1h ago
Thank you for considering it :-)

Hit me up if you have questions or issues. I’m easy to find

90s_dev•1h ago
One of these days, a project will catch on that's vastly simpler than any memory solution today, yet solves all the same problems, and more robustly too, just like how it took humanity thousands of years to realize how to use levers to build complex machines. The solution is probably sitting right under our noses. I'm not sure it's your project (maybe it is) but I bet this will happen.
pizlonator•1h ago
That’s a really great attitude! And I think you’re right!

I think in addition to possibly being the solution to safety for someone, Fil-C is helping to elucidate what memory safe systems programming could look like and that might lead to someone building something even better

Dwedit•56m ago
If you're filling uninitialized pointers with AAAAAAAA, it might be best to also reserve that memory page and mark it as no-access.
throwawaymaths•54m ago
that only happens in debug-builds.

https://ziglang.org/documentation/master/#undefined

dang•12m ago
Related:

How safe is Zig? - https://news.ycombinator.com/item?id=31850347 - June 2022 (254 comments)

How Safe Is Zig? - https://news.ycombinator.com/item?id=26537693 - March 2021 (274 comments)

How Safe Is Zig? - https://news.ycombinator.com/item?id=26527848 - March 2021 (1 comment)

How Safe Is Zig? - https://news.ycombinator.com/item?id=26521539 - March 2021 (1 comment)