<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Nice.</div><div><br></div><div>I give the client the git repo and the source code in PDF format now.</div><div><br></div><div>I seem to me moving in the direction of embedded+mobile+desktop integrations, and less data centery stuff. Honestly useful because more of my work becomes visible to the wives and this means at they have an idea of what I'm doing more than "some invisible system somewhere".</div><div><br></div><div>Even on mobile, though, I prefer the use of native code to managed runtime solutions. I will use a managed runtime if I must, but I really do prefer to be able to explain every single line of code in terms of what exactly it makes the machine do.</div><div><br></div><div>It is virtually impossible to get that kind of understanding in any scripting language. Semantics can be explained, sure, but Python release x and x+1 will often create different machine instructions for the same code.</div><div><br></div><div>Vulnerabilities and thus exploits come from lack of understanding, laziness, or both. It is much easier for me to prove the functionality of my code compiled directly to x86 or ARM assembly, than to prove the same for a script, since I don't have to assume or prove that e.g., Python is securely doing what I told it to do.</div><div><br>Sent from my iPad</div><div><br>On Aug 6, 2015, at 8:33 AM, Chris Fowler <<a href="mailto:cfowler@outpostsentinel.com">cfowler@outpostsentinel.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Michael B. Trausch" <<a href="mailto:mike@trausch.us">mike@trausch.us</a>><br><b>To: </b><a href="mailto:ale@ale.org">ale@ale.org</a><br><b>Sent: </b>Wednesday, August 5, 2015 11:50:45 PM<br><b>Subject: </b>Re: [ale] Ruby vs C, a non-technical chat<br><div><br></div><div></div><div>I like to write the heavy lifting in C++, and then use SWIG to generate the API for prototyping/automation/testing/etc., which keeps all the doors open anyway. Static C++ code is easier to support when you're not the one with the hands on the system, too. It's just amazing how many "IT professionals" will completely screw up your scripting code for no other reason than they could read it and they thought they could solve their problem without calling you, but they only made it worse instead, and they broke the system's remote access, and... well, you don't see IT n00bs really messing with ELF files all that much.</div></blockquote><div><br></div><div>They don't touch my stuff. They only get to run it. Sometimes I may even run it through Acme::EyeDrops to so that they really can't touch it. No one sees my code. My goal is to use Linux to deliver a system to those that do not need to know Linux. I could be the only Linux system in your Windows shop. </div><div><br></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Ale mailing list</span><br><span><a href="mailto:Ale@ale.org">Ale@ale.org</a></span><br><span><a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a></span><br><span>See JOBS, ANNOUNCE and SCHOOLS lists at</span><br><span><a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a></span><br></div></blockquote></body></html>