
I think I've learned more here than I did at MIT. ∨ ∧_∧ ( ´_ゝ`)  ̄\ / / ̄ ̄ ̄ ̄ ̄/  ̄ ̄| / ./ UNIX ./  ̄| |(__ニつ/_____/_ 田| | \___))\ ノ||| | ⌒ ̄Discussion of UNIX and technology.
>>13
Oh, now that you've mentioned it, I remember leftybbs. I almost thought I was the only person on earth who still knew about this.
https://github.com/alyssa-p-hacker/SchemeBBS
I have no idea about the specifics but I liked to post on this boar, rip
While looking this up I learned that someone was rewriting it in common lisp. It's the same guy apparently. First time I hear of it
https://github.com/ryukinix/cl-bbs
I find it weird how "AI"-zealots compare AI versus compiler as analogous to compiler versus assembler without realizing that knowing assembly language is an important skill to have when you're developing software. They just say this as an end-it-all for any discussion, because who in their right mind mind would know a thing or two about assembly? The nice thing about C as opposed to C++ and a lot of the others is that you can roughly imagine what the compiler will spit out when you see the code and if that isn't possible, you can read the generated assembly by the compiler and check for yourself. It gives you control and as a programmer naturally you're ought to be a control freak. Now I don't want to make this thread be a fighting ground for programming languages, so I'll leave it at that. My point is that the same way you should know what the AI does and what it all means, you should understand what the compiler does and what it all means.
Well said
It makes sense in the mind of the oft-maligned lowest-common-denominator of high-level developer, who only writes js, python or other scripting languages and gets by through copying code snippets or dwim vibes without much deeper understanding of the process to speak of. Sadly experience has shown low-quality code to proliferate in certain niches and "AI" will be no exception to this.
>>24
Tar zxf is convenient compared to cpio, the true UNIX archiver. While cpio -i extracts the files from an archive like you would expect, cpio -o is very different from most other archive programs, expecting to read a list of files from standard input. Replicating the behavior of '7z a archive directory' requires something like 'find directory | cpio -o (| gzip > archive)'.
Too bad cpio hasn't been standardized since System V Release 4 or i would send it more often to people.
>>27
I don't use it, because it's rarely part of the base system and i always type tar out of habit. Iterating on the ar/tar syntax and badgering everyone to link tar to their new and slightly incompatible ar!pax program would have been the smarter choice honestly, which is sort of what libarchive did with "bsdtar". The pax format seems fine, but i have no idea what the benefit over ustar is.
>>28
As it should, since you ought to encrypt on the file level at least.
>>42
Do you know where it was hosted? G*rmany seems to be on a spree
I wonder if some AI supercomputers could be used to crack open proprietary software/firmware/chipsets so better solutions could be made.
Nano rocks. When I'm writing a program in C++ I have two terminal windows open on the left/right side of my screen. On one I have nano open and the other I use to run cmake/make. Honestly the best dev setup I've come up with since I started programming
I am the bone of my SICP.
Scheme is my body, and Lisp is my blood.
I have typed over 1024 parentheses.
Unknown to Java.
Nor known to C#.
Have withstood emacs to write many programs.
Yet these skills will never lead to a career.
So as I pray, Unlimited Satori Works!
>>31
You type like 10 parenthesis per line when programming Lisp, so you've written like 102 lines of code? I get the joke, but still it doesn't add up.
i use nix btw