4 ms·

There are many problems with this website. I couldn't actually find the meat of it, where the intro page talked about what it could do for us. Inconsistent tit

by keyle 10mo ago

There are many problems with this website. I couldn't actually find the meat of it, where the intro page talked about what it could do for us. Inconsistent titles, stuff labelled [TOC]. It might be a work in progress and not really ready to be shared widely.

Joel_Mckay 10mo ago
Languages like C are simply very unforgiving to amateurs, and naive arbitrary code generators. Bad workmanship writes bad code in any language. Typically the "easier" the compiler is to use... the more complex the failure mode. =3 Vibe coders usually offer zero workmanship (especially with the web), and are enamored with statistically salient generated arbitrary content. https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Dev...
- vlovich123 10mo ago
  C is simply unforgiving, amateur or not.
  - uecker 10mo ago
    Programming is unforgiving.
- keyle 10mo ago
  What are you actually answering to?
  - Joel_Mckay 10mo ago
    Reply to bypass a nonsense slop-article that doesn't actually offer any legitimate insights into workmanship standards. Follow the 10 rules on the single wiki page, and C becomes a lot less challenging to stabilize. Could also look at why C and Assembly is still used where metastability considerations matter. If you spend your days in user-space Applications, than don't worry about it... A bit of history where these rules came from, and why they matter. =3 "Why Fighter Jets Ban 90% of C++ Features" https://www.youtube.com/watch?v=Gv4sDL9Ljww https://www.youtube.com/watch?v=Gv4sDL9Ljww
  - kubb 10mo ago
    I agree, seems off topic but let’s be kind.
    - Joel_Mckay 10mo ago
      The basis of the cited 10 rules helped form many standards for reliable code: https://www.stroustrup.com/JSF-AV-rules.pdf https://www.stroustrup.com/JSF-AV-rules.pdf Best of luck =3
    - keyle 10mo ago
      Is the use of "actually" wrong here? What part of my question was not kind?

by keyle 10mo ago

Joel_Mckay 10mo ago

Languages like C are simply very unforgiving to amateurs, and naive arbitrary code generators. Bad workmanship writes bad code in any language. Typically the "easier" the compiler is to use... the more complex the failure mode. =3 Vibe coders usually offer zero workmanship (especially with the web), and are enamored with statistically salient generated arbitrary content. https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Dev...

vlovich123 10mo ago
C is simply unforgiving, amateur or not.
- uecker 10mo ago
  Programming is unforgiving.
keyle 10mo ago
What are you actually answering to?
- Joel_Mckay 10mo ago
  Reply to bypass a nonsense slop-article that doesn't actually offer any legitimate insights into workmanship standards. Follow the 10 rules on the single wiki page, and C becomes a lot less challenging to stabilize. Could also look at why C and Assembly is still used where metastability considerations matter. If you spend your days in user-space Applications, than don't worry about it... A bit of history where these rules came from, and why they matter. =3 "Why Fighter Jets Ban 90% of C++ Features" https://www.youtube.com/watch?v=Gv4sDL9Ljww https://www.youtube.com/watch?v=Gv4sDL9Ljww
- kubb 10mo ago
  I agree, seems off topic but let’s be kind.
  - Joel_Mckay 10mo ago
    The basis of the cited 10 rules helped form many standards for reliable code: https://www.stroustrup.com/JSF-AV-rules.pdf https://www.stroustrup.com/JSF-AV-rules.pdf Best of luck =3
  - keyle 10mo ago
    Is the use of "actually" wrong here? What part of my question was not kind?