home.social

Search

247 results for “ApacheGroovy”

  1. Alguien se ha leído las pildoras #ApacheGroovy y encima le ha servido para algo!!
  2. Ahora ya puedes suscribirte al RSS de píldoras #ApacheGroovy gracias a que le he metido un generador de rss ... hecho en ApacheGroovy, cómo no!!!


    https://groovy.es/rss.xml
  3. Ahora ya puedes suscribirte al RSS de píldoras #ApacheGroovy gracias a que le he metido un generador de rss ... hecho en ApacheGroovy, cómo no!!!


    https://groovy.es/rss.xml
  4. Ahora ya puedes suscribirte al RSS de píldoras #ApacheGroovy gracias a que le he metido un generador de rss ... hecho en ApacheGroovy, cómo no!!!


    https://groovy.es/rss.xml
  5. Buenos días, ya está disponible la segunda #ApacheGroovy píldora, esta vez dedicada a GString

    Oro parece una cadena no es, qué es?

    https://groovy.es/w/gstring.html
  6. Buenos días, ya está disponible la segunda #ApacheGroovy píldora, esta vez dedicada a GString

    Oro parece una cadena no es, qué es?

    https://groovy.es/w/gstring.html
  7. Segunda entrega de las #GroovyScripts píldoras

    Aún tengo que encontrar el mejor formato, pero allá va la segunda entrega de píldoras con #ApacheGroovy

    Jugando con String y GString

    https://groovyconsole.dev/?gist=de2ddf7272128061067bc3547ec46627
  8. Segunda entrega de las #GroovyScripts píldoras

    Aún tengo que encontrar el mejor formato, pero allá va la segunda entrega de píldoras con #ApacheGroovy

    Jugando con String y GString

    https://groovyconsole.dev/?gist=de2ddf7272128061067bc3547ec46627
  9. 📢 Did you know you can write & run some #ApacheGroovy code online ❓

    groovyconsole.dev

    Code on #Github
    github.com/groovy-console/groo

    ▶️ Frontend: Google #AppEngine
    ▶️ Groovy runtime runners: Google #CloudFunction

    You can also run your #SpockFramework tests!

    🖖 Test often & prosper! 🖖

  10. 📢 Did you know you can write & run some #ApacheGroovy code online ❓

    groovyconsole.dev

    Code on #Github
    github.com/groovy-console/groo

    ▶️ Frontend: Google #AppEngine
    ▶️ Groovy runtime runners: Google #CloudFunction

    You can also run your #SpockFramework tests!

    🖖 Test often & prosper! 🖖

  11. 📢 Did you know you can write & run some #ApacheGroovy code online ❓

    groovyconsole.dev

    Code on #Github
    github.com/groovy-console/groo

    ▶️ Frontend: Google #AppEngine
    ▶️ Groovy runtime runners: Google #CloudFunction

    You can also run your #SpockFramework tests!

    🖖 Test often & prosper! 🖖

  12. 📢 Did you know you can write & run some #ApacheGroovy code online ❓

    groovyconsole.dev

    Code on #Github
    github.com/groovy-console/groo

    ▶️ Frontend: Google #AppEngine
    ▶️ Groovy runtime runners: Google #CloudFunction

    You can also run your #SpockFramework tests!

    🖖 Test often & prosper! 🖖

  13. No matter which programming language you choose, understanding & using strings effectively will significantly enhance your ability to handle textual data and take your coding skills to new heights! opensource.net/how-groovy-work #ApacheGroovy

  14. No matter which programming language you choose, understanding & using strings effectively will significantly enhance your ability to handle textual data and take your coding skills to new heights! opensource.net/how-groovy-work #ApacheGroovy

  15. From Boring to Brilliant: Transforming Strings with #ApacheGroovyhttps://opensource.net/advanced-strings-apache-groovy-10/ ?utm_source=social&utm_medium=mastodon #OpenSource

  16. From Boring to Brilliant: Transforming Strings with #ApacheGroovyhttps://opensource.net/advanced-strings-apache-groovy-10/ ?utm_source=social&utm_medium=mastodon #OpenSource

  17. @StrangeNoises In the existing lambda approach, the $ sign is just the name of the variable. It's an allowed identified.

    Coming from a #ApacheGroovy background, I often used closures like you say with some kind of factory method. That makes sense.

    In my approach, what I like is that I don't expose the internals. So I keep control. A user can't really mess up with his own lambda.

  18. @StrangeNoises In the existing lambda approach, the $ sign is just the name of the variable. It's an allowed identified.

    Coming from a #ApacheGroovy background, I often used closures like you say with some kind of factory method. That makes sense.

    In my approach, what I like is that I don't expose the internals. So I keep control. A user can't really mess up with his own lambda.