LaTeX

I have mixed opinions on it.
It Just Works™...

...but it's so inconsistent! Compare, for instance,
$\circ$ and $\diamond$
A bigger circle is \bigcirc, so what's a bigger version of \diamond? That's correct! \Diamond!
There are obviously more examples, but I ask: where's the normalisation?!

Just stick to T_EX, you'll be better off.

>>2
Where can I start learning T[sub]E[/sup]X?

>>3
Terrible! ^B_B^C_o^d_e

>>3
http://www.amazon.com/The-TeXbook-Donald-E-Knuth/dp/0201134489

^T_B^E_B^R_C^R_O^I_D^B_E^L_!^E

kike^{kikekikekikekikekike}kike

J^AV_ASCRIPT is better. use it.

How do I use plainT_EX without LaTeX? Ideally to still product PostScript/PDF files.

Why not AsciiDoc?

Or if you fucking need type setting, use PS or DjVU.

when will javascript replace bbcode?

when will you check my dubs?

\newcommand{\Circ}{\bigcirc}

>>12
NO COMMON SENSE ON /PROG/!

>>12,13
SPAWHBTC

>>14
SHALOM NIGGER!

>>13
Forking the language with macros to enforce naming conventions which no library will respect is in no way a reasonable thing to do.

>>16
Forcing the anus with cocks to enforce gay conventions which no redneck will respect is in no way a reasonable thing to do.

>>16
why not?

>>18
"fart once, shit's everywhere"

>>19
it's ok as long as the fart is contained within a module. Then it's just a shitty module.

Is there any good alternative for beamer?

I got used to it pretty quick. Especially if you have editor that checks and completes macro names (like Emacs' AUCTeX).

I ain't writin no book.
rst2pdf within emacs is good enough for me.

>>18
It's a fool's errand. It will be an herculean task to find each and every LaTeX command and frequently used package and force naming and ``API'' conventions, only for them to break with every uncommonly-used package and newly created one.

Then you'd have decade's worth of documentation and code samples contradicting your new conventions, and thus hordes of new users breaking them just like the old.

I'm not saying it can't be done; the Perl community got everyone to use the [code]use strict[;/code] and [code]use warnings[;/code] pragmas by way of social pressure in order to prune a bit the insanity of their language.

It'd take a new LaTeX book and sexy new packages depending on them to take the community by storm, after they are already set in place and cover a fair bit of the language, but in the end you'd still have the same old crufty and brittle language that is (La)TeX macro language underneath, with no namespaces or scopes, with fixed-size everything, and mysterious breakage with some extra whitespace in the code, with a better facade, after man-years of effort.

no namespaces or scopes
Does it really need that? Sure T_EX may be Anal Touring complete, but it's still just a markup language.

>>24
sed "s/$\circ$/\newcommand{\Circ}{\bigcirc}/g"  *.tex > *_w\/circ.tex

The again, why us T_eX? It ain't portable, And broken as shit. It was great on 1980, before PS was made.

>>26
PostScript is a replacement for TeX? I guess I should try it out.

>>26
Different application for a different purpose. Enjoy manually hyphenating your text.

>>27

nooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

>>29
nooo what?

>>30

%!PS

/Courier findfont 12 scalefont setfont

/noo {
  1.2 1.2 scale
  35 rotate
  (o) show
} def

/do-times {
  0 index 0 eq not {
    1 index exec
    1 sub
    do-times
  } {
    pop pop
  } ifelse
} def

200 200 moveto
(no) show
{noo} 23 do-times
showpage
save
restore