FACEBOOK RELAY JAVASCRIPT FRAMEWORK SIMPLIFIES API

Facebook has reconstructed its  Relay JavaScript framework for building data-pushed purposes for more uncomplicated use.

Renamed  Relay up to date , the up to date framework features a GraphQL framework incorporating best practices from classic Relay, facebook's native mobile GraphQL purchasers, and the GraphQL group, fb software engineers Lee Byron and Joe Savona said this week.

"Relay up to date retains the perfect elements of Relay—co-located knowledge and examine definitions, declarative data fetching—while additionally simplifying the API, including options, making improvements to efficiency, and lowering the dimensions of the framework," the engineers said. "to perform this, we embraced two ideas: static queries and in advance-of-time optimization."

Developers can use new Relay brand new APIs within the context of present Relay applications thanks to a compatibility API, and Relay has blended fb's React UI library with the GraphQL question language for information-fetching to permit scaling.

GraphQL has been utilized in native iOS and Android apps from fb for the reason that 2012, but facebook's native apps crew had found that it brought the overhead of creating queries via concatenating strings and importing queries over sluggish connections. The staff decided that if GraphQL queries have been statically identified, they will be built as soon as and saved on facebook servers and replaced within the mobile app with a tiny identifier, leading to decreased network visitors and quicker cell app performance.

Relay up to date takes a equivalent method. "The Relay compiler extracts colocated GraphQL snippets from across an app, constructs the important queries, saves them on the server ahead of time and outputs artifacts that the Relay runtime uses to fetch those queries and course of their results at runtime," the engineers stated.

Beforehand-of-time compilation is utilized in Relay up to date, as is rubbish collection. "rubbish assortment is enabled in the core runtime and likewise moderately integrated into the public API in order that developers don't have to explicitly handle cache reminiscence utilization," the engineers mentioned.

At the beginning supposed for constructing apps for the computer, tablets, and different excessive-finish gadgets, Relay has been used for functions starting from net instruments to cellular apps built with  React Native, the facebook engineers stated. previously, Relay was once composed of 1 library, but with Relay modern, it features three, with a compiler, runtime, and React/Relay integration layer. This modularity might permit Relay's use with other view libraries sooner or later or as a standalone library. Relay's compiler is designed so as to add more capabilities in response to GraphQL's sort device or for use for tools past app building.

If programming languages were vehicles:

C was the great all-arounder: compact, powerful, goes everywhere, and reliable in situations where your life depends on it.

                                                                   



C++ is the new C — twice the power, twice the size, works in hostile environments, and if you try to use it without care and special training you will probably crash.

                                                                       



C♯ is C++ with more safety features so that ordinary civilians can use it. It looks kind of silly but it has most of the same power so long as you stay near gas pumps and auto shops and the comforts of civilization. A well-known heavily muscular intimidator keeps touting it.

Java is another attempt to improve on C. It sort of gets the job done, but it's way slower, bulkier, spews pollution everywhere, and people will think you're a redneck.

Python is great for everyday tasks: easy to drive, versatile, comes with all the conveniences built in. It isn't fast or sexy, but neither are your errands.

Perl used to serve the same purpose as Python, but now only bearded ex-hippies use it.

LISP is programming stripped down to the bare essence. It's been around since forever. Using it makes you stronger, but only an athlete or a maniac can make a living with with it.

Haskell is like a hipster version of LISP.

PHP is this hand-me-down deathtrap that you only use because you're stuck with it, and when you hit a speed bump the wrong way it sets you and your passengers on fire.

Go is a shiny new toy that tech nerds say will be the way of the future, but it's only practical if you limit everything you want to do to stay within its range.

COBOL probably seemed like a good idea at the time.

MATLAB is what scientists use to do special scientist things.

R is what scientists use when they can't afford MATLAB.

OCaml is this funny shaped thing that Europeans like for some reason.

This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a freak golf cart.

If you're wondering about this choice of cars, and if they fit the facts; then repeat to yourself 'it's just a j

+Web Solution, Web Design and development Company, India 

JavaOne: Java EE 8 Release Pushed to 2017

The annual Java One conference kicked off on Sunday with a keynote confirmation of the widely expected delay of the release of Java EE 8. Anil Gaur, Oracle Corp. group vice president of engineering with responsibility for Java EE and WebLogic Server, laid out the proposed roadmap for the next version of the enterprise Java platform during the opening keynote presentation on Monday.

According that roadmap, Java EE 8 will be ready by the end of 2017, and Java EE 9 will be ready sometime in 2018.

"Java EE has been the platform of choice for developing and deploying enterprise applications for many years," Gaur told conference attendees. "It provides a very comprehensive set of APIs for applications that require scalable, transactional security. I am pleased to see EE adopted in clouds, and also to see that many vendors have started to use EE APIs to develop microservices applications. But they are doing so in their own way and, lacking a standard in this space, it's impossible to ensure compatibility and portability."

Gaur said Oracle sees Java EE as the platform for standardizing innovation around enterprise Java, and he emphasized that his company is committed to being part of the future of Java EE.

During a pre-conference interview, Gaur highlighted key areas in which Oracle is investing in enterprise Java, including a new programming model centered around distributed data streams and the reactive style of programming. "This is a way to develop apps that are loosely coupled and distributed," he told ADTmag. He added that Oracle is looking for ways to leverage the type of modularity coming in Java SE 9 in upcoming releases of Java EE.

 The Java EE Roadmap

The Java EE Roadmap (source: Oracle)
"We want to see how we can extend support in packaging, so developers can combine multiple artifacts within the configuration," he said. "These concepts are already there; what we're trying to do is bring them to the platform so people can use them as they move to applications from environment A to environment B."

Supporting things like containerization and reactive programming present challenges for the average developer, Gaur said, which is why Oracle is working to expand Java EE functionality to standardize these practices. He added that Java EE 8 will likely include enhanced Security (secret management, support for Oauth, OpenID), an API for self-contained configuration, and an API for health checks.

"We have started to roll out surveys from the product community," he said. "At the end of the day, it's the community, and the expert group that will finalize the scope."

Earlier this year, a group of volunteers doubting Oracle's commitment to enterprise Java formed the Java EE Guardians. The group has petitioned Oracle execs in an effort to get the company to prioritize the continuing evolution of Java EE.

When asked about the Guardians' efforts, Gaur said, "Our plans are not based on what they are doing, but I look at the positive aspect of what they can bring in. We have been working with open communities -- Java User Groups, Java Champions, etc. -- for a really long time, so I'm sure we'll be able to find a way to collaborate with them."

"The modularity work is challenging and important, and so it is better to do it right than meet a deadline," said IDC analyst Al Hilwa. "Most enterprises wait years to put new versions of Java into production. Still, continuous and agile evolution of Java is key to its long-term dominance as a language. The EE delays are a bit more troublesome, because of the longer time-line, and because there are many competing approaches in architecting new applications. I think integrating support for microservices is an important consideration."

+Web Solution, Web Design and development Company, India




Source taken from: adtmag.com 

The tool has shed its Java dependency in favor of compiling Java source code to JavaScript

Google's Closure compiler, for optimizing and transpling JavaScript, no longer needs Java to run. Instead, Java source code is compiled to JavaScript so it can run under Node.js or in a browser. Java-dependent Closure had been introduced by Google in 2009.

The experimental release detailed this week supports ECMAScript 2015 features like arrow functions and let and const, and it provides polyfills for some ES2015 methods. It will check both syntax and types, and will provision warnings for JavaScript "gotchas." Google cautions, though, that some features are not available, and performance may not equal the Java version.

[ Find out how to get ahead with our career development guide for developers. | The art of programming is changing rapidly. We help you navigate what's hot in programming and what's going cold. | Keep up with hot topics in programming with InfoWorld's Application Development +pnp universe . ]
The upgrade is not a rewrite of Closure in JavaScript. To use the new version, developers should add it as a dependency in a project via NPM, though it also can be used with the Gulp streaming build system.

"If you'd like to migrate from google-closure-compiler, which requires Java, you'll have to use gulp.src() or equivalents to load your JavaScript before it can be compiled. As this compiler runs in pure JavaScript, the compiler cannot load or save files from your file system directly," Google's Sam Thorogood, developer programs engineer, said. Developers not using Gulp or Webpack plugins will need to specify code via flags, release notes in GitHub state.

Closure is available under an Apache 2.0 license.

@itworld, +Web Solution, Web Design and development Company, India