Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262640AbTIHP2I (ORCPT ); Mon, 8 Sep 2003 11:28:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262690AbTIHP2H (ORCPT ); Mon, 8 Sep 2003 11:28:07 -0400 Received: from dns.toxicfilms.tv ([150.254.37.24]:15510 "EHLO dns.toxicfilms.tv") by vger.kernel.org with ESMTP id S262640AbTIHP05 (ORCPT ); Mon, 8 Sep 2003 11:26:57 -0400 Date: Mon, 8 Sep 2003 17:26:51 +0200 (CEST) From: Maciej Soltysiak To: "Ihar 'Philips' Filipau" Cc: root@chaos.analogic.com, Linux Kernel Mailing List Subject: Re: [OT] Re: nasm over gas? In-Reply-To: <3F5C9BDA.9080705@softhome.net> Message-ID: References: <3F5C9BDA.9080705@softhome.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1219 Lines: 28 > I have a long standing dispute with one of my friend: once he has > said 'asm is dead - every one is using C/C++ now'. Stating that asm is dead is not realizing that it is really important in some niches. Niches which must be in asm to provide the best for the customers. This is and will be common in 'programming language wars'. Dead technologies are not used. Asm is used, therefore Asm is not dead. This is the definition, and the sentence to counter 'asm is dead'. > What will be next? In my short carrier I saw as Asm was dying three > times. But I beleive it will reborn over and over again ;-))) Pascal will be next I think. Or any other language that does not resist the trends. C/Java/Python - Those guys are surfing the wave of modern programming, and rapid development. Others like cobol, fortran, etc. are just unknown, and thus some people think they are dead. Another thing: Programming languages do not die, They just fade away Regards, Maciej - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/