If Only Brendan Eich Had One More Day

The pinnacle of error handling right here! This dev just casually commented out the error handling with // I missed the part where that's my problem in a webhook function. Sure, let the API call fail silently in production - what could possibly go wrong? Just yeet that error into the void and let future-you (or some poor on-call engineer at 2AM) deal with the consequences when customers start complaining. Classic "works on my machine" energy. The Spider-Man reference makes it even more perfect - with great code comes absolutely zero responsibility, apparently!

Content You shouldn't use client javascript to access databases for several reasons (bad practice, security issues, etc) but if you really want to do this, here is an example: 748 var connection new Activexobject ("ADODB .Connection") ; var connectionstring "Data Source server; Initial Catalogcatalog ;User IDuser; Password connection. Open (connectionstring); new ActiveXObject ("ADODB. Recordset"); rs. Open ("SELECT FROM table", connection); rs.MoveFirst while(!rs.eof) document.writers.fields (1)); rs.movenext; rs. close; connection. close; A better way to connect to a sql server would be to use some server side language like PHP, Java, NET, among others. Client javascript should be used only for the interfaces. And there are rumors of an ancient legend about the existence of server javascript, but this is another story. ;) Share Edit Follow Flag edited Jun 24 '09 at 13:27 answered May 13 09 at 12:29 Fabio Vinicius Binder 12.5k 4 30 32

Content HTML CSS JavaScript Data Structures Algorithms

Content Spider-Man is wrong Lisa Simpson is right JavaScript Application too much recursion

Content THE SCENT OF ROSEMARY HELPS INCREASE MEMORY SV3A

Content C DateTime. ToStringO PHP DateTime:formato JavaScript Date. tolSOStringO splitTiol