Install X/Y

Why do you think this is so funny?

Do you think it's funny cause it's a play on an (as apparent to you) nonsensical phrase GNU/Linux?

Do you think it's funny because BSD and Gentoo aren't very popular, and require a lot of effort to maintain, so you think programmers use it cause programmers like things like this?

I am an expert programmer, and a Lisp wizard. I do not particularly care about UNIX politics, and view all current operating systems as retarded. However, I do like the GNU approach to UNIX (although not necessarily the reality) the most out of all the other approaches from a technical stand point.

Maybe you think installing these operating systems is a difficult act that only strange programmers would participate in.

I do not understand why you think ``install BSD/Gentoo'' is so amusing. Why do you place it everywhere?

>>1
PROTIP: I'm the "rename GNU/Linux as BSD/Linux guy".
I'm also not the install BSD/Gentoo guy.
That's just some guy who enjoys spam.

>>1
However, I do like the GNU approach to UNIX (although not necessarily the reality) the most out of all the other approaches from a technical stand point.
I hate to break it to you, but you're a retard, OP.
The GNU approach to UNIX is ``attempt to do everything all at once, then fail on all fronts''.
The traditional UNIX philosophy is ``do one thing really well, then combine with other tools''.
GNU is to the UNIX philosophy as Microsoft is the the UNIX philosophy.

I suspect their creation of monolithic garbage heaps rather than nice modular utilities is to prevent anybody from actually using their applications in other programming projects. That is, using them without modifying the source.
If the only way you can reuse feature <whatever> from emacs in your own project is to actually modify the source, then they prevent you from dodging their shitty viral license by calling a binary.

That's some proprietary tier assholery right up there.
Seriously, it's the kind of thing Apple would do.

>>10
I'm a Lisp programmer, I think the UNIX philosophy is garbage.

Some GNU programmers are or were Lisp programmers. GNU's approach to UNIX could be called a Lipsish approach to UNIX. That being said UNIX is the antithesis to Lisp.

Please see my other posts on this board and the other board for reasons why the UNIX philosophy is retarded, I do not care to repeat them.

>>12
Yeah, sorry, but Lispers don't really have any credibility.
They have the most immature approach to programming of any language fanboys.
The approach of "I'm writing code for myself. My code is for me, it will never be shared. Even if it is shared it will never need to be read of modified by others because I'm perfect and my code is perfect.".

There's a good reason Lispers don't actually get employed as programmers, and it's not the HURRR DURRR CONSPIRACY TO KEEP THE PERFECT MASTER RACE DOWN that Lispers often complain about.

>>12
Please see my other posts on this board and the other board for reasons why the UNIX philosophy is retarded, I do not care to repeat them.
Yeah ok, I'll check all messages signed Anonymous on this board and the other board, I do care to read them.

>>13
None of what you said is true.

>>14
They're not that hard to find e.g. look at (one of) the secret society threads on the front page of lounge on the other board.

>>19
Just repeating things doesn't make them true.

>>21
Same goes for you.
If you want to prove me wrong then explain Lisp's lack of quality libraries and opensource projects.

>>22
Lisp has plenty of quality libraries though.

**** Development
+ ASDF
  + Build system.
+ Quicklisp
  + Library package manager.
+ SLIME + Swank + Paredit + Redshank
  + Emacs extensions.
**** General
+ Alexandria
  + Standard library.
+ Anaphora
  + Anaphoric macro library.
+ Cells
  + Data flow extensions.
  + GUI framework (e.g. celtk cells-gtk).
+ CL-PPCRE
  + Regular expressions library.
+ CLIM
  + GUI framework.
  + Mainly commercial.
+ Iterate
  + Alternative to LOOP.
+ optima
  + Pattern matching.
+ SERIES
  + Lazy evaluation.
  + Iteration.
+ SPLIT-SEQUENCE
  + Partitioning sequences.
+ LOCAL-TIME
  + Time and dates.
  + Based on Eric Naggum's History of Time.
+ metabang-bind
  + Combines labels, let, flet, destructuring-bind, with-slots,
    with-accessors, and multiple-value-bind into one form.
  + Extensible.
**** Implementation abstraction
+ Bordeaux threads
  + Standardizes Threads.
+ CFFI
  + Standardizes C interop.
+ CL-FAD
  + Standaridzes files and directories.
+ Closer to MOP
  + Meta object protocol.
+ Trivial backtrace
  + Standardizes backtrace printing.
+ Trivial features.
  + Standardizes =*features*=.
+ Trivial Gray streams
  + Ensures CLOS streams (already defacto in most implmentations).
+ Trivial garbage
  + Standardizes weak pointers and weak hash-tables.
+ USOCKET
  + Standardizes the sockets interface.
**** Systems
+ Babel
  + Character encoding.
+ Chipz
  + Decompression.
+ CHUNGA
  + Chunked streams
+ CL+SSL
  + Interface to OpenSSL.
+ Flexi-streams
  + Stream interface over streams for character encoding.
+ Ironclad
  + Cryptography.
+ Nibbles
  + Reading and writing machine types.
+ Salza2
  + Compression.
**** Graphics
+ CL-JPEG
  + JPEG input and output.
+ CL-OPENGL
  + Bindings for OpenGL.
+ CL-VECTORS
  + 2D primitive drawing library.
+ CLX
  + Bindings to X.
+ PNG-READ
  + PNG input.
+ Skippy
  + GIF input and output.
+ Vecto
  + High level interface to CL-VECTORS.
+ ZPB-TTF
  + Parses ttf files.
+ ZPNG
  + PNG output.
**** Web
+ Hunchentoot
  + Web server.
+ Drakma
  + HTTP client.
+ RFC2338
  + Multi-part form data.
+ Parenscript
  + Javascript transpiler.
+ CL-WHO
  + HTML DSL.
+ Postmodern
  + Postgres interface.

>>23
That's all?
And this language is 50 years old?
Wow, it's even less popular than I thought.

>>22
There's plenty of great open source projects too, Maxima, ACL2, Lisa...

Why do you think there isn't?

>>24
No that is not all, not even close to it...

>>25
Because the Lisp philosophy has always been ``I'm the smartest, therefore reinventing the wheel is a good idea.''.
And ``Sharing? What's sharing. Standards and libraries are for ENTERPRISE programmers.''.

>>27
Lisp has one of the greatest standards in existence: ANSI Common Lisp. It's very stable and well crafted. If you write a conformant program, it is very well likely to run on many Common Lisp implementations. However, Common Lisp implmentations provide various extra tools and extensions, (on top of which small libraries were built). It's not a perfect standard, but it's very good.

So I don't know why you think Lisp people don't like standards...

>>29
Past tense.
Rimmus later realised that it's easier to steal credit for other's work and never wrote a line of code again.

>>30
Yes there were a variety of Lisp machines and Lisp OSes from a number of vendors.

You had super computers like the Connection Machine (as seen in Jurrasic Park, and incorrectly referred to as a Cray), to NuBUS extension boards for Macintosh computers (Texas Instruments Microexplorer, Symbolics Ivory etc.) and many things in between.

>>32
But Lisp programmers share code all the time, for example a Lisp programmer from MSI Japan recently got permission to open source much of the utilities he wrote there, to the benefit of all other Lisp programmers.

Most Common Lisp implementations are open source.

As mentioned there's hundreds of community libraries, and people collaborate on things all the time.