- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Unrelated: Late 1970's into the 1980's developed a custom language for military embedded systems (but used for other things, and almost bought by Tektronix!] it too concepts from Simula, SmallTalk and others... Now what we were doing (real time constraints and all) was not the message passing of the day....so we didnt have "objects", but we had actions and things, and of course they became known as thingies.... I wonder if any of those systems are still in use....
Admin
array.map(func).includes(true)is an inefficient way to doarray.some(func). But if you're going to do a wasteful_.isEqual(), why not go all out on the worst ways to do things?Admin
This widget has exactly the same shape… as a thingie! A great big thingie! It was terrific.
Admin
That all looks very Java to me :-)
Admin
I'm currently in the middle of some really fun dirty-checking that uses _.isEqual. It's almost reasonable... almost. But if the back end has a null while the front end has an undefined, it doesn't matter that both values are "do nothing", _.isEqual will declare they're not the same. So I'm writing code to drop nil values, and clean up other things, and it's enough that I'm starting to think I should just write what I should have written the first time: a bunch of property-by-property comparison code.