Skip to main content

Home/ Coders/ Group items tagged closure

Rss Feed Group items tagged

Fabien Cadet

Gotcha: Python, scoping, and closures - fuzzy notepad, 2011-04 - 9 views

  •  
    Pakistani Escorts In Dubai // Model Escort In Dubai // Pakistani Call Girls In Dubai // Female Escort In Dubai // Indian Pakistani Escort In Dubai // Indian Escorts In Dubai / Indian Call Girls In Dubai // Dubai Escort In Dubai // Arab Escort In Dubai // Indian Massage Escort In Dubai // Pakistani Massage Escort In Dubai // Indian Escorts //
anonymous

Closure Tools - Google Code - 4 views

  •  
    Google's JavaScript library and tools
Fabien Cadet

Service Oriented Agony | 8th Light, 2012-02-01 by Bob Martin - 7 views

  • The structure seems obvious to system designers who have grown tired of single monolithic systems and want to break those systems up into components and services. What could be more natural than to break the system along the lines of data base managment?
  • Unfortunately this is a huge violation of the Single Responsibility Principle — or its big brother the Common Closure Principle.
  • These principles tell us to group together things that change together, and keep apart things that change for different reasons.
  • ...6 more annotations...
  • When you separate things that change for the same reasons, you have to make changes in many different places in the system.
  • So it’s a lot of work just to get anything working.
  • Moreover, when you group together things that change for different reasons, you expose the components of the system to collateral damage, thrashing, CM collisions, and a whole host of other problems.
  • So what’s the solution? First of all, I question whether the system needed to be partitioned into services.
  • Services are expensive and complicated, you should only create them if you absolutely need to. It’s always easier to live in a single process. Remember Martin Fowler’s first law of distributed objects: Don’t distribute your objects.
  • Many systems could be streamlined, and development made much faster, if the system designers paid more attention to the Single Responsibility Principle.
David Corking

JavaScript as a Functional Language | Ajaxonomy | 2009 - 0 views

  • there is a little bit of hand-waving involved in calling JavaScript a functional language. JavaScript is not a side-effect free language, nor is it an expression-based language (i.e., it is not value-oriented, but rather variable-oriented). There is no tail call optimization in any of the current implementations, so recursion must be kept shallow. And the list goes on. Truth be told, JavaScript is really one of the first hybrid imperative-functional languages.
  • Higher-order functions allow us to do functional composition,
  • Since JavaScript does not have "overloaded" functions, this type of functionality is usually simulated using manipulation of the function's arguments. Currying comes in handy because it allows you to do this manipulation in a much cleaner and more modular way.
  • ...1 more annotation...
  • Closures have quite a few applications in real-world JavaScript: event binding, callbacks, sorting, mapping (in the classical Lisp sense), and many others. In more modern JavaScript programming, you can find them almost everywhere.
  •  
    This is a short tutorial approach to an old but little-noticed saw.
David Corking

Remember Smalltalk? | Gartner Blogs 2008 - 1 views

  • 2) If you are BIG fan of dynamics languages (closures, meta programming, and all that cool stuff) then consider giving Smalltalk a look.  You might like what you see.  Its like Ruby but with bigger muscles.  You think Rails is cool? Check out seaside. In the end we’ll see a up tick in Smalltalk momentum over the next few years. 
  • Please don’t talk about Smalltalk. I enjoy my competitive advantage over the Java/NET crowd
  • Where Smalltalk really shines recently is in field of web applications due to its dynamic nature (live upgrading, debugging etc.) and because its shortcoming are not relevant here.
  • ...9 more annotations...
  • On the Desktop - Dolphin creates 500k exe’s with ease - its a 1 button click (you just have to follow some of their easy put things in packages rules).
  • Remember LAN MAN? OS2? Both were heavily endorsed by Gartner.
  • I laugh when people say poor performance on older hardware was a mjor Smalltalk weakness. We routinely delivered applications that ran on 386 and 68020 processors with 8MB RAM. And yes, they were quite snappy. No, the reason Smalltalk didn’t catch on is because Sun spent more money on Java marketing than was spent on all computer languages combined, since the dawn of time.
  • I’ve listened personally to whiny ROR programmers groan and whine about PHP devs LEARNING ROR and undercutting them.
  • I didn’t fall for it for the marketing. I fell for WORA, for the language/runtime separation, for the multi-vendor approach (Sun never wanted to be the single provider for any Java centric product niche, and in fact was never the leader), for the comprehensive set of vendor-neutral APIs for all sorts of execution environments/applications,
  • For now I would like to see more use of Smalltalk like constructs in Java (Groovy).
  • Smalltalk must have sofisticated CASE tools, business process simulation tools, large development environments etc. etc. etc.
  • I stayed to teach Smalltalk since 1993 and am very happy about this information. Each academic year, we produce a small group of new Smalltalkers in the Czech Republic.
  • Joe Barnhart // Apr 4, 2009 at 2:48 pm At the company where I work, we have used Smalltalk for 19 years. Our tiny team of programmers has beat the pants off of competitors who employ teams 100 times our size.
  •  
    trend spotting
1 - 7 of 7
Showing 20 items per page