Prof David West wrote:
Years ago, companies were demanding that all of their applications be
written in C++, because of speed and because of "features" like multiple
inheritance and friend declarations that "improved the efficiency of
your code."
Even Squeak introduces `traits' for aspect-orient
Thus spake Prof David West circa 16/02/09 05:51 PM:
> It IS dumb. Not for you as the developer, but on the part of the client
> for making it a "requirement."
The client doesn't _make_ it a requirement, as if requirements are
created willy-nilly by some air-headed marketing type (no offense
inte
Thus spake Prof David West circa 16/02/09 05:47 PM:
> Thus spake glen e. p. ropella circa 16/02/09 16:02 PM
>
>> The next trick is to transition ... to more
>> formal, repeatable, and communicable processes.
>
> There are no such things.
Yes, there are. But you may not be hearing those words t
They had the seed of one. Self did not have the class library and range
of functionality of Smalltalk and, more importantly for Sun, it had no
user base; at the time that Smalltalk was being touted as the "next
COBOL" because of the extent to which is was being used in industry.
There was, from
Thus spake glen e. p. ropella circa 16/02/09 11:12 AM
> When I write a
> program for a client and that client's requirements include taking over
> and developing the code themselves, then choosing Java because "Java
> developers are cheaper because there are more of them" is not only NOT
> dumb, i
Thus spake glen e. p. ropella circa 16/02/09 16:02 PM
> The next trick is to transition ... to more
> formal, repeatable, and communicable processes.
There are no such things.
Formal only applies in the small number of cases where the domain you
are trying to understand and in which your softwa
Two events tomorrow that may be of interest to you:
At 10:00, Dr. Eugene Agichtein, an assistant professor in the
Mathematics and Computer Science Department at Emory University,
discusses his research on mining the web for useful information about
users and usage. For more information, vis
Thus spake Nick Frost circa 16/02/09 03:01 PM:
> because I felt it would be irresponsible of me to leave the job to a
> recent college graduate (as occurred) who might not have had any
> experience with Ruby (for example).
>
> [...]
> IMHO, the needs, considerations, and
> motivations of a sysadmi
On Feb 16, 2009, at 12:12 PM, glen e. p. ropella wrote:
Thus spake Prof David West circa 14/02/09 01:24 PM:
Language selection reasons like, "it is too hard to learn," "memory
leaks," "it runs faster," "Java developers are cheaper because
there are
more of them," etc., are really dumb reason
Given that a Steve Yegge blog post started this discussion, you might be
interested in another (earlier) post of his
http://steve-yegge.blogspot.com/2007/02/next-big-language.html
and something more for the Javascript fan-boys:
http://javascript.crockford.com/javascript.html
BTW having work
Marcus G. Daniels wrote:
> Parks, Raymond wrote:
>> Owen Densmore wrote:
>> ...
>>
>>> Really hip programming teams will define a subset of all these systems
>>> that are platform independent -- i.e. work on all systems. They will
>>> stick to these subsets, understanding that sometimes con
Parks, Raymond wrote:
Owen Densmore wrote:
...
Really hip programming teams will define a subset of all these systems
that are platform independent -- i.e. work on all systems. They will
stick to these subsets, understanding that sometimes constraints
really are freedoms.
I hav
Owen Densmore wrote:
...
> Really hip programming teams will define a subset of all these systems
> that are platform independent -- i.e. work on all systems. They will
> stick to these subsets, understanding that sometimes constraints
> really are freedoms.
I have a colleague who insists
Thus spake Prof David West circa 14/02/09 01:24 PM:
> Language selection reasons like, "it is too hard to learn," "memory
> leaks," "it runs faster," "Java developers are cheaper because there are
> more of them," etc., are really dumb reasons for choosing a language.
> Instead you should focus on
On Sat, Feb 14, 2009 at 2:24 PM, Prof David West wrote:
>
>
> 2. Except for a really dumb decision on the part of ParcPlace, Java
> would never have come into existence. Sun wanted Smalltalk, and only
> when rebuffed, decided to morph Oak to Java. (An earlier, equally
> stupid, decision forced A
On Mon, Feb 16, 2009 at 7:28 AM, Prof David West wrote:
> On Sun, 15 Feb 2009 20:58:43 -0700, "Owen Densmore"
> said:
>
>
> > Re: Ruby -- It really does not cut it.
>
> I probably agree - but can 100,000 avid users be wrong? I included it
> in my list only on the basis of popularity for Web-only
I finally got around to looking up the Lively Kernel:
http://research.sun.com/projects/lively/
I'm impressed! Entirely written in Javascript. No downloads required
(apparently like GoogleMaps, you use the Javascript library remotely,
at http://www.experimentalstuff.com)
This is fascinat
Montana moves ahead on support for passenger rail .. fyi. Peggy
-- Forwarded message --
From: Michael Ackley
Date: Sat, Feb 14, 2009 at 9:40 AM
Subject: Fwd: MT STATE LEGIS. UPDATE - Senate Bill 283 - Sat. Feb. 14, 2009
To: Undisclosed-recipients
Begin forwarded message:
*Fro
In case you have forgotten the impacts of coal .. read this Director of
NASA's Goddard Space Science Institute's position:
Peggy Miller
-- Forwarded message --
From: James Hansen
Date: Sun, Feb 15, 2009 at 8:10 PM
Subject: The Sword of Damocles
To: j...@columbia.edu
To be remo
Owen wrote:
Architectural studies look at the system from a 50,000 foot view, so
that the student can understand how the whole system works.
Implementation studies look at how a practitioner would, on the job,
build part of a system.
If in fact it is possible for a student to understand
On Sun, 15 Feb 2009 20:58:43 -0700, "Owen Densmore"
said:
> I'm with Nick. Why? We have to separate understanding *architecture*
> from implementation.
>
> Architectural studies look at the system from a 50,000 foot view, so
> that the student can understand how the whole system works.
>
>
21 matches
Mail list logo