frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Free Programing Books

https://github.com/EbookFoundation/free-programming-books
72•fmfamaral•2h ago•10 comments

Tinnitus Neuromodulator

https://mynoise.net/NoiseMachines/neuromodulationTonesGenerator.php
84•gjvc•2h ago•53 comments

Attention Is a Luxury Good

https://seths.blog/2025/10/attention-is-a-luxury-good/
54•herbertl•2h ago•32 comments

1,180 root system drawings

https://images.wur.nl/digital/collection/coll13/search
117•bookofjoe•4h ago•20 comments

The IDEs we had 30 years ago ... and we lost (2023)

https://blogsystem5.substack.com/p/the-ides-we-had-30-years-ago-and
381•AlexeyBrin•5h ago•303 comments

Event Sourcing, CQRS and Micro Services: Real FinTech Example

https://lukasniessen.medium.com/this-is-a-detailed-breakdown-of-a-fintech-project-from-my-consult...
39•fmfamaral•2h ago•31 comments

Who invented deep residual learning?

https://people.idsia.ch/~juergen/who-invented-residual-neural-networks.html
24•timlod•5d ago•3 comments

./watch

https://dotslashwatch.com/
236•shrx•8h ago•61 comments

Liva AI (YC S25) Is Hiring

https://www.ycombinator.com/companies/liva-ai/jobs/inrUYH9-founding-engineer
1•ashlleymo•1h ago

Flowistry: An IDE plugin for Rust that focuses on relevant code

https://github.com/willcrichton/flowistry
43•Bogdanp•3h ago•7 comments

SQL Anti-Patterns You Should Avoid

https://datamethods.substack.com/p/sql-anti-patterns-you-should-avoid
145•zekrom•5h ago•97 comments

What Dynamic Typing Is For

https://unplannedobsolescence.com/blog/what-dynamic-typing-is-for/
12•hit8run•4d ago•4 comments

Andrej Karpathy – It will take a decade to work through the issues with agents

https://www.dwarkesh.com/p/andrej-karpathy
1023•ctoth•1d ago•909 comments

Ripgrep 15.0.0

https://github.com/BurntSushi/ripgrep/releases/tag/15.0.0
188•robin_reala•4h ago•42 comments

Lux: A luxurious package manager for Lua

https://github.com/lumen-oss/lux
36•Lyngbakr•5h ago•5 comments

Picturing Mathematics

https://mathenchant.wordpress.com/2025/10/18/picturing-mathematics/
9•jamespropp•2h ago•0 comments

New Work by Gary Larson

https://www.thefarside.com/new-stuff
422•jkestner•20h ago•109 comments

Fast calculation of the distance to cubic Bezier curves on the GPU

https://blog.pkh.me/p/46-fast-calculation-of-the-distance-to-cubic-bezier-curves-on-the-gpu.html
92•ux•8h ago•19 comments

Ruby Blocks

https://tech.stonecharioteer.com/posts/2025/ruby-blocks/
137•stonecharioteer•4d ago•80 comments

Our Paint – a featureless but programmable painting program

https://www.WellObserve.com/OurPaint/index_en.html
23•ksymph•5d ago•3 comments

AMD's Chiplet APU: An Overview of Strix Halo

https://chipsandcheese.com/p/amds-chiplet-apu-an-overview-of-strix
134•zdw•13h ago•47 comments

Rapid amyloid-β clearance and cognitive recovery by modulating BBB transport

https://www.nature.com/articles/s41392-025-02426-1
44•bookofjoe•3h ago•9 comments

Atuin desktop: Runbooks that run

https://github.com/atuinsh/desktop
3•PaulHoule•1h ago•0 comments

Life, Work, Death and the Peasant, Part V: Life in Cycles

https://acoup.blog/2025/10/17/collections-life-work-death-and-the-peasant-part-v-life-in-cycles/
42•bell-cot•9h ago•5 comments

The pivot

https://www.antipope.org/charlie/blog-static/2025/10/the-pivot-1.html
405•AndrewDucker•22h ago•191 comments

Cruz Godar Generative Art Gallery

https://cruzgodar.com/gallery/
35•bookofjoe•6d ago•2 comments

Meta convinces Blue Owl to cut $30B check for its Hyperion AI super cluster

https://www.theregister.com/2025/10/17/meta_blue_owl_hyperion/
27•rntn•2h ago•35 comments

StageConnect: Behringer protocol is open source

https://github.com/OpenMixerProject/StageConnect
167•jdboyd•12h ago•91 comments

Live Stream from the Namib Desert

https://bookofjoe2.blogspot.com/2025/10/live-stream-from-namib-desert.html
538•surprisetalk•1d ago•98 comments

The Unix Executable as a Smalltalk Method [pdf]

https://programmingmadecomplicated.wordpress.com/wp-content/uploads/2025/10/onward25-jakubovic.pdf
123•pcfwik•17h ago•14 comments
Open in hackernews

The early Unix history of chown() being restricted to root

https://utcc.utoronto.ca/~cks/space/blog/unix/ChownRestrictionEarlyHistory
68•kencausey•5d ago

Comments

ape4•5h ago
It was one of those restrictions that seemed unjustified to me but I figured someone smarter than I had seen a reason.
gear54rus•3h ago
Yeah.. I'm sitting here wondering how many years would it take to remove equally stupid error that says 'private key permissions too open' from ssh-add and friends.

Would save me a wrapper script on my flashdrive that does hacks like loading it from stdin or moving it to temp file.

TZubiri•2h ago
It's just a nice security measure.
TZubiri•2h ago
Imagine if you wanted to enter a bank safe, but your key doesn't fit the lock. If you were able to change the lock, you would bypass the lock mechanism, rendering it useless
JadeNB•26m ago
But imagine if you were the bank-safe owner. Shouldn't you be able to change the lock?
rcxdude•1h ago
It would need at least a little bit of thought with suid binaries.
charcircuit•24m ago
Suid binaries were a bad idea and should be removed anyways.
pessimizer•5h ago
> Forbidden

> You don't have permission to access /~cks/space/blog/unix/ChownRestrictionEarlyHistory on this server.

I laughed out loud.

https://web.archive.org/web/20251018101005/https://utcc.utor...

drfuchs•3h ago
Not being able to chown() caused us grief developing Frame Maker back in the 80s. The responsible way to handle "save" was to write the document into a new file mydoc.new, then rename mydoc.cur to mydoc.backup and then rename mydoc.new to mydoc.cur, so that failure never left you in the lurch. The only problem was that there was no way to create mydoc.new to have the same owner as mydoc.cur and customers complained that we'd keep changing the owner of their files. If only the semantics of the unix filesystem supported file generation numbers, like on Tops20 or VaxVMS, where the default for writing to a file isn't "yeah, sure, write over top of the old data, and let's hope nothing fails along the way" this would not have been a problem.
SoftTalker•1h ago
I would guess that many early systems just didn't have the storage space for a lot of multiple versions of files. Was VMS saving diffs or full copies of files?

Once storage space was plentiful, the pattern of "overwrite the existing file" was already well established.

webdevver•1h ago
ive always felt that file systems are by far the weakest point in the entire computing industry as we know it.

something like zfs should have been bog standard, yet its touted as an 'enterprise-grade' filesystem. why is common sense restricted to 'elite' status?

ofcourse i want transparent compression, dedup, copy on write, free snapshots, logical partitions, dynamic resizing, per-user/partition capabilities & qos. i want it now, here, by default, on everything! (just to clarify, ive ever used zfs.)

its so strange when in the compute space you have docker & cgroups, software defined networking, and on the harddrve space i'm dragging boxes in gparted like its the victorian era.

why can't we just... have cool storage stuff? out the box?

pessimizer•50m ago
Because it was extremely difficult to create something like zfs? And it was proprietary and patent-encumbered, and the permissively licensed versions were buggy until about 5 minutes ago?

That's like saying the Romans should have just used computers.

SoftTalker•11m ago
Because the vast majority of personal computer users have no need for the complexity of zfs. That doesn't come for free, and if something goes wrong the average user is going to have no hope of solving it.

FAT, ext4, FFS, are all pretty simple and bulletproof and do everything the typical user needs.

Servers in enterprise settings have higher demands but they can afford an administrator who knows how to manage them and handle problems. In theory.

TZubiri•2h ago
Wait. You can use chown as non root?
kazinator•2h ago
If you could chown files to an arbitrary other user, you could use that to evade disk quotas.

The protocol for changing ownership should be two step.

1. The file is put into an "offered" state, e.g. "offered to bob". Only the owner or superuser can make this state change.

2. Bob can take an "offered to bob" file and change ownership to bob.

Files can always be in an offered state; i.e. have an offered user which is normaly equal to their owner. So when ownership is taken, the two match again.

heythere22•1h ago
What's the deal with disk quotas? Saw that in the OT as well. Why would you measure folder size seperately for each and every user? Would it not be a lot easier to just use the disk space of a folder regardless of whomever the file belongs to?
kazinator•1h ago
It's not folder size that you measure, but a user's usage: how many blocks are occupied by files belonging to a certain user, no matter where they are.

That's what quotas are: per-user storage limits.

If Bob has a large file which is sitting in Alice's home directory, that counts toward's Bob's quota, not Alice's. If Bob could sneakily change the ownership to Alice, while leaving the permissions open so he could access the file, then the file counts toward Alice's quota.