frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Gemini 4 Neon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
608•yigitdemirag•7h ago•540 comments

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
1237•speedping•13h ago•540 comments

Gemini 4 Neon looks like an Opus 5.5 competitor

https://micjm.com/blog/gemini-4-neon-looks-like-a-top-model/
163•seizethecheese•4h ago•58 comments

Multiple vulnerabilities in Regexp and String case conversion

https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/
149•runesoerensen•5h ago•45 comments

Unreal Tournament 2004 in the Browser

https://ut2004.dev/
76•TheAceOfHearts•3h ago•33 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
483•gmays•12h ago•330 comments

AI agents ask better questions than KPMG accountants in audit trial

https://europeanbusinessmagazine.com/ai-agents-better-questions-kpmg/
416•Betelbuddy•13h ago•179 comments

DNS resolvers are the wrong place to fight piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
636•ritzaco•15h ago•241 comments

Inside Deutsche Bank

https://www.inside-db.com/
598•gyre007•13h ago•202 comments

LLM assisted reverse engineering

https://www.slowchronicle.com/posts/llm-assisted-reverse-engineering
115•ioma8•6h ago•33 comments

DaisyRose-27B

https://www.radixark.com/blog/daisyrose-27b
164•de_sty•9h ago•49 comments

Dumping an AES key from a MyQ garage opener to stop rebooting when offline

https://kusha.me/blog/stop_myq_homebridge_819lmb_rebooting/
72•kusha•2d ago•28 comments

Mosquitoes are Ladakh's latest tourists

https://ruralindiaonline.org/article/mosquitoes-are-ladakh-s-latest-tourists
14•akbarnama•22h ago•0 comments

Camera Index

https://www.cameraindex.co.uk/
5•bookofjoe•1d ago•0 comments

Genie 4 is now available

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/genie-4-now-available-p...
213•leumon•10h ago•148 comments

The Cambridge Dictionary has named ‘human’ as the Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
251•DeepLogin•14h ago•175 comments

Advancing chip design with OpenAI models

https://openai.com/index/advancing-chip-design-with-our-models/
177•vighneshiyer•11h ago•114 comments

We need smart people who give a shit

https://violetpixel.com/blog/2026-11-17-we-need-smart-people-who-give-a-shit/
350•ExMachina73•5h ago•183 comments

Show HN: ExitPath – Open-source ways out of Slack, Notion and Microsoft 365

https://exitpath-ruddy.vercel.app/
185•zerocool0101•13h ago•54 comments

FailTrace – Reproduce a failed GitHub Actions run locally from its URL

https://github.com/Ri4dH/failtrace
17•ri4dh•3h ago•2 comments

Show HN: Take Voyager 1 apart, down to a single memory chip

https://rshekhar.com/voyager/
175•raj-shekhar•12h ago•45 comments

Previous-Token Prediction Based LLM Inversion for Prompt Reconstruction

https://arxiv.org/abs/2607.29378
27•dalmo3•3h ago•5 comments

Palo Alto Networks to Acquire Applied Compute for $4.5B

https://investors.paloaltonetworks.com/news-releases/news-release-details/palo-alto-networks-acqu...
33•alpb•5h ago•6 comments

Cuttlefish on Mac: Android's Virtual Device Framework on Apple Silicon

https://engineering.fb.com/2026/11/13/android/cuttlefish-on-mac/
57•acossta•3d ago•12 comments

Show HN: Open-source, real-time object tracking for live video feeds

https://github.com/aryamandarda/tamserve
64•aryaman_darda•2d ago•2 comments

A Collage Showing 49 Drill Holes Made by NASA's Curiosity Mars Rover

https://science.nasa.gov/photojournal/a-collage-showing-49-drill-holes-made-by-nasas-curiosity-ma...
42•wawayanda•2d ago•5 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
156•ibobev•14h ago•47 comments

Launch HN: Maritime (YC F26) – A managed cloud for production AI agents

45•ashriv•11h ago•41 comments

KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312)

https://www.cve.org/CVERecord?id=CVE-2026-99312
179•Kozmik1•12h ago•116 comments

AI will not make you rich (2025)

https://colossus.com/article/ai-will-not-make-you-rich/
81•madars•3h ago•46 comments
Open in hackernews

Path is a utility for working with paths

https://gitlab.com/SpyrjaGaldr/path
60•spyrja•1y ago
A recent post here got me thinking about my own personal gripes with OS path handling offerings. So I've basically spent the passed couple of days working on a little project in an attempt to rectify the situation somewhat (in the spirit of cross-platform development). It should also work pretty well with existing tools. Let me know what you think, and feel free to open an issue or a pull-request if you have any problems getting it running it on your system. Enjoy!

Github link: https://github.com/SpyrjaGaldr/path

https://simonsafar.com/2025/path_as_system_call/

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

Comments

vesinisa•1y ago
What can this do that standard Unix find can not do?
autobodie•1y ago
cross platform support, according to the description.
indemnity•1y ago
fd exists https://github.com/sharkdp/fd
spyrja•1y ago
Looks like it has a pretty good interface as well. It does however seem a just a bit too top-heavy (lot's of dependencies) not to mention a few more bugs than I particularly care for. But sheesh, 37K stars, it must be good for something!
blooalien•1y ago
> ... "it must be good for something!"

It's good for finding files fast, and piping the resulting file paths into other tools for further action / handling. It does what it claims to do and does it well. :)

spyrja•1y ago
I would say the default behaviour just isn't very ergonomic. Suppressing warnings for example requires piping to /dev/null (whereas `path` supresses permission warnings by default), if you want to limit the number of results you have to pipe the output to another command, getting xargs-like behaviour (obviously), or putting quotes around lines with embedded spaces, there are simply more hoops to jump through. It's much easier to type "path -sf .jpg .jpeg .png" than whatever would be required to get the `find` utility to do the same. (Or, say, finding all node_modules folders with "path -z n_m", it's just so much more satisfying.) But yes, these are mostly just syntactic-sugar kinds of issues. Aside from that (and perhaps the lack of cross-platform compatibility), I would say there is nothing inherently deficient about the `find` command. It's a work-horse which probably has more features than `path` does. But the latter really is growing on me. It is actually quite fun to use, if I may say so myself!
jimbokun•1y ago
“A more ergonomic find command” is a nice elevator pitch.
pimlottc•1y ago
From the name and description, I expected this to perform operations on file path strings, like convert relative to absolute (and vice versa), expand symlinks, convert unix paths to dos, etc. This is more like a find command.
spyrja•1y ago
I don't see why it necessarily couldn't, my only question would be if there are really many actual use cases for such things? As far as symlinks go, I suppose being able to expand them (but not following them!) might be somewhat useful. But converting to DOS paths and vice-versa? That just doesn't seem very useful. Nevermind converting to-and-fro relative and absolute paths, I can't even imagine what the point of that would be. But perhaps I'm just not seeing the forest for the trees, as they say.
qrobit•1y ago
As a rule of thumb I always make paths absolute when handling files in scripts. But then sometimes I need to copy a directory tree relative to $CWD somewhere else, so I convert them back to relative

Fish, being a great shell, provides this via `path` command[0]

[0]: https://fishshell.com/docs/current/cmds/path.html

jl6•1y ago
> for the primary purpose of helping other programs know where to find stuff

Potential footgun to make a program rely on this to locate, say, a shared library (as in one of the examples), if there’s a possibility that someone has smuggled a malware’d version of it into, say, /tmp, since it defaults to searching the root directory.

spyrja•1y ago
Kind of, but also kind of not. I mean if someone can smuggle a file into some random directory, chances are they have enough access to write directly to the "correct" folder to begin with. Personally I wouldn't execute or otherwise load any sort of executable content from a non-root directory (although certainly there are many people who wouldn't even think twice before doing such a thing). So it really just boils down to having a sane security-policy. Restrict searches with something like "path -d /usr *" and you are guaranteed not to scoop-up something that was world-writable in the first place. In fact in the example given in the README, that is precisely how that would have worked. Both /lib32 and /lib64 are owned by "root" and hence not a concern.
jl6•1y ago
Naturally every footgun is guaranteed to be safe as long as you use it right :)

I wonder if a safer default would be to start searches at the current directory rather than the root directory?

spyrja•1y ago
I did actually consider that at one point, but eventually decided against it because I felt would have meant a sacrifice in performance; first you'd do the local search, then start at the very top and recurse back down, checking every single entry against the local path to be sure that you don't do the local traversal all over again. Fortunately the code base is very clean and straight-forward, so it would be a fairly trivial excercise to just fork the repo and make those changes yourself to get that kind of behaviour.
account-5•1y ago
I've been finding nushell's `ls` with a where clause is pretty good for this. There's also the `find` command too.
spyrja•1y ago
Well I ran a bunch of tests and it turns out that the performance wasn't actually impacted very much after all. So the changes are official. I also made some other adjustments to the default behaviour; if no pattern is specified then it just matches everything. In other words, "path -f" prints every regular file in the filesystem (starting in the current one). Anyway, thanks for the suggestion, otherwise I may not gone down that (decidedly satisfying) rabbit-hole!