frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Toyota, Nissan, and Honda to standardize parts to lower costs

https://www.caranddriver.com/news/a74490092/toyota-nissan-honda-standardize-parts-lower-costs/
467•zdw•5h ago•277 comments

87% of the Anthropic power will come from gas and 11% from coal in 2028

https://betterdatacenterproject.com/2026/11/16/how-ai-is-powered-a-breakdown-of-byop-and-grid-power/
58•happosai•1h ago•33 comments

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
990•rafaelc•1d ago•216 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
1029•g-b-r•19h ago•848 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
44•tamnd•4h ago•16 comments

Sandwich Simulator

https://stulle.app/
231•subdomain•9h ago•78 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
459•k__•15h ago•116 comments

Data Processing Incidents on Inference Providers

https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers/
144•sdko•7h ago•57 comments

Notes on the discrete Fourier transform (DFT)

https://eli.thegreenplace.net/2026/notes-on-the-discrete-fourier-transform-dft/
27•kouosi•3h ago•4 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
606•beginning_end•20h ago•387 comments

If tiny 'primordial' black holes exist

https://phys.org/news/2026-11-tiny-primordial-black-holes.html
31•wglb•2d ago•1 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
268•jger15•1d ago•89 comments

Is 'fork' missing operation in sandboxes?

https://avrea.com/blog/avrea-sandboxes-computers-should-be-forkable
5•damezumari•2d ago•4 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
582•soheilpro•23h ago•270 comments

Reversing the Next-Page Prefetcher in Skylake-X

https://devsh0.github.io/microarchitecture,/intel,/computer-architecture/2026/11/17/reversing-the...
8•todsacerdoti•3d ago•0 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
112•sebaandrada•11h ago•13 comments

The Mythology of Conscious AI

https://www.noemamag.com/the-mythology-of-conscious-ai/
61•Anon84•7h ago•119 comments

Fast-Anything: Don't rewrite it in Rust. Rewrite the 5% that's slow

https://github.com/EL4CTEO/fast-anything
27•BaselAshraf81•5h ago•12 comments

Split Radiance Cascades

https://www.jacktollenaar.top/articles/split-rc.html
32•ibobev•2d ago•0 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
92•vasie•13h ago•21 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
161•raphlinus•12h ago•62 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
117•f311a•15h ago•57 comments

Show HN: Compile the same source for GPUs and CPUs

https://github.com/ThrudTheBarbarian/xc
10•spacedcowboy•1w ago•0 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
241•fortran77•3d ago•156 comments

Pion Interceptor: WebRTC for Hackers

https://pion.ly/blog/pion-interceptor-webrtc-for-hackers/
10•Sean-Der•3d ago•1 comments

Reaktiv Workbook – A spreadsheet where every cell is Python

https://workbook.bui.app/
18•buibuibui•3d ago•3 comments

GnuPG Security Advisory for GPGME

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
251•gdgghhhhh•1d ago•101 comments

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2415•jasondavies•1d ago•1174 comments

Shaping the Loops, Closing the Loops

https://revyl.com/blog/pattern-engineering/
25•based0x10•3d ago•9 comments

PostgreSQL Extensions in Go

https://jespino.github.io/gopgext/
147•valyala•16h ago•25 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!