Clojure for Java (OOPS) programmers

Feb 2020

10 Mon

11 Tue

12 Wed

13 Thu

14 Fri 09:30 AM – 09:00 PM IST

15 Sat 08:45 AM – 06:00 PM IST

16 Sun

Make a submission

Accepting submissions till 20 Jan 2020, 11:59 PM

Novotel Pune Nagar Road, Crimson Hall, Pune

Tickets

IN/Clojure 2020 is the 4th edition of India’s annual Clojure and ClojureScript conference. Follow twitter.com/in_clojure for updates.

Backstory

We began in Pune in 2016 and after two editions in namma Bengaluru, we’re delighted to come full circle back to apla Pune (and all those delicious bakarwadis and modaks).

As India’s premiere Clojure and ClojureScript conference, we strive to facilitate the free exchange of ideas between new and experienced programmers alike.

Over the years, IN/Clojure has served as a platform to kickstart a series of Clojure workshops and meet-ups across the country. And it has helped attendees make a strong case for Clojure, and Clojurescript adoption in their companies.

We believe that this edition of the conference, like previous editions will foster the growing Clojure community in Asia.

Who should attend?

Whether you are knee-deep writing macros that write macros, or struggling to escape the beginner’s plateau, or wondering if/why/how to adopt Clojure in your organization, or are in it purely for the joy of learning, IN/Clojure is the event bringing together a great mix of Clojure/Script masters, practitioners, and newcomers from across India and beyond.

Why Attend?

We welcome you to join nearly 149 other people and...

Speak: CFP is open till 20 Jan 2020.
Learn: We run two all-day hands-on Clojure workshops. Check 'em out here.
Converse: Derive some sweet cerebral expansion from the talks, the tweetstorms, and the “hallway tracks”.
Inspire: Trade notes, ideas, tools, and techniques with new and experienced Clojure programmers alike (photostream).
Be Inspired : Start that project, that meetup, that hack night, that business, that beautiful work of art.
Sponsor: Help foster the growing Clojure and FP community in India/Asia.
Network: Meet seasoned practitioners and awesome sponsors (listed below). Hire or get hired. Acquire or get acquired ;-)
Grab: Some cool swag, and some fun swag, and some zany swag.
Party: Eat, drink, and make merry with some of the nicest people around.

Plus, this year we enjoy the company of the perennially effervescent Bozhidar Batsov; prolific Clojurist, Emacs fanatic, maintainer of CIDER, and Lisp hacker extraordinaire.

(Oh, and tickets are going, going, going... grab yours while stocks last.)

#Sponsors:

Click here to view the Sponsorship Deck.

IN/Clojure 2020 Sponsors:

#Platinum Sponsor

#Gold Sponsor

#Bronze Sponsor

#Community Sponsor

#Speaker travel support

Hosted by

IN/Clojure

IN/Clojure is India’s annual Clojure and ClojureScript conference, including talks about features, libraries, tools, usage, and more. IN/Clojure 2020, our 4th edition, is happening on 14th and 15th Feb 2020 (Fri/Sat) in Pune, Maharashtra. more

All submissions

Previous Next

This submission has been added to the schedule

Clojure for Java (OOPS) programmers

Submitted Jan 20, 2020

🌑 Submission Type: Full (40 minutes)

‘legacy’ OOPS programmers vs ‘current’ functional programmers - people find it hard to go from one to the other
Intent is to explain the differences and make it easier for OOPS programmers to adopt Clojure. We’'ll refrain from comparing which one is better.

Outline

Talk will be presented by Madhu (Clojure programmer) and Rashmi (OOPs turned Clojure programmer)

Discuss the paradigms - Encapsulation of data and methods vs immutable functions acting on input data and outputting new data.

(Examples of a simple java class vs a Clojure function)

Talk about how conditioned OOPs programmers are to classes and objects and at first glance it seems we are adopting a messy world of methods, procedures where there is no control over access to data.

Immutable functions are like mathematical functions unlike the methods, procedures of other programming languages.

For an OOPS programmer lack of classes meaning lack of structured code - namespaces in Clojure allow for structuring code.

OOPS requires management of references, their state change, it’s important to follow best practices to control the state change. References also lead to null objects.
Immutable functions get rid of references, explain persistent data structures for how copies of objects are avoided in Clojure.

Clojure - built on Java and uses the Lisp paradigm
All underlyng Java functionality is available. at the same time the Lisp paradigm enables immutability of code.
(Give examples of calling a String function the Java way and the Clojure way)

Seq vs Iterator - Seq follows the interface pattern, mostly all Clojure collections provide the ISeq interface. Stateless compared to Java.

Defprotocol, defmethod - Underlying OOPs polymorphism concept, how the lisp paradigm makes it immutable. (Give examples of Java and Clojure)

Clojure allows mutable state using a few data types -
Atoms - Based on underlying Java atomic variables. Explain.

Clojure - Ease of making changes by generating JAVA bytecode and testing.

Conclusion - Possible to have redundant code, not follow best practices in both Java and Clojure.

Speaker bio

Madhuparna is a senior developer at Quintype, she builds digital tools for media publishers. She loves working on backend and frontend technologies, she mostly spends time working with Clojure, NodeJS and Javascript.

Rashmi has over 20 years of experience in product development in various verticals including 15 years in the Silicon Valley where she primarily worked at Adobe Systems on products like Adobe Illustrator, HTML5 animation and Video Publishing. She is currently the Vice President of Engineering at Quintype.