News for hackers. Stuff that matters.
Re:One million lines of code ought to be enough for anybody by delsarto on Wednesday December 18, 2019 @10:49AM (#21826027)
> (no file system would need a path longer than 260 characters, right? :o) )

This is poking fun at Windows' PATH_MAX, but it's very easy to hit BINPRM_BUF_SIZE's 128 character path limit for #! lines; maybe not so much for humans, but with CI systems installing things in weird deep directories (e.g. virtualenvs ... see https://github.com/pypa/virtualenv/issues/596).

So the old adage about glass houses and stones is still good advice ;)

Re:One million lines of code ought to be enough for anybody by throwaway8941 on Wednesday December 18, 2019 @11:31AM (#21826516)
Nix developers ran into this very limit.

https://lwn.net/Articles/779997/

Re:One million lines of code ought to be enough for anybody by aidenn0 on Wednesday December 18, 2019 @12:17PM (#21827024)
Unless they split the line without whitespace, that example is already non-portable because it's not well defined what happens to shebangs with more than one argument. IIRC linux merges all of them into a single argument, but other unixen do different things.
Re:One million lines of code ought to be enough for anybody by saagarjha on Wednesday December 18, 2019 @01:41PM (#21827840)
And people struggle to find examples of Linux bending over backwards for compatibility…
Re:One million lines of code ought to be enough for anybody by mmis1000 on Wednesday December 18, 2019 @09:49PM (#21831654)
I didn't hit that until I am start using node.js...

Then the npm<3 install modules in a dawn nested way and actually cause problem.

Re:One million lines of code ought to be enough for anybody by m463 on Wednesday December 18, 2019 @06:25PM (#21830553)
In unix, there are lots of limits people eventually run into, then either hack to overcome, or go back and painfully rearchitect.

- max size of a command line

- max open files

- kernel stack size

etc...