Slashdot Mirror
Domain: leap-cf.org
Stories and comments across the archive that link to leap-cf.org.
Comments · 9
-
Re:Er, no, not really
Google goes nuts when it runs into PHP iCalendar. It sees every link as a new page to look at, and after a few runs by googlebot, it's trying to index the daily calendar page for every day within a decade of today.
Yeah, I've seen similar problems before. At least you still have your data. -
Re:Cyrus IMAP for sure..You still have not addressed how a compiler can modify a system in dangerous ways more easily than an interpreter. What can a C or C++ program do that a Perl or Python one can't? Let's revisit the original post:
As for the rhetorical question on adding bash, perl & python, bash is a command shell and is unlikely to be made into a tool that can be used to modify production application components. Perl & python are interpreted languages, and such if the application depended on perl or python, you would have to install them. If/when perl & python can be used to generate binary code, then good system management practices would discourage the placement of perl or python on a "production" server.
Bash, Perl, and Python can all be used to generate binary code or any other kind of code. As an example, there's a assembler written in Bash. Even worse, if you can run one of those interpreters on a system, you don't need to generate binary code; you can do all kinds of mischief by sending source straight to the interpreter.
So, you see I'm not attacking a straw man, I'm pointing out the flaws in your logic.
By the way, Python is both a compiler and an interpreter. You see those modules in ".py" files? When you import the module, the compiler compiles the source, then writes a file of the same name with an extension of ".pyc" or ".pyo" if it can. You can then remove the source ".py" file and everything will still work. Do the ".pyc" and ".pyo" files have native machine code? No. Does that make them less capable or any less compiled? Not really. -
Re:good
here you go! remember me when you start making $$$$ fast.
-
Re:i like maddogOver the years, I've heard Jon talk several times.
The last time was March 2003 in Orlando, Florida at a join user meeting of Linux Enthusiasts and Professionals of Central Florida and the Melbourne (Florida) LUG.
I wrote about it in my
-
Users running Turbo
>> Ya know, I can't think of a single person that I know that runs Turbolinux. Maybe that has something to do with their problems.
In the Central Florida LUG, Linux Enthusiasts And Professionals there is at least one user according to our latest informal poll.
Results from the October 2000 and July 2001 polls are here:
Oct. 2000
July 2001
Over the years, Red Hat, Debian, and Mandrake have consistantly been the top distros of choice... -
Users running Turbo
>> Ya know, I can't think of a single person that I know that runs Turbolinux. Maybe that has something to do with their problems.
In the Central Florida LUG, Linux Enthusiasts And Professionals there is at least one user according to our latest informal poll.
Results from the October 2000 and July 2001 polls are here:
Oct. 2000
July 2001
Over the years, Red Hat, Debian, and Mandrake have consistantly been the top distros of choice... -
Users running Turbo
>> Ya know, I can't think of a single person that I know that runs Turbolinux. Maybe that has something to do with their problems.
In the Central Florida LUG, Linux Enthusiasts And Professionals there is at least one user according to our latest informal poll.
Results from the October 2000 and July 2001 polls are here:
Oct. 2000
July 2001
Over the years, Red Hat, Debian, and Mandrake have consistantly been the top distros of choice... -
Users running Turbo
>> Ya know, I can't think of a single person that I know that runs Turbolinux. Maybe that has something to do with their problems.
In the Central Florida LUG, Linux Enthusiasts And Professionals there is at least one user according to our latest informal poll.
Results from the October 2000 and July 2001 polls are here:
Oct. 2000
July 2001
Over the years, Red Hat, Debian, and Mandrake have consistantly been the top distros of choice... -
Documentation language, then documentation GUI
First off, don't put your documentation or data at risk, always use standard documentation languages. Languages that are not only open, not only formats taht will last for decades, but formats that are 100% facimile reproducable. Think like a publisher.
With that said, SGML with strict DTDs is key. Factor in the ubiquious nature of other, widespread documentation languages like TeX/LaTeX, HTML, XML and, now, DocBook and its obvious that you want to standardize on SGML and DocBook and convert between them all. Plus you need to be able to make PDFs quick and easy.
Now you need a GUI. The problem with most GUIs is that you are limited by them. Not LyX, it is highly-extensible and more and more features are added by the moment. Originally a WYSIWYG (actually WYSIWYM, "what you mean") for TeX/LaTeX, LyX can eat TeX/LaTeX, SGML and other mark-up in-line. Again, you have a GUI, but you are not limited by it.
From the GUI standpoint, LyX has automatic TOC, TOF, biblio, indices, notes and other table/figure generation. I personally love LyX for its margin note and sidebar features, as well as headers and footnote. Lastly, LyX can eat EPS in-line and the PostScript preview is exactly what PostScript will go to your printer (I hate apps with print previews that aren't exact).
Lastly, built in support for RCS/CVS revision control makes it an ideal application for multiple tech writers. IMHO, who need limited collaboration tools when you have real revision control underneath?
If you're looking for a quick "HOWTO" to getting LyX installed, there is one for RPM-based distros here..
-- Bryan "TheBS" Smith