java vs javascript (xpages)

31
MWLUG 2014 Java versus JavaScript: There really is no competition Andrew Barickman – PSC Group LLC

Upload: andrew-barickman

Post on 10-Dec-2014

336 views

Category:

Technology


5 download

DESCRIPTION

Should you use Java or JavaScript to write XPages applications? The answer is yes. XPages facilitates creating great applications written almost entirely in Java and written almost entirely in JavaScript. There are no right or wrong answers, only circumstances and ramifications. The determining factors as what is best for your development team are many and complex. In this presentation Andrew will seek to dispel the myth that there is even a competition. The answer should always be - it depends. Come and see the session and make your own mind up.

TRANSCRIPT

Page 1: Java vs javascript (XPages)

MWLUG 2014

Java versus JavaScript: There really is no competition

Andrew Barickman – PSC Group LLC

Page 2: Java vs javascript (XPages)

About

Practice LeaderChicago Illinois

@ajbarickman

[email protected]

• 20 Years in IBM delivery

• Delivery

• Management

• Sales Support

• Technical Direction

Page 3: Java vs javascript (XPages)
Page 4: Java vs javascript (XPages)

Our Partners

Page 5: Java vs javascript (XPages)

Application Modernization with PSC

PSC views the process of modernizing application platforms from a holistic, enterprise perspective. Building from our Hub Services, our AMC provides extensive services in each of three critical areas – providing our clients with a 360o View of the process.

Page 6: Java vs javascript (XPages)
Page 7: Java vs javascript (XPages)

Introduction

• What this session is NOT– Deep technical explanations of how each works– The proclamation of which is better

• What can we agree upon– Both are important to developing cutting edge, elegant,

maintainable applications– Where possible everyone should strive to be proficient with

both

• Thing look different depending on who you are– End Users– Developers– Management

Page 8: Java vs javascript (XPages)

Introduction

JavaScript• Server and Client Side

Language• Used for both UI and core

business logic

Java• Server side language• Primarily used for core

business logic

Page 9: Java vs javascript (XPages)

If I am an End Users

End users want their applications to be:• Elegant• Beautiful• It just works• As far as technology goes…

It is irrelevant

Page 10: Java vs javascript (XPages)

Developers

All time is an investment and comes at the cost of something else you could be learning, therefore don’t waste it.

What should I invest in (first)?

Page 11: Java vs javascript (XPages)

Developers

Popularity

Courtesy of LangPop.com

Page 12: Java vs javascript (XPages)

Who needs Java?

What type of development do you do?

http://www.wissel.net/blog/d6plinks/SHWL-8HHABV

Page 13: Java vs javascript (XPages)

Developers

Why Java over JavaScript?– Programming model in the rest of the

ICS portfolio– You can do things you cannot do with

SSJS. Closer to the core– Open the whole world of Java to you– Code separation– Reusability– Maintainability

Friday 11:30amAD106: Don't fall asleep using Relational Databases: Using Hibernate with

XPages – Toby Samples PSC

Page 14: Java vs javascript (XPages)

Developers

Why JavaScript over Java?– Elegant, beautiful user experiences delight your

users– Client side development versus server side

development

Page 15: Java vs javascript (XPages)

Server side development

Server side components render client side

Page 16: Java vs javascript (XPages)

Core Controls – Standard XPages

Page 17: Java vs javascript (XPages)

New XPages

“XPages is a first class web development platform with benefits”

Page 18: Java vs javascript (XPages)

New XPages

Which would your users rather use?

Page 19: Java vs javascript (XPages)

Client Side Development

Build the best user experience and tie ittogether with the power of Domino

Ajax

Page 20: Java vs javascript (XPages)

Client Side Development

The rise of client side development and JavaScript MVC frameworks

Friday 3pmOS102: Write once, run anywhere - Angular.js in XPages – Mark Roden PSC

Page 21: Java vs javascript (XPages)
Page 22: Java vs javascript (XPages)
Page 23: Java vs javascript (XPages)
Page 24: Java vs javascript (XPages)
Page 25: Java vs javascript (XPages)

Management

• Application development managers must consider the composite skill set of the team

• What is the make up of your current team?

• Do you have classic Notes client developers?

Page 26: Java vs javascript (XPages)

Classic Notes Developers

• Non CS Major• Does not understand

Object Oriented design concepts

• Procedural programmer• Good at solving business

problems not architectural problems

Recommendation: Start with JavaScript add Java later

Page 27: Java vs javascript (XPages)

Case Study #1

What Mergers and Acquisition knowledge management system

WhyPortability, POI, Speed, Supportable by internal staff

HowAngular.js, POI, Custom Java REST Services, Almost No SSJS

Very Large International Professional Services Firm

Page 28: Java vs javascript (XPages)

Case Study #2

What Project Management Portal

WhyNo Java skills internally, supportable by standard Notes devs

HowCustom UI based on XPages control, SSJS, LotusScript

Large Commercial Construction Company

Page 29: Java vs javascript (XPages)

Case Study #3

What Managed resource management and time tracking

WhyNo Java skills internally, supportable by standard Domino web devs

HowMostly SSJS with a lot of front end JavaScript and responsive design

Staffing and Placement Company

Page 30: Java vs javascript (XPages)

Parting Advice– I’m new to XPages and boy there is a lot to learn

• Focus on JavaScript– I’m a CS major and comfortable with Java

• Focus on JavaScript– I’m a longtime XPages programmer and I am writing

kick butt applications without a single line of Java• Learn Java

– I’m a really good web developer just starting with XPages• Learn Java

Page 31: Java vs javascript (XPages)

Questions?

Questions?