Why does no one ever talk about how much it costs to digitize a book or magazine? Of course if Iwant one of those fancy PDFs (PWFs, whatever you want to call ‘em), I’d have to send a PDF to the vendor and abracadabra, I’d get a beautiful interactive product to browse through.

But what about converting text mystelf  if we want to go the re-flowing text route? Or do I have to find an ebook compiler to do it. Seems like it’s something our IT staff can learn — maybe with the help of a consultant — and we can do it inhouse. We’re already using XML, so how much harder can it be? Famous last words .  . .

Web applications are nice. They’re useful, they’re cross-platform, users need no installation, no upgrades, no maintenance, not even the computing or storage power to which they are used. As weird as it may sound, I’ve even seen announcements for web applications supposed to run your games on distant high-end computers so that you can actually play on low-end computers. Go web application!

Of course, there are a few downsides to web applications. Firstly, they require a web connexion. Secondly, they are largely composed of plumbing. Finally, ensuring their security is a constant fight.

How many pipes do you need?

If you have ever developed a web application, you know what I mean by plumbing: just writing an online TODO list — the equivalent of maybe twenty minutes of work in Visual Basic, in Python, Java or Objective-C — requires mixing an insane amount of languages, to define your user interface (HTML, JavaScript, CSS), to define your storage (DDL, DML, DCL, plus possibly an ORM language), to get your server and your client to communicate (XML, more JavaScript, PHP or one of its competitors, as well as some HTTP and a little MIME configuration), to launch your application (whichever configuration languages are used by your server). Of course, if your application is a bit more complex and requires something like compatibility with smartphones, or like distant storage, or distributed computing, or backups, or modularity (in the world of the web, it’s called “web services”)… well, you will probably require a few additional languages.

All of this is just plumbing. Only once you have written it can you concentrate on the core of the application. And once the application is written, the pain is just starting, because chances are that your application can be attacked by hijacking the link between your user interface and the core (cross-site scripting) or between the core and the storage (SQL injection) or by keeping the user interface and replacing the application core (man-in-the-middle attacks) or by replacing the user interface by a malicious client or by taking the place of a currently connected user to steal some of its credentials (rebinding) or by taking advantage of low-level bugs (buffer over/underflows), etc.

None of this is a show-stopper, of course — just take a look at the web and you will see thousands of web applications. Just like the complexity of Software Development Kits in the early days of Windows, MacOS or X didn’t stop adventurous hackers from developing desktop applications. But of course, if twenty-five years of desktop application development have taught us one thing, it is that the life of developers can be made easier. Nowadays, a few generations of SDKs later, Windows developers have .Net, C# and Visual Studio, Macintosh developers have Cocoa, Objective-C and XCode, while X-based developers have the libraries of Gnome/KDE, Python and a variety of programming environments. The growing popularity (and libraries) of Haskell, F#, OCaml, Scala and other functional programming languages could mean that one of the next generations of SDKs will increase safety and security.

The web hasn’t quite reached that stage yet. Even the state-of-the-art in web frameworks only provides features slightly more advanced than early Windows/Mac/X SDKs: low-level bindings for low-level mechanisms, designed to ensure low-level properties. Or, rephrased differently, in the current state of web development, GMail, Google Maps or Facebook are still considered complicated applications, although they are conceptually quite simple and should therefore be equally simple to implement.

We can do better. How? By removing the need for plumbing. By providing automated mechanisms for ensuring high-level security properties. By providing language support for common patterns.

Enter OPA

Let me introduce OPA. OPA, or One Pot Application, is a complete development platform for web applications and web services. Development in OPA requires no plumbing. Applications developed with OPA are automatically checked for safety and security before they are executed. Applications developed with OPA are automatically (and provably) immune to cross-site scripting, to SQL injections and to most existing forms of attacks. And OPA provides language support for storage, communication between client and server (Ajax and Comet), concurrency, distribution, mobility, etc.

With OPA, we intend to skip several generations of SDKs and provide right now a high-level and modern programming platform. OPA has been 6 years in the making: 4 years of sketches, mockups and prototypes as part of academic research projects and 2 years of actual implementation at MLstate. A few days ago, OPA has officially entered demonstrable status. Not quite ready for prime time, but definitely usable for development. Do you want to write an online note-taking application? That’s about 20 lines of code, from scratch. A minimal chat? About 30 lines. A multi-channel, distributed chat? About 80 lines. A minesweeper? About 100. We’re using it to develop utilities, content management systems, tools for administrations and games.

Pre-alpha builds of OPA have been distributed to selected partners. A public version will be made available within a few weeks, as well as commercial applications developed with OPA. In the meantime, we are busy improving the syntax, completing the standard library, making error messages intelligible, fixing the bugs and extending the range of safety and security checks.

Interested? Well, few details are public at this time. However, you can take a look at a video recorded during ICFP presenting OPA and MLstate.

Stay tuned.

wiki reference http://en.wikipedia.org/wiki/Brainfuck

compiler/interpreter: http://wuarchive.wustl.edu/pub/aminet/dev/lang/brainfuck-2.lha

lhazipper: http://linux.softpedia.com/get/System/Archiving/LHa-31904.shtml

PS: for x86 the source code should be modified.. 2nd link Includes interpreter and compiler for the Amiga. The interpreter can be compiled with gcc by removing line 43, which says chkabort();

Heute ist endlich mein über Amazon.de bei einem englischen Händler bestelltes Buch “Programming Interactivity” von Joshua Noble gekommen . Der Untertitel des über 700 Seiten schweren Buches lautet “A Designer’s Guide to Processing, Arduino, and openFrameworks“, also genau das, womit ich mich zur Zeit befasse. Schon beim Stöbern bei Amazon viel mir das äußerst vielversprechende Inhaltsverzeichnis sofort auf.

Aber hier soll es erstmal um die Einrichtung von openFrameworks gehen. Was ist das überhaupt? openframeworks.cc titelt selbst: openFrameworks is an open source C++ toolkit for creative coding. Hört sich schon mal ganz interessant an. Dann wollen wir uns das mal ansehen.

Zuerst benötigen wir einen C++ Compiler für Windows. openFrameworks.cc und “Programming Interactivity” nennen u.a. Code::Blocks (Open Source). Dieser ist schnell runtergeladen (10,8 + 19,3 MB) und installiert. Zusätzlich werden die Code::Blocks Additions für openFrameworks benötigt. Die includes und libs des ZIP-Files kopieren wir nach C:\Program Files (x86)\CodeBlocks\MinGW.

Nun geht es weiter mit dem eigentlichen openFrameworks. Dieses wird von der openFrameworks Downloadseite heruntergeladen. Damit der Compiler die entsprechenden Dateien auch finden und zuordnen kann, sollte der Inhalt des openFrameworks nach C:\Users kopiert werden.

Das wars, nun kann der Spaß beginnen. Am einfachsten beginnt man immer mit dem Leer-Beispiel, was openFrameworks mitliefert. Das würde sich dann in C:\Users\apps\examples\emptyExample befinden. Ordner z.B. auf den Desktop kopieren und emptyExample.cbp starten (im Regelfall sollte diese Dateiendung dann mit Code::Blocks verknüpft sein). Im Programm werden wir hauptsächlich in der TestApp.cpp programmieren:

Wir sehen verschiedene Funktionen. setup() ist vergleichbar mit der setup() aus Processing oder der Arduino-Umgebung. update() wird vor draw() aufgerufen – draw() ist die Dauerfunktion in openFrameworks, so wie loop() bei Arduino und die gleiche draw() bei Processing. Dann sind noch die häufig benutzten Funktionen zum Abfangen von Tastatur- und Mauseingaben deklariert.

Unser Hallo-Welt-Programm soll einen Kreis darstellen:

#include "testApp.h"
#include "stdio.h"

//--------------------------------------------------------------
testApp::testApp(){

}

//--------------------------------------------------------------
void testApp::setup(){

}

//--------------------------------------------------------------
void testApp::update(){
}

//--------------------------------------------------------------
void testApp::draw(){
    ofSetColor(0,0,0);
    ofFill();
    ofCircle(400,400,200);
}

//--------------------------------------------------------------
void testApp::keyPressed  (int key){
}

//--------------------------------------------------------------
void testApp::keyReleased(int key){

}

//--------------------------------------------------------------
void testApp::mouseMoved(int x, int y ){
}

//--------------------------------------------------------------
void testApp::mouseDragged(int x, int y, int button){
}

//--------------------------------------------------------------
void testApp::mousePressed(int x, int y, int button){

}
//--------------------------------------------------------------
void testApp::mouseReleased(int x, int y, int button){

}

//--------------------------------------------------------------
void testApp::resized(int w, int h){

}

Das Ergebnis ist eine 1.226kb große EXE-Datei, die dieses Ergebnis ausgibt:

Eclipse Java Compiler (EJC) is an incremental compiler that is generally faster than any JDKs. It also fixes some incompatible problems related to JDK6, e.g. http://issues.apache.org/jira/browse/OPENJPA-640. This post is about how to run EJC with an ant target to compile your Java projects.

1. Install Ant 1.7+.
2. Download the latest JDT Core Batch Compiler and put it directly into your $ANT_HOME/lib folder. Or, if you have Eclipse installed, you have the compiler by default! Locate the org.eclipse.jdt.core_xxx.jar in the plugins directory of your Eclipse installation, put that jar file into the $ANT_HOME/lib folder, and at the same time unzip this jar file and make jdtCompilerAdapter.jar available to ant.
3. You are now ready to test the Eclipse compiler in command line. The key is to direct ant to use EJC by specifying the compiler parameter -Dbuild.compiler to org.eclipse.jdt.core.JDTCompilerAdapter. Go to a Java project and type in:

   ant -Dbuild.compiler=org.eclipse.jdt.core.JDTCompilerAdapter -Dant.build.javac.target=1.6 -Dant.build.javac.source=1.6 compile
   

4. You can also set up an ant target to play around with it:

   <target name="-eclipse-compile">
     <javac source="1.6" target="1.6" compiler="org.eclipse.jdt.core.JDTCompilerAdapter">
       ...
     </javac>
   </target>
   

418438     เทคนิคของตัวแปลภาษา     Compiler Techniques

ไวยากรณ์ภาษา การสร้างประโยคและความเปลี่ยนแปลงในความหมายของคำแนวคิดของวจีวิภาค และความกำกวมของคำ เครื่องกวาดหาคำแบบกว้าง ไวยากรณ์ของสเตทจำกัด และเครื่องรับรู้ เครื่องกวาดหาคำแบบเรียงตัวอักษร การใช้ตารางสัญญลักษณ์ เครื่องมือของวจีภาค ทฤษฎี และตัวอย่างของภาษาที่เป็นอิสระจากข้อความแคบ และออโตมาต้าแบบพุดดาวน์เทคนิคของวจีภาคที่เป็นอิสระจากข้อความแคบ การแปลข้อความ เทคนิคของการผลิตรหัสที่ไม่ขึ้นกับเครื่อง และการปรับปรุงเทคนิคดังกล่าว คุณลักษณะที่เกิดในตัว และคุณลักษณ์ที่สังเคราะห์ขึ้นมา แผนการแปลข้อความที่อำนวยการโดยวากยสัมพัทธ์

(Grammars, languages, and their syntax and semantics concept of parsing and ambiguity, scanners, finite state grammars and recognizers, lexical scanners, implementation of symbol tables, parser; theory and example of context-free languages and push-down automata, context-free parsing techniques translation, techniques of machine independent code generation and improvement, inherited and synthesized attributes. Syntax directed translation schema.)

(418438 มหาวิทยาลัยเกษตรศาสตร์)

GCC or the GNU Compiler Collection is undeniably the most widely used C/C++ compiler today. Unlike to Microsoft Visual C++ or Turbo C++ compilers, GCC is developed and used by majority of the Open Source community. In fact, GCC is ready out of the box in all Linux distros. Also, GCC is ANSI/ ISO compliant so we are confident that standard functions/ headers such as <string>, etc. are supported. However, since GCC on its own does not have a GUI, we are forced to compile it using the command line/ Terminal. So, how do we use GCC anyway (assuming that an IDE is not available)?

Step 1. In the command line, make sure that you are in the same directory as the  C/C++ source code (.c, .cpp, .cc, .cxx ) you want to compile.

Step 2. If you want to compile a C++ file called ’srcFile.cpp’ and you want to name its executable output as ‘outFile’, type the GCC command following this format:

g++ srcFile.cpp -o outFile

*Note that you should change ‘g++’ to ‘gcc’ if you want to compile C programs.

OrEv.

I don’t personally use Resharper, but a few developers i work with love it, so i thought i’d give it a go.

I won’t bother reviewing it, as that’s something that’s been done everywhere already, but i’d like to highlight 1 particular danger of using such tools: these tools may suggest you do things which are dangerous, and are bad programming practice.

I am posting specifically about Resharper’s hint to replace all variable declarations with the var keyword.

So i looked on the internet, and saw that other people have similar concerns about using the var keyword. I don’t share all those concerns – i think it’s worth using when a variable is created on the same line it is declared. I think it’s very dangerous to use it when capturing the return value from a method call.

This is okay:
var myList = new List<int>();

This is not okay:
var myList = peopleDataAccess.GetPeopleIDs();

If you are not familiar with C#, or especially if you are not familiar with the new features being added to C#, it’s tempting to take Resharper’s suggestions on face value.

However, in the second example above, myList is now depending on the return value of a particular method. If that method is refactored such that the return type changes, the line above will still work fine, but using the variable elsewhere in the function will probably cause a compile time error. If you were explicit and said what you expect the method to return, the compiler would point to the declaration of the variable being wrong, not the use of it.

This is a big problem if you have many developers working on a project – if you change the return type, and update all the references, other developers may still get problems when they update to the latest version on their branch and get strange “method doesn’t exist” errors at compile time. If they were to instead get an error on the variable declaration line, they can see GetPeopleIDs now returns a PeopleIDCollection object (for example), rather than a list of integers, and fix the code much more quickly.

Why make developers hunt around for the cause of the problem, when the compiler can point to the cause directly?

So the moral, if there is one, is probably: Be wary of the advice that tools are giving to developers.

İndirmek isteyenler için(Boyut: 25,4 MB):

Download MinGW Developer Studio

Σε διάφορα φόρα ανα τακτά χρονικά διαστήματα υπάρχει και κάποιο topic στο οποίο ζητείται να προταθεί κάποιος μεταγλωττιστής για κάποια γλώσσα προγραμματισμού. Μιας και αυτό το blog δραστηριοποιείται γύρω απο την γλώσσα προγραμματισμού C++ θα γίνει εδώ μια μικρή αναφορά σε compilers και στα IDE που τα συνοδεύουν.

MS Visual C++ 2008 Express [Compiler + IDE]

Η πρόταση της Microsoft για την C++.  Περιλαμβάνει ένα σύνολο απο εργαλεία τα οποία διευκολύνουν την ανάπτυξη και συντήρηση εφαρμογών. Είναι ο “μικρός” αδερφός του Visual Studio και διατείθεται δωρεάν στην παρακάτω διεύθυνση: MS C++ 08 Express Περιλαμβάνει compiler, IDE, debugger, Win32 API για άτομα τα οποία ενδιαφέρονται για native application programming.

Δεν περιλαμβάνει κάποιον resource editor, ούτε υπάρχει δυνατότητα χρήσης των MFC κλάσεων. Επίσης για να τρέξουν οι εφαρμογές που έχουν δημιουργηθεί με τον compiler, σε άλλους υπολογιστές, απαιτείται η εγκατάσταση του κατάλληλου restributable package διαφορετικά η εφαρμογή θα τερματίσει με ένα μήνυμα σφάλματος.

Sebetulnya UTS hari ini (jam 9 nanti) tentang intelejensia kolektif yang bahannya tentang EA (evolutionary algorithm) dan ACO (ant colony optimization), tapi yang dibaca sebelum tidur malah buku Practical Software Maintenance-nya Tom Pigoski. Kebetulan memang untuk kuliah pengujian perangkat lunak kebagian bab tentang testing pada saat maintenance. Baru baca bab-bab awal. Persepsi awal tentang isinya lumayan menarik sambil merefleksikan masa-masa yang pernah dialami (sebetulnya istilah pengalaman lebih singkat tapi punya makna konotasi yang bisa baik bisa juga jelek ).

Singkat kata, dari bacaan awal bisa diceritakan bahwa perawatan (padanan untuk maintenance) seringkali memiliki banyak interpretasi. Perawatan bisa jadi merupakan pengeluaran yang kecil dibanding biaya pengembangan atau justru menjadi pengeluaran utama dibanding biaya pengembangan. Interpretasi pertama dicirikan dengan adanya alokasi sekitar 10% untuk ‘support & maintenance‘, sedangkan interpretasi kedua mengalokasikan 80% untuk hal tersebut. Pertanyaan pertama yang muncul adalah “Yang mana yang lebih baik? untuk developer, maintainer, dan customer” (pengguna dibedakan dengan customer dan dikesampingkan dulu karena berdasarkan buku tsb, tersangka utama penyedot biaya perawatan adalah pengguna).

Pihak yang melakukan perawatan pun bisa jadi bukan pengembang perangkat lunak awal melainkan pihak lain yang mengkhususkan diri di bidang perawatan perangkat lunak (itu cerita di bukunya dengan situasi di US, kalau di Indonesia ada tidak yah (organisasi spesialis perawatan)?).

Sebelum mencoba menjawab pertanyaan di atas, cerita lain tentang isi buku tsb adalah bahwa aktivitas yang dilakukan dalam proses perawatan bisa digolongkan menjadi 3 kelompok, yaitu:

• corrective
• adaptive
• perfective/improvement

Kunci dari keberhasilan proses perawatan (lagi-lagi berdasarkan buku tsb.) adalah mengklasifikasikan hal-hal yang perlu berubah ke dalam kelompok tersebut. Pengklasifikasian di atas disusun berdasarkan prioritas dan resikonya. Kisaran proporsi ketiga kelompok tersebut berturut-turut 20%, 25%, dan 55%. intinya, kebanyakan dari perawatan adalah improvement. Celakanya permintaan atas improvement ini nggak melihat struktur perangkat lunak ada. Jadi ingat pernah ada yang minta ganti grid (standar VCL Delphi) biar tampak lebih menarik (Dibandinginnya dengan DataGrid defaultnya Flex). Ibaratnya, lagi nyetir mobil kecepatan tinggi tiba-tiba punggung itu gatal!.

IMHO, situasinya akan lebih enak kalau deskripsi sistem yang mau dibikin itu bisa selesai di 10% (lebih enak lagi kalau verifikasi kesesuaian dengan spesifikasinya bisa dilakukan otomatis menggunakan metode formal) waktu total pengembangan sistem sehingga 90 persen sisanya adalah proses maintenance & testing untuk menyesuaikan dengan kebutuhan yang diyakini selalu berubah. Aspek adaptif dan perfektif berhubungan dengan antarmuka dengan sistem lain (infrastruktur perangkat keras, API, sistem operasi, target deployment platform), dan manusia (user interaction).

Saya sendiri sebetulnya lebih tertarik ke interaksi. Bayangan saya adalah user interface yang dinamis (bukan sekedar style/theme yang hanya mencakup aspek estetis, tetapi juga struktur hierarki, tata letak, dan pemilihan komponen interaksi) yang menyesuaikan dengan target deployment platform (desktop, web, mobile) dan selera pengguna. Untuk itu diperlukan tool untuk membantu perancang interaksi (paradigma Microsoft) atau menjadi fasilitas yang terintegrasi dengan sistem yang digunakan oleh pengguna (end-user development). Satu hal yang pasti dengan adanya sistem antarmuka yang dinamis dan universal ini lahir kebutuhan baru yaitu pembuatan manual penggunaan yang otomatis juga.

Kalau diinventarisasi, untuk menyelesaikan persoalan di atas (pembangkitan antarmuka dan manual ~ user interface and instruction manual generation) perlu beberapa hal berikut:

• pemodelan domain arsitektur informasi, interaksi, dan kapabilitas platform (domain spesific modeling, MDA) termasuk model pembangkitan teks narasi untuk menceritakan skenario interaksi(natural language processing) menjadi bahasa spesifik (domain spesific language).
• teknik kompilasi, khususnya untuk proses generation dari domain spesific language ke kode target platform
• pengetahuan tentang interaksi (teori aktivitas dan teori kognitif) yang menjadi batasan pada proses pencarian solusi
• Teknik optimasi kombinatorial untuk menghasilkan solusi berupa konfigurasi yang diharapkan

Tampak terlalu besar cakupannya untuk dijadikan tesis (mungkin harusnya jadi program riset kk/unggulan?) dengan sisa waktu kurang dari satu semester. Mungkin bisa dibatasi lagi supaya lebih layak mengingat masih ada konsep-konsep yang sifatnya vague.

ELECTRONICS

• How to make an LED work
• BJT configurations
• Estimating transmitter distance
• CAPACITORS
• RESISTORS and RESISTANCE
• what is heterodyne?
• Test your TV remote contorl.
• Capacitor Circuit In an electronic circuit, a capa…
• data sheets
• 1)WinRLC’ is a tool for electronic calculations.
• IR MUSIC TRANSMITTER AND RECEIVER
• Basics of Audio Electronics
• DDR3 memory chips
• DDR3 SDRAM
• The name operational amplifier was originally give…
• Basics of op-amp
• door bell
• HamCalc-A program for radio calculations
• Mat switch
• AVR dealy calculator

COMPUTERS and INTERNET

• Recommended Software in Design and Technology
• 50 blog directries to submit your blog for free
• Understanding the Components of a Home Network
• A History Into Microsoft Products
• Clean your keyboard-part 2
• Clean your keyboard
• web based calculater
• shrink the size of any file
• online backup
• Improving browsing performance for Internet Explor…
• How to turn off third-party services
• My Computer Won’t Shut Down Itself After Installin…
• How to Rename the Recycle Bin
• Add sound to almost every event in Windows
• Saving Web Pages with Internet Explorer 6
• When you connect to a web site your computer sends…
• Make XP boot even Faster
• Speeding up your browsing by increasing your cache…
• How to test user profiles
• Hide ‘User Accounts’ from users
• Disable CD Autorun
• AVI File Fix in Windows XP
• Remove the Recycle Bin from the Desktop
• Windows XP Doesn’t Remember Folder Settings Anymor…
• Remove “Standby” option from shutdown menu.
• Internet Explorer – Increase the number of concurr…
• convert your pc to hometheatre pc
• offline blog editor
• TRICK TO TEST WHETHER YOUR ANTIVIRUS IS PROTECTING…
• Free Download High resolution wallpapers for Windo…
• FAQ’S in C- II
• FAQ’s in C

LINUX

• Why LINUX is virus proof
• Complete Overview of Linux
• Convert man Pages to Text
• Find out what a command does
• writing the linux device driver
• linux installation made easy
• The linux file system explained

MOBILE STUFF

• LG mobile codes
• 10 things you dont know about nokia
• GSM secret codes

em construção…

Astazi de  dimineatza eram la cursul de Modelare Numerica a Proceselor Fizice, implementarea fiind facuta in C++. La un moment data proful vorbea despre pointeri despre adrese de memorie etc. si ajunse la faza sa dea si un exemplu. Ciudat, bizar nu stiu cum sa-i spun dar s-a intamplat sa-i nu-i mai functioneze compilerul de C++, a incercat el tot felu de metode sa il faca sa functioneze, dar nimic. Ma roaga sa il ajut, sa fac exemplul pe terminalul meu:) ok d’accord, dar intamplarea ciudata era ca nici mie nu imi mergea compilerul:)) Tre bizarre…:)) Cum s-a facut, cum nu….. dar era destul de ciudat ca in acelasi timp sa nu functioneze la nici unul…

ECM sent me this awesome post from Uncommon Descent. The post explains how someone who doesn’t want to read about intelligent design can learn what intelligent design by doing. That’s right – you can learn about intelligent design by practicing intelligent design.

Excerpt:

Of course a good example of design would be engineering in all its specialties. Unfortunately almost all fields of engineering are inaccessible to laymen for many reasons. But the good news is that there is a field that is theorically and practically available (at least at a basic level) to almost all people (or at least to scientific-minded people as most ID deniers are): computer science. Our suggested patent-pending method to become IDer is based on computer programming. Developing programs gives ID refuters a lot of advantages to learn ID.

(1) Computer programming is an activity where, differently from literature, philosophy, journalism and so on, a severe control overarches all the design cycle. In programming errors matter, also the minor ones are never condoned. This is good discipline for the student, to be always forced to correct his errors. If you write a book filled with errors, no worry, it will be published the same. If you write a program with one error nothing works. This is the difference between storytelling and programming. Usually there are at least two kinds of control or filter: at compilation time and at run-time. Any program works only if it passes the two filters.

[...](2) Computer programs don’t arise by unguided evolution. They entail CSI and only intelligence can create CSI. Whether software were generable by mean of randomness and machines, software houses wouldn’t need to pay legions of expensive programmers. When you are programming you see directly your intelligence at work. Eventually other programmers can help you but no other unintelligent thing can do the job for you.

(3) To develop programs is a good exercise to learn CSI, IC, nested functional hierarchies, sub-functions, structures, dependences among parts, meta-information, libraries, etc.

Intelligent design is nothing more than sequencing a large number of parts into a chain that has function. That’s it – that’s all it is. God is a software engineer. And if you’re interested in seeing some of the published research done by ID theorists, check out this list of their publications in scientific, peer-reviewed research journals. (H/T Truthbomb Apologetics)

There is only one problem with the post at UD, though. They recomment Perl and PHP for the exercise. Perl and PHP are crappy languages for any program longer than 100 lines that needs to be maintained longer than 2 months, or maintained by another developer who did not write it. The readability and maintainability of Perl and PHP are atrocious. Stick with languages like Java, Smalltalk or C#.

Other arguments for a Creator and Designer

To learn more about arguments for a Creator and Designer, check out some of my favorites below, taken from the big list of arguments and counter-arguments:

• The origin of the universe
• The fine-tuning of the universe for complex life
• The galactic, stellar and planetary fine-tuning to provide a habitable environment for complex life
• The origin of the building blocks in the simplest replicating cell
• The origin of biological information in the simplest replicating cell
• The sudden origin of all major body plans in the Cambrian explosion
• The natural limits to biological change

While Adobe knows that a Flash plugin for iPhone won’t likely happen (besides strategic reasons around RDA, this is the result of long non optimized Flash for OSX), they are trying to circumvent this restriction, by providing a compiler (based on LLVM) that will produce ARM assembly code from ActionScript programs. It will be included in Flash CS5 (a beta is expected by the end of the year), and will work on both mac and Windows.
The limiting factor will be the lack of debugger, but it should be ok for simple applications, as development and debugging could be made on a desktop computer (by simulating the iPhone drawing area and limited processor power). The compiler would then be used only at integration test steps, and for final deployment. However, for more advanced (demanding) applications or games, such solution will end being very difficult and tedious, as optimizing near the limits won’t be possible.
Finally it will paves the way for paid Flash applications on iPhone (there have still been some iPhone games derived from free Flash games).