[Info-vax] Rust as a HS language, was: Re: Quiet?

[plugh]

On Thursday, April 7, 2022 at 9:33:57 AM UTC-7, chris wrote:
> On 04/07/22 17:03, plugh wrote: 
> > On 4/7/22 08:46, chris wrote: 
> >> So the typical process these days is rapid development, which skimps 
> >> on process and testing and debugs the product at the customer. I 
> >> don't think any language can cure that, as it's the process and 
> >> attention to detail that are missing and no fault of the language 
> >> involved. To suggest that sort of thing can be fixed by the 
> >> current language fashion of the month is fantasy and ignores 
> >> the main problem... 
> > 
> > With all respect, your confirmation bias is showing. 
> Not sure abut confirmation bias. Probably worked in over a dozen 
> companies, freelance over the decades and becomes easy to see which 
> are the well managed ones, and those who prioritise cost over quality. 
> You may learn the basics at uni, but really need to be at 
> the sharp end in industry to understand the endless conflict trying 
> to maintain professional standards. That's not bias, just hard won 
> experience... 
> 
> Chris

I remember meeting a Digit at a SAAS vendor conference in Phoenix a few years ago, mutually lamenting at the lack of formal engineering going into many of today's software products.  I can't control which abstract 2-out-of-3 product features will be chosen, but I can control how I respond when faced with a concrete choice.

After a year studying this language, I feel confident deploying a production program on Debian Stable.  I know with (more or less) absolute certainty, that such a program could compile and load on VMS with no source code change (and if the underlying runtime libraries were also available). That's the kind of guarantee I'm talking about.