frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenClaw Creator: Why 80% of Apps Will Disappear

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

What Happens When Technical Debt Vanishes?

https://ieeexplore.ieee.org/document/11316905
1•blenderob•5m ago•0 comments

AI Is Finally Eating Software's Total Market: Here's What's Next

https://vinvashishta.substack.com/p/ai-is-finally-eating-softwares-total
1•gmays•5m ago•0 comments

Computer Science from the Bottom Up

https://www.bottomupcs.com/
1•gurjeet•6m ago•0 comments

Show HN: I built a toy compiler as a young dev

https://vire-lang.web.app
1•xeouz•7m ago•0 comments

You don't need Mac mini to run OpenClaw

https://runclaw.sh
1•rutagandasalim•8m ago•0 comments

Learning to Reason in 13 Parameters

https://arxiv.org/abs/2602.04118
1•nicholascarolan•10m ago•0 comments

Convergent Discovery of Critical Phenomena Mathematics Across Disciplines

https://arxiv.org/abs/2601.22389
1•energyscholar•10m ago•1 comments

Ask HN: Will GPU and RAM prices ever go down?

1•alentred•11m ago•0 comments

From hunger to luxury: The story behind the most expensive rice (2025)

https://www.cnn.com/travel/japan-expensive-rice-kinmemai-premium-intl-hnk-dst
2•mooreds•12m ago•0 comments

Substack makes money from hosting Nazi newsletters

https://www.theguardian.com/media/2026/feb/07/revealed-how-substack-makes-money-from-hosting-nazi...
5•mindracer•13m ago•1 comments

A New Crypto Winter Is Here and Even the Biggest Bulls Aren't Certain Why

https://www.wsj.com/finance/currencies/a-new-crypto-winter-is-here-and-even-the-biggest-bulls-are...
1•thm•13m ago•0 comments

Moltbook was peak AI theater

https://www.technologyreview.com/2026/02/06/1132448/moltbook-was-peak-ai-theater/
1•Brajeshwar•13m ago•0 comments

Why Claude Cowork is a math problem Indian IT can't solve

https://restofworld.org/2026/indian-it-ai-stock-crash-claude-cowork/
1•Brajeshwar•14m ago•0 comments

Show HN: Built an space travel calculator with vanilla JavaScript v2

https://www.cosmicodometer.space/
2•captainnemo729•14m ago•0 comments

Why a 175-Year-Old Glassmaker Is Suddenly an AI Superstar

https://www.wsj.com/tech/corning-fiber-optics-ai-e045ba3b
1•Brajeshwar•14m ago•0 comments

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•16m ago•0 comments

These White-Collar Workers Actually Made the Switch to a Trade

https://www.wsj.com/lifestyle/careers/white-collar-mid-career-trades-caca4b5f
1•impish9208•16m ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•17m ago•0 comments

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

https://new.knife.day/blog/reddit-steel-sentiment-analysis
1•p-s-v•17m ago•0 comments

Federated Credential Management (FedCM)

https://ciamweekly.substack.com/p/federated-credential-management-fedcm
1•mooreds•17m ago•0 comments

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

https://app.writtte.com/read/kZ8Kj6R
1•lasgawe•18m ago•1 comments

The Story of Heroku (2022)

https://leerob.com/heroku
1•tosh•18m ago•0 comments

Obey the Testing Goat

https://www.obeythetestinggoat.com/
1•mkl95•19m ago•0 comments

Claude Opus 4.6 extends LLM pareto frontier

https://michaelshi.me/pareto/
1•mikeshi42•19m ago•0 comments

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•22m ago•0 comments

Google Translate apparently vulnerable to prompt injection

https://www.lesswrong.com/posts/tAh2keDNEEHMXvLvz/prompt-injection-in-google-translate-reveals-ba...
1•julkali•22m ago•0 comments

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

https://bsky.app/profile/fullmoon.id/post/3meadfaulhk2s
1•todsacerdoti•23m ago•0 comments

Software development is undergoing a Renaissance in front of our eyes

https://twitter.com/gdb/status/2019566641491963946
1•tosh•24m ago•0 comments

Can you beat ensloppification? I made a quiz for Wikipedia's Signs of AI Writing

https://tryward.app/aiquiz
1•bennydog224•25m ago•1 comments
Open in hackernews

Plan 9 from User Space

https://github.com/9fans/plan9port
76•welovebunnies•4mo ago

Comments

kotenok2000•4mo ago
Why did they put installation script in INSTALL INSTEAD OF install.sh? Most other repositories i have seen put human-readable instructions in there.
lstodd•4mo ago
It's plan9. It is supposed to be at once weird and somewhat fitting.
throwaway2fd82•4mo ago
I don't think an INSTALL script with that name is common among Plan 9 software.

Also, this project is designed for operating systems other than Plan 9.

opless•4mo ago
* plan9 PORT sigh the clue is in the name
yjftsjthsd-h•4mo ago
Yes, it's a plan9 port; why would you expect it to change any more than is absolutely needed to get it running on the new host OS?
opless•4mo ago
Yes, not plan9.

I despair at your (and GGP) lack of comprehension

yjftsjthsd-h•4mo ago
I don't think it's a lack of comprehension, so much as that we disagree what a "port" means.
opless•4mo ago
I was correcting the user's "plan9" comment.

It's a port of a collection of plan 9 userspace to a non-9 operating system.

Perhaps you've now learnt something

GG

MisterTea•4mo ago
There is likely some history there. Plan 9 is the only OS I know of that bakes in all of the documentation and there is a heavily ingrained culture of 'RTFM!' in the community.

The interesting part is the two references to a person who has long since passed, Uriel. The make file and configure files both print "read the README file." I am sure he complained that most people would blindly unpack the source and immediately run make or configure without ever reading anything. It could be a way to force people to RTFM. But that is just my opinion. If you really want an answer, drop an email to the 9fans mailing list and ask. It's still active.

pjmlp•4mo ago
Pretty common in all UNIXes, which is why projects like GNU and Linux even had a starting point what to compare themselves to.

IBM systems have the famous Red Books, but ok it isn't included.

Windows before the Internet days, when the SDK came in CD, having a MSDN subscription meant receiving a box with all documentation from Microsoft.

Inferno as Plan 9's successor also included all documentation.

Niklaus Wirth OSes for Modula-2 and Oberon, had the OS documentation as hypertext.

All Xerox PARC OSes, across Smalltalk, Interlisp-D and Mesa/Cedar had online help with the system documentation.

packetlost•4mo ago
Plan9port is available in a lot of package managers. I've been using mk and rc for my build/task running and scripting needs for a while and have been very happy. rc in particular is such a concise scripting language that shaves off all the rough edges of sh (not to mention bash), I rarely need to reference docs.
emmelaich•4mo ago
Yep and p9 is used many places e.g. in WSL for access to Windows files.
jacquesm•4mo ago
Plan 9 is amazing. I just released my own ancient little operating system (see 'Show HN') which took some of Plan 9's ideas. Plan 9 was a massive inspiration at the time that it was released, I had it running on a really small machine for the time and I love the underlying concepts. It is a real pity that it never really took off.

Plan 9 is what Unix could have been, the whole idea that 'everything is a file' is so powerful that we ended up not believing it and the resulting hacks are all so ugly in comparison. Plan 9 does this so consistently that you can test a new version of the window manager in a window on the currently running window manager.

For fun I ran the Bell-Core window manager inside a Plan 9 window at some point just to see if it could be done.

https://en.wikipedia.org/wiki/ManaGeR

And yes, you could do it, and fairly easily so. This kind of structural coherency is a great feature for an operating system to have.

Isamu•4mo ago
>the whole idea that 'everything is a file' is so powerful that we ended up not believing it and the resulting hacks are all so ugly in comparison

I agree. People find it hard to wrap their heads around simple and uniform interfaces. They can’t simplify what they want to accomplish, they want to inflict their complexity on everyone.

Simplifying is maybe emotionally deflating, it makes for a less satisfying solution. Career-wise, it is better to propose complex solutions that take lots of manpower. That’s how you climb the ladder.

calvinmorrison•4mo ago
yet - you still have to learn opaque crap. example

echo kill > /proc/123/ctl

Sure, that works if you know kill, but you cannot inspect ctl and understand the interface, its a write interface. so you can certainly RTFM, read the dev proc list, etc. it's not discoverable

so like /proc/net/stat or whatever, it means nothing to me... its gonna just be a TSV of bytes that mean something, unless you know it.

so for all the simplicity, it's what i would call, not very usable.

serbuvlad•4mo ago
Ok, but there's nothing stopping from writing a "discoverable" GUI or TUI or CLI for this interaction.

To the user it doesn't matter.

To the developer, it makes a difference.

/proc/<pid>/ctl is not any more or less simple or discoverable for the end user than TerminateProcess or kill(2). It's all opaque esoteric stuff.

But for the developer /proc/<pid>/ctl is MORE discoverable than TerminateProcess or kill(2), since it's a file you can list, so you know it exists. Yeah, you still have to read the man page (you always have to read the docs as a developer), but you know there's a ctl file that probably controls some stuff about the process there. And you already know how to interact with it (the same IO interface as everything else).

calvinmorrison•4mo ago
Of course. But it's not implemented. The OS is the spec.
magicalhippo•4mo ago
I guess in theory there is nothing stopping the system from providing yet other files, like say "/proc/123/ctl/description" which provides a human-readable description of what "/proc/123/ctl" does, and "/proc/123/ctl/schema" which provides a standardized schema for interacting with the parent, akin to a XSD or JSON Schema.
calvinmorrison•4mo ago
No there's not. Other than plan9 does not have it and it was not considered important.
Ferret7446•4mo ago
"everything is a file" is unix's equivalent of the Greek's "everything is a basic geometric shape" and epicycles, or heck, "everything is an object". These kinds of reductions are naive and result in kludges of representation.
poncho_romero•4mo ago
By that logic isn’t this argument equally reductive?
jacquesm•4mo ago
> These kinds of reductions are naive and result in kludges of representation.

I've spent a lot of time with these 'kludges' as well as all of the alternatives available and I far prefer the kludges. They make working with resources remote or local a breeze, they allow the same software to work with a COM port or a SCSI channel, they allow for all kinds of abstractions and get rid of an enormous amount of cruft in code to special case each and every device under the sun.

The 'Unix' version of that statement is the one that is kludgy, I'll give you that. But I was looking well beyond Unix, see TFA.

tiu•4mo ago
Why Plan 9 seems to be 'much' more popular/discussed and not Inferno?

[0]: https://en.wikipedia.org/wiki/Inferno_(operating_system)

yjftsjthsd-h•4mo ago
> Applications are written in the Limbo programming language, which provides static typing, garbage collection, and built-in concurrency features. Limbo code is compiled into architecture-independent bytecode executed by the Dis virtual machine. The Dis VM can interpret the bytecode or compile it just-in-time into native instructions, allowing applications to run consistently across different platforms.

Can you port existing software to it, or do you have to rewrite everything in Limbo? Because if you do, that right there almost completely kills it IMO.

pjmlp•4mo ago
You could port as much as what was already on Plan 9, so same restrictions apply as UNIX to Plan 9.

The C compiler is there, the same way as in Plan 9, Inferno is the evolution of Plan 9, in one way it was Bell Labs response to Java, in other way it was another take to what went wrong in Plan 9 like the failure to design Alef to be usable.

Naturally Limbo was prefered as the main userspace language, from safety and usability point of view.

yjftsjthsd-h•4mo ago
Ah, okay, I thought limbo was the only userspace language, which would massively hinder adoption. If that's not the case then I know of no particular technical reason inferno wouldn't be a good option. I do wonder if other people had the same misunderstanding as I did.
pjmlp•4mo ago
Here is one of the places where you can see the reference to C compiler being available.

https://inferno-os.org/solutions/embedded

rcarmo•4mo ago
As someone who tried to use both, there is little you can do with it in practice when compared to Plan9. There was a _great_ baremetal port of Inferno to the Raspberry Pi, but there aren't any modern versions for other SBCs.
pjmlp•4mo ago
Yes, it is a tragedy that so many leave the UNIX evolution[0] train at the middle station, instead of the end.

[0] - as per what its creators worked on following it