frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GTA III on a 1993 Atari Jaguar – On the real hardware [video]

https://www.youtube.com/watch?v=nBkHACh5BHc
1•gmmachine•3m ago•0 comments

How to read the genome and build a human being (2016) [video]

https://www.youtube.com/watch?v=s6rJLXq1Re0
1•simonebrunozzi•3m ago•0 comments

Content, Art, & Porn

https://www.sherryning.com/p/content-art-and-porn
1•jger15•3m ago•0 comments

Super Mario 64 on the Atari Jaguar – NO the real Atari Jaguar not an emulator [video]

https://www.youtube.com/watch?v=pBJxz8FlSfE
1•gmmachine•4m ago•0 comments

Show HN: SwordCheck – A read-only security check-up for your Mac

https://github.com/SwordSec/SwordCheck
1•s3yfullah•6m ago•0 comments

Ask HN: Do you feel developers are more "grumpy" these days?

2•ksajadi•7m ago•0 comments

View a randomized old tweet from anyone on the timeline

https://twitter.com/onlyfootnotes/status/2123828162417336336
1•onlyfootnotes•9m ago•1 comments

Scientists Track 219,000 People–Discover Unexpected Shift in Dementia Risk

https://www.newsweek.com/scientists-track-219000-people-discover-unexpected-shift-in-dementia-ris...
4•gmays•11m ago•0 comments

Show HN: XSquads– Set a mission, agents work on it autonomously in your harness

https://xsquads.ai
3•vincirufus•11m ago•1 comments

A Transformer Compressed 1GB of Wikipedia to 105MB

https://tufalabs.ai/research/tufazip/
1•mrkn1•14m ago•0 comments

Leaky AI supply chain is exposing secret user data at an alarming rate

https://arstechnica.com/security/2026/11/a-leaky-ai-supply-chain-is-exposing-secret-user-data-at-...
2•BoiledCabbage•14m ago•0 comments

Kalshi Asks NY Judge for Say Before Any Renewed Restraining Order

https://rg.org/news/prediction-markets/kalshi-letter-justice-crane-new-york-attorney-general-tro-...
1•ra0x3•14m ago•0 comments

Google Search upgrade: Gemini 4 Hydrogen features

https://blog.google/products-and-platforms/products/search/gemini-4-hydrogen-search-upgrade/
1•kristianp•15m ago•0 comments

Why Anthropic's blockbuster debut didn't ease Wall Street's AI fears

https://www.cnn.com/2026/11/20/investing/anthropic-ai-stock-nasdaq
2•baal80spam•17m ago•0 comments

If tiny 'primordial' black holes exist

https://phys.org/news/2026-11-tiny-primordial-black-holes.html
1•rbanffy•17m ago•0 comments

Supreme Court sentences 29-year-old activist to prison over FB post

https://prachataienglish.com/node/12123
2•DeepLogin•17m ago•0 comments

Prompt Canaries Detect Prompt Leaks at AI Providers

https://www.dragos.com/blog/ai-supply-chain-security-canary-tokens
1•paulis•18m ago•0 comments

Photos were transmitted by wire in the 1930s (2024)

https://kottke.org/24/03/how-photos-were-transmitted-by-wire-in-the-1930s
1•sammatilda•21m ago•0 comments

The Nvidia Board Removed Jensen on False Pretenses

https://www.effort.news/nvidia
4•adamrezich•22m ago•0 comments

Ask HN: What's stopping us from putting agents in general purpose robots?

2•ex-aws-dude•23m ago•0 comments

A few hours ago Google DeepMind created a math horizon repo

https://github.com/google-deepmind/math-horizon
3•RubenLtke•25m ago•2 comments

Elon Musk announces another Tesla vehicle no one asked for

https://electrek.co/2026/11/19/musk-tesla-model-y-no-steering-wheel-7-seat/
4•cisc•28m ago•1 comments

Show HN: Trichroma, a Platformer of Light

https://trichroma.namirsab.dev/
2•namirsab•30m ago•0 comments

Show HN: Tally – Company numbers with their history and source

https://tallycatalog.com/
2•verkyyi26•33m ago•0 comments

Kia's cheapest EV is coming next year, and it could cost under $25,000

https://electrek.co/2026/11/19/kias-cheapest-ev-coming-2027-under-25k/
5•cisc•34m ago•0 comments

Anton Syndrome

https://en.wikipedia.org/wiki/Anton_syndrome
2•ironworks•34m ago•0 comments

One Developer, Two Decades, and 30M Users Later – Philip Guo [video]

https://www.youtube.com/watch?v=GPk0nNuc8S0
1•matt_d•36m ago•0 comments

GnuPG Security Advisory for Gpgme (T8557,CVE-2026-129975)

https://lists.gnu.org/archive/html/info-gnu/2026-11/msg00006.html
3•nh2•36m ago•1 comments

Windows 11 passkey bug cries failure after successful sign-in

https://www.theregister.com/security/2026/11/20/windows-11-passkey-bug-cries-failure-after-succes...
3•Bender•39m ago•0 comments

Show HN: Build a trading bot in 10 seconds

https://board.blink.cash/
1•akeyes6•40m ago•1 comments
Open in hackernews

Avoid Continue

https://www.teamten.com/lawrence/programming/avoid-continue.html
2•todsacerdoti•1y ago

Comments

zoezoezoezoe•1y ago
I dont know if I fully agree. Sure, there is definitely an argument the be had about whether or not `continue` is the best word to use in this instance, but why avoid it entirely? Every programmer is able to easily understand what code like this would do:

``` for (Node node : nodeList) { if (node.isBad()) { continue; } processNode(node); } ```

Every keyword in any programming language is largely arbitrary in my opinion let's take a look at the beginning of the codeblock `for (Node node : nodeList)` also completely arbitrary, though it's clear to anyone who's ever written C++ that it is equivalent to saying "for every node in nodeList".

Continue is not meant to read as "continue execution" it's meant to be "continue to the next item of the list", and I think avoiding it entirely is a pointless effort.

Ukv•1y ago
I feel `skip` may have been a better name, but disagree with it being logically difficult to parse beyond that.

If I'm reading a loop and see

    for x in y {
        if exclusions.contains(x) { skip; }
        if x.children.length == 0 { skip; }
        if os.file.exists(x.name) { skip; }
        ...
I instantly know that processing for those elements is skipped, and they won't be relevant for the rest of the loop.

Whereas if I see

    for x in y {
        if !exclusions.contains(x) {
            if x.children.length != 0 {
                if !os.file.exists(x.name) {
        ...
I feel like there's still mental overload with not knowing where those `if` blocks end, and so having to keep the conditions in mind. It doesn't immediately tell me that the rest of the loop is being skipped.

The `log()` mistake seems no less likely to happen using early-returns in function instead, and I'd argue nesting checks actually introduces more room for that kind of error overall, where you append something at the end within the wrong set of brackets, compared to a flatter structure.