Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re: RFC: PDL Cheat Sheet

by BrowserUk (Pope)
on Jan 03, 2007 at 11:49 UTC ( #592746=note: print w/replies, xml ) Need Help??


in reply to RFC: PDL Cheat Sheet

This looks (after a minimal and superficial scan) extremely useful. Many thanks for producing this.

PDL is one of those modules that I have had several half hearted attempts at getting to grips with. A lack of a real need to do so, and many other interesting problems with which to occupy my mind that have less steep learning curves or more immediate satisfaction criteria mean that I have yet to make any real in roads to its possibilities.

This may just reduce the gradient of the learning curve, or facilitate such, that I actually use it to solve or progress one of the many stalled projects sitting on my back boiler.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^2: RFC: PDL Cheat Sheet
by lin0 (Curate) on Jan 04, 2007 at 05:25 UTC

    Hi BrowserUk

    I am glad you think you can use this "cheat sheet" :-)

    I completely agree with you in that PDL has a steep learning curve. This is why, I am preparing a set of tutorials to help people getting started with it. So, please, keep an eye open that more tutorials are forthcoming :-)

    Cheers,

    lin0

      You know, looking back at some of my attempts at using PDL, a simple tie interface wrapper that allows you to treat piddles as normal arrays would greatly reduce the gradient?

      I realise that it probably wouldn't be as efficient, but it might allow an easier start and once you get stuff going, it should be fairly 'algorithmic' to convert it back to native calls to squeeze out that last ounze of performance.

      Anyway, I'll keep my eyes open for the tutorials. Thanks again.


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://592746]
help
Chatterbox?
[Corion]: Once more, I'm looking for a sane client-side framework, but I guess these don't exist. Everything I look at either uses a weirdo home-grown templating language (like Angular in all its incarnations) or uses weirdo Javascript incarnations (like ...
[Corion]: ... Inferno.js, which uses ES2015) or uses some horrible amount of Javascript infrastructure before you can even render a single file.
[Corion]: I'd really like to create a dynamic frontend for my Google Keep clone, but so far, all the templating solutions seem to bring their own template language or require me to hand-code everything in (their own flavour of) Javascript. I'd like something ...
[Corion]: ... that can use templates from the HTML (via <script language="text/ template">... my template ...</script> and otherwise gets out of my way. But it seems that is not how the Javascript world is, currently :-/
[Corion]: I guess my question is, has anybody worked with React, Ember, Angular (v2, v4, v.whatever) or any other JS client-side dynamic rendering/virtual DOM thingie and found a simple, single-file solution like jQuery?

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (12)
As of 2017-03-27 19:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Should Pluto Get Its Planethood Back?



    Results (321 votes). Check out past polls.