Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Apr 2004 06:52:57 +0400
From:      Sergey Zaharchenko <doublef@tele-kom.ru>
To:        Chris Ashlee <chrisa@uvic.ca>
Cc:        freebsd-chat@freebsd.org
Subject:   Re: Beginning C++ in FreeBSD
Message-ID:  <20040423025257.GB350@Shark.localdomain>
In-Reply-To: <40884502.9060301@uvic.ca>
References:  <200404151110.i3FBAaoo048373@adsl-68-76-19-75.dsl.klmzmi.ameritech.net> <200404171050.29467.dgw@liwest.at> <20040417123848.GA244@Shark.localdomain> <200404202139.53518.dgw@liwest.at> <20040421162837.GA296@Shark.localdomain> <40884502.9060301@uvic.ca>

next in thread | previous in thread | raw e-mail | index | archive | help

--4bRzO86E/ozDv8r1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 22, 2004 at 03:19:46PM -0700,
 Chris Ashlee probably wrote:
>=20
> All of these are good points, and debunk assembly's supposed advantages.=
=20
> But the difficulty of writing fast assembly code on any decent=20
> architecture (ie. not x86) is really the least of its problems. The=20
> worst of its problems:
>=20
> 1) It takes longer to write,
> 2) It takes longer to debug,
> 3) It's much harder for others to understand,
> 4) It's MUCH harder to change,
> 5) It limits you to one CPU architecture.
>

These have been mentioned already; somehow, they didn't seem to persuade
someone we wished to persuade:)

>=20
> But writing *everything* in assembly is not the way of good software=20
> engineering, for all the reasons I mentioned above. While you write your=
=20
> programs in assembly language, everyone else is writing code in half the=
=20
> time, debugging it in a quarter the time, and it can be changed more=20
> easily to add new features or adapt to changing requirements. And it=20
> runs just as fast, too!
>
> The focus in software engineering these days is not on more performance:=
=20
> we've already solved that problem. The focus is on developing things on=
=20
> time, on budget, that meet the ever-changing requirements. Assembly is a=
=20
> poor choice for all of these needs. Daniela, if you ever want to=20
> collaborate on software projects with other programmers, you're not=20
> going to be able to do it in assembly language. Bear this in mind as you=
=20
> continue to learn as a programmer.
>=20

I don't really like the `programming means managing time and budget'
approach. Too many people here in our university don't have the sense of
measure in these things, and they start mixing the process of
programming with the process of getting money for nothing:). But
maintainability is really important. So, for me, the 4) point wins, with
3) as its closest rival.

--=20
DoubleF
"He's the kind of man for the times that need the kind of man he is ..."

--4bRzO86E/ozDv8r1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAiIUIwo7hT/9lVdwRAkHjAJ4yKOwYNvApJS9EJnyoJfjT74STTACfRkqU
cKpeB5xkFhh0GTrqzB9y3R8=
=wNbu
-----END PGP SIGNATURE-----

--4bRzO86E/ozDv8r1--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040423025257.GB350>