As a longtime Delphi developer I've been reading everything I can find about Kylix in anticipation of trying it out one of these days. However, I was disappointed in Petr Sorfa's review of the product (LJ August 2001 issue), in particular with his unsupported assertion that “the main problem, of course, is the Object Pascal programming language itself.”
If that's the main problem with the product, at least say why. As far as I can tell from the review his major problem with the language was “getting used to the := symbol for assigning variable values”. Big deal—all new languages take some getting used to.
Methinks there's some C++ snobbery here. Object Pascal is, admittedly, a proprietary language (like Java), which is what he may be getting at. However, it is a full-featured, object-oriented language similar to Java in features and general approach (with the exception of Java's automatic garbage collection). I think it deserves a little respect.
I've been interested to read the Geek Law column in the last couple of issues of LJ. While I wasn't surprised to see a disclaimer at the end of each column, I was surprised that there's no mention of the advice being relevant only to the US legal system. While the articles so far have mentioned Congress and the US, I think it would be helpful for it to be stated explicitly that the author is writing from the point of US law.
Even in the UK (from where I am writing), we have three different judicial systems: one for England and Wales, one for Scotland and one for Northern Ireland. There's no guarantee that something that is legal in England and Wales is legal in Scotland, for example.
Who says one voice can't make a difference? Larry reminds us that not only does law vary nation to nation, but even within the US from state to state. He has modified the disclaimer.
I have to comment on the Cooking with Linux column by Marcel Gagné. The French chef gag is funny for about two minutes. Then it becomes tiresome. Another few minutes and it becomes downright irritating. By the time I finish a column, I'm ready to lock François in the wine cellar and throw away the key. So I seldom finish the column, which is a shame because otherwise it's well written and interesting. Please, Marcel, consider ditching the gag.
—Daniel D. Jonesetcfirstname.lastname@example.org
Mon cher ami, perhaps the ungarnished and simple shipboard food you enjoy in the navy has influenced your palate. Some people like a little French seasoning with their technical staples. Linux isn't all free bière—un peu du vin est nécessaire aussi.
I am surprised that one of your readers should be offended by a biblical reference in the June 2001 Best of Technical Support, page 96. Perhaps Noel Moss has nothing better to do than to take it upon him/herself to try to curtail the author's first amendment right to freedom of the press, regardless of literary intent. I'm certain the reader would not have been offended if the reference had come from the Koran, or the Book of the Dead, rather than the Bible. I read Linux Journal cover to cover and have not once been offended by its content. Keep up the good work.
Thanks Paul, I was beginning to think there were no unoffended readers left.
The August 2001 issue of Linux Journal stated:
There are three editions of Kylix: Open, which is available for free (downloadable) for noncommercial GPL development (or $99 US for a hard copy version); Developer, for commercial use with a limited number of features and components ($999); and Server, with all of the features and components ($1,999).
I have reviewed most of the Borland web site (including community.borland.com) and can't seem to locate any but the trial edition of Kylix for download. How can I find this open (GPL) edition for download?
Kylix Open Edition was released only recently and is now available at borland.com/kylix/openedition.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Tech Tip: Really Simple HTTP Server with Python
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide