Feelin' Groovy: A Groovy Developer in the Java World
•
0 likes•157 views
Keynote given at Gr8conf.in, Delhi, India, January 2017. Variation of same keynote given at Gr8conf.eu in Copenhagen (https://www.youtube.com/watch?v=KZ7u8CddgnI) and Gr8conf.us in Minneapolis, earlier in 2016
Recommended
More Related Content
Similar to Feelin' Groovy: A Groovy Developer in the Java World
Similar to Feelin' Groovy: A Groovy Developer in the Java World (20)
Recently uploaded
Recently uploaded (20)
Feelin' Groovy: A Groovy Developer in the Java World
- 1. Feelin' Groovy A Groovy Developer in the Java World
- 2. Contact Info Ken Kousen Kousen IT, Inc. ken.kousen@kousenit.com http://www.kousenit.com http://kousenit.wordpress.com (blog) @kenkousen Groovy Podcast: http://nofluffjuststuff.com/groovypodcast O'Reilly videos: http://search.oreilly.com/?q=kousen&x=0&y=0
- 3. A note about the US Elections...
- 4. A note about the US Elections... I'm sorry
- 5. A note about the US Elections... Anybody hiring?
- 12. Pierre-Simon Laplace 1749 - 1827
- 14. Patent Trolls
- 18. What I use to sell Groovy to Java devs: - Groovy JDK Why Use Groovy?
- 22. (Thanks to Soren Glasius)
- 24. Even better, move to Geb See gr8conf_geb.groovy … (also build.gradle and GebConfig.groovy)
- 25. What I use to sell Groovy to Java devs: - Groovy JDK - Native syntax for collections Why Use Groovy?
- 27. What I use to sell Groovy to Java devs: - Groovy JDK - Native syntax for collections - POGOs Why Use Groovy?
- 29. What I use to sell Groovy to Java devs: - Groovy JDK - Native syntax for collections - POGOs - AST transformations Why Use Groovy?
- 31. What I use to sell Groovy to Java devs: - Groovy JDK - Native syntax for collections - POGOs - AST transformations - Safe navigation operator Why Use Groovy?
- 33. What I use to sell Groovy to Java devs: - Groovy JDK - Native syntax for collections - POGOs - AST transformations - Safe navigation operator - Slurpers and Builders (XML and JSON) Why Use Groovy?
- 36. What I use to sell Groovy to Java devs: - Groovy JDK - Native syntax for collections - POGOs - AST transformations - Safe navigation operator - Slurpers and Builders (XML and JSON) - Metaprogramming Why Use Groovy?
- 37. Remember the Date calculation? What about Java 8? java.time.LocalDate doesn't have the same minus method Easy enough to fix with Groovy metaprogramming
- 39. Source Code All these examples hosted at: https://github.com/kousen/keynote
- 40. How popular is Groovy?
- 42. TIOBE Data December, 2016 (http://www.tiobe.com/tiobe-index/) 1 Java 17.856% 19 Groovy 1.786% 32 Scala 0.689% 50 Clojure 0.183% (Note: Kotlin in "next 50")
- 43. StackOverflow Developer Survey Most Popular Technologies - Used Java 36.3% Groovy 0.34% Kotlin 0.12% Scala, Clojure not listed
- 45. Why Use Grails? Grails 3
- 46. Why Use Grails? Grails 3 - Uses Gradle
- 47. Why Use Grails? Grails 3 - Uses Gradle - Cool profiles: REST, Angular, …
- 48. Why Use Grails? Grails 3 - Uses Gradle - Cool profiles: REST, Angular, … - One word: RxGORM - Part of GORM 6 (!) in Grails 3.2
- 49. Why Use Gradle? Definitive build tool in the open source world
- 50. Why Use Gradle? Definitive build tool in the open source world Rapidly growing adoption in industry
- 51. Why Use Gradle? Definitive build tool in the open source world Rapidly growing adoption in industry Lots of people seriously loathe Maven
- 53. Perception End of Pivotal support means end of Groovy and Grails
- 54. Reality Six Pivotal employees affected Three Groovy Three Grails
- 55. Reality Six Pivotal employees affected Three Groovy Three Grails All were successfully employed soon afterwards
- 56. Reality Gradle, Inc increased hiring
- 57. Reality Groovy moved to Apache Apache Groovy, top level project, Nov 2015
- 59. Reality Grails moved to OCI Does more to support Grails than Pivotal ever did
- 60. One other unfortunate side effect…
- 62. Reality Inside Groovy community: Short term uncertainty, but we're okay
- 63. How do we fight the perception problem?
- 64. How do we fight the perception problem? Groovy Point to Apache Project Downloads have steadily increased
- 66. How do we fight the perception problem? What about Grails? OCI blog
- 68. How do we fight the perception problem? What about Grails? OCI blog Grails Quickcasts
- 70. How do we fight the perception problem? What about Grails? OCI blog Grails Quickcasts Grails Slack channel
- 72. Perception "Our company decided to use Spring Boot instead of Grails"
- 73. Reality Everything in Spring Boot is in Grails
- 74. Reality Everything in Spring Boot is in Grails This includes the Spring Boot actuator → profiling and administration
- 75. Reality Everything in Spring Boot is in Grails This includes the Spring Boot actuator → profiling and administration Grails adds convenience, capabilities, and customization to Spring Boot
- 76. Reality Spring Boot is Grails Lite
- 77. Maybe Grails needs rebranding... Grails Boot
- 78. Das Boot
- 79. Or maybe even... Holy Grails S
- 80. Objections Common objections to Groovy-related projects
- 82. Response @CompileStatic Works on classes and methods
- 83. What about the elephant in the room...
- 85. Now we know why that Gradlephant looks so grumpy…
- 87. IDE Support IDE support is the real issue Static typing makes IntelliJ IDEA work better
- 88. Who wins when Gradle supports Kotlin? Clear winners: - JetBrains - Kotlin developers
- 89. Who loses when Gradle supports Kotlin? Groovy, because fewer developers come into the field Internally, we're fine Externally, we have a perception problem "Gradle adopted Kotlin because of problems with Groovy"
- 90. What about Gradle, Inc? This is a big gamble for them - Kotlin is still very new
- 91. What about Gradle, Inc? This is a big gamble for them - Kotlin is still very new - What about all those existing build files that use Groovy?
- 92. What about Gradle, Inc? This is a big gamble for them - Kotlin is still very new - What about all those existing build files that use Groovy? - Groovy is great at DSL's
- 93. What about Gradle, Inc? This is a big gamble for them - Kotlin is still very new - What about all those existing build files that use Groovy? - Groovy is great at DSL's - Still need Eclipse support (JetBrains says they'll do it, but whoa)
- 94. What about Gradle, Inc? This is a big gamble for them - Kotlin is still very new - What about all those existing build files that use Groovy? - Groovy is great at DSL's - Still need Eclipse support (JetBrains) Time will tell whether or not this was a good idea
- 97. Groovy's Biggest Strength The Community
- 99. The Groovy Community In Groovy-related projects Experienced devs are friendly and helpful
- 100. The Groovy Community This flows from the top I could add a dozen more easily …
- 101. The Groovy Community Often your greatest strength is also your biggest weakness
- 102. The Groovy Community Often your greatest strength is also your biggest weakness Maybe our leaders are TOO humble
- 103. The Groovy Community That's where we can help →
- 104. The Groovy Community That's where we can help → Tell other devs about your Groovy experiences
- 105. Bottom Line Groovy, Grails, Gradle, Ratpack, Griffon, Spock, Geb, …
- 106. Bottom Line Groovy, Grails, Gradle, Ratpack, Griffon, Spock, Geb, … All healthy, powerful, successful, mature technologies
- 107. Groovy, Grails, Gradle, Ratpack, Griffon, Spock, Geb, … All healthy, powerful, successful, mature technologies Our problems are perception, not reality Bottom Line
- 108. Bottom Line Groovy, Grails, Gradle, Ratpack, Griffon, Spock, Geb, … All healthy, powerful, successful, mature technologies Our problems are perception, not reality So go tell everybody, and become your own …
- 109. Groovy Evangelist
- 110. Thanks! Thank you for coming and Enjoy the rest of Gr8conf!