Jerad  Bailey

Jerad Bailey


Red Hat Mandrel Makes Java Native

Red Hat has introduced a new Java distribution, Mandrel, that compiles Java applications directly to native machine code for faster startup with lower memory.

Based on Oracle’s GraalVM, Mandrel offers an additional community-supported build with minor differences. Red Hat’s senior director of engineering, Mark Little, explains, “Mandrel can best be described as a distribution of a regular OpenJDK with a specially packaged GraalVM native image.” The primary driver behind Red Hat’s introduction of Mandrel is to drive speed and efficiency of the Quarkus framework, with its “supersonic subatomic Java.” Quarkus is a framework offering both local development with rapid reload as well as containerized or serverless distribution to cloud providers. Since its first introduction in 2019, Quarkus has emphasized the ability to build native executables that start faster and decrease cloud operational cost & resources.

The head of GraalVM, Thomas Wuerthinger, responded to the release of Mandrel, stating, “Thank you @maxandersen and colleagues for active participation in the @graalvmcommunity!”

Andres Dinn explained the role of GraalVM and Mandrel in episode 7 of the Quarkus Insights video series. The video explains usage as well as various technical details with questions such as the difference between just-in-time compilation and ahead-of-time compilation. Dinn explains the benefits and drawbacks of each and where they are best suited.

Mandrel’s GitHub repository represents a fork of GraalVM but does not yet offer binary distribution. Instead, users compile the JDK themselves by following the provided instructions.


What is GEEK

Buddha Community

Red Hat Mandrel Makes Java Native
Autumn  Blick

Autumn Blick


How native is React Native? | React Native vs Native App Development

If you are undertaking a mobile app development for your start-up or enterprise, you are likely wondering whether to use React Native. As a popular development framework, React Native helps you to develop near-native mobile apps. However, you are probably also wondering how close you can get to a native app by using React Native. How native is React Native?

In the article, we discuss the similarities between native mobile development and development using React Native. We also touch upon where they differ and how to bridge the gaps. Read on.

A brief introduction to React Native

Let’s briefly set the context first. We will briefly touch upon what React Native is and how it differs from earlier hybrid frameworks.

React Native is a popular JavaScript framework that Facebook has created. You can use this open-source framework to code natively rendering Android and iOS mobile apps. You can use it to develop web apps too.

Facebook has developed React Native based on React, its JavaScript library. The first release of React Native came in March 2015. At the time of writing this article, the latest stable release of React Native is 0.62.0, and it was released in March 2020.

Although relatively new, React Native has acquired a high degree of popularity. The “Stack Overflow Developer Survey 2019” report identifies it as the 8th most loved framework. Facebook, Walmart, and Bloomberg are some of the top companies that use React Native.

The popularity of React Native comes from its advantages. Some of its advantages are as follows:

  • Performance: It delivers optimal performance.
  • Cross-platform development: You can develop both Android and iOS apps with it. The reuse of code expedites development and reduces costs.
  • UI design: React Native enables you to design simple and responsive UI for your mobile app.
  • 3rd party plugins: This framework supports 3rd party plugins.
  • Developer community: A vibrant community of developers support React Native.

Why React Native is fundamentally different from earlier hybrid frameworks

Are you wondering whether React Native is just another of those hybrid frameworks like Ionic or Cordova? It’s not! React Native is fundamentally different from these earlier hybrid frameworks.

React Native is very close to native. Consider the following aspects as described on the React Native website:

  • Access to many native platforms features: The primitives of React Native render to native platform UI. This means that your React Native app will use many native platform APIs as native apps would do.
  • Near-native user experience: React Native provides several native components, and these are platform agnostic.
  • The ease of accessing native APIs: React Native uses a declarative UI paradigm. This enables React Native to interact easily with native platform APIs since React Native wraps existing native code.

Due to these factors, React Native offers many more advantages compared to those earlier hybrid frameworks. We now review them.

#android app #frontend #ios app #mobile app development #benefits of react native #is react native good for mobile app development #native vs #pros and cons of react native #react mobile development #react native development #react native experience #react native framework #react native ios vs android #react native pros and cons #react native vs android #react native vs native #react native vs native performance #react vs native #why react native #why use react native

Tyrique  Littel

Tyrique Littel


How to Install OpenJDK 11 on CentOS 8

What is OpenJDK?

OpenJDk or Open Java Development Kit is a free, open-source framework of the Java Platform, Standard Edition (or Java SE). It contains the virtual machine, the Java Class Library, and the Java compiler. The difference between the Oracle OpenJDK and Oracle JDK is that OpenJDK is a source code reference point for the open-source model. Simultaneously, the Oracle JDK is a continuation or advanced model of the OpenJDK, which is not open source and requires a license to use.

In this article, we will be installing OpenJDK on Centos 8.

#tutorials #alternatives #centos #centos 8 #configuration #dnf #frameworks #java #java development kit #java ee #java environment variables #java framework #java jdk #java jre #java platform #java sdk #java se #jdk #jre #open java development kit #open source #openjdk #openjdk 11 #openjdk 8 #openjdk runtime environment

Samanta  Moore

Samanta Moore


Going Beyond Java 8: Local Variable Type Inference (var) - DZone Java

According to some surveys, such as JetBrains’s great survey, Java 8 is currently the most used version of Java, despite being a 2014 release.

What you are reading is one in a series of articles titled ‘Going beyond Java 8,’ inspired by the contents of my book, Java for Aliens. These articles will guide you step-by-step through the most important features introduced to the language, starting from version 9. The aim is to make you aware of how important it is to move forward from Java 8, explaining the enormous advantages that the latest versions of the language offer.

In this article, we will talk about the most important new feature introduced with Java 10. Officially called local variable type inference, this feature is better known as the **introduction of the word **var. Despite the complicated name, it is actually quite a simple feature to use. However, some observations need to be made before we can see the impact that the introduction of the word var has on other pre-existing characteristics.

#java #java 11 #java 10 #java 12 #var #java 14 #java 13 #java 15 #verbosity

Introduction to Cloud-Native Java

Cloud-native solutions are not a novelty thing. Writing, deploying, and managing applications outside of local machines opens countless opportunities for businesses around the world. And those that use Java are major beneficiaries of this approach thanks to containers, JVM optimizations, multi-purpose frameworks, and native image technology. In this Refcard, we go through the basic explanations of cloud-native development on Java and explore everything you need to make your project cloud-native.

Table of Contents

► Introduction

► What Is Cloud-Native Java?

► Cloud-Native Features in OpenJDK

► Key Components and Approaches to Cloud-Native Java

► Setting Up Your Cloud-Native Java Environment

► Conclusion

Section 1


Cloud-native solutions are not a novelty thing. Ever since the first virtualized services emerged in the 90s, it was only a matter of time before the software development process in its entirety moved to the cloud. Writing, deploying, and managing applications outside of local machines opens countless opportunities for businesses around the world. And those that use Java, one of the most popular programming languages, are major beneficiaries of this approach thanks to containers, JVM optimizations, multi-purpose frameworks, and native image technology.

In this Refcard, we go through the basic explanations of cloud-native development on Java and see the scope of capabilities brought by multiple utilities. You’ll get everything that is required to make your project cloud-native: tools, an assessment of advantages and limitations, a detailed user guide, and a walkthrough example to get you started right away.

This is a preview of the Introduction to Cloud-Native Java Refcard. To read the entire Refcard, please download the PDF from the link above.

#java #cloud native #openjdk #native image #spring native #cloud-native java

Samanta  Moore

Samanta Moore


Spring Boot and Java 16 Records

In this article, we will discuss Java 16’s newest feature, Records. Then we will apply this knowledge and use it in conjunction with a Spring Boot application.

On March 16th, 2021, Java 16 was GA. With this new release, tons of new exciting features have been added. Check out the release notes to know more about these changes in detail. This article’s focus will be on Java Records, which got delivered with JEP 395. Records were first introduced in JDK 14 as a preview feature proposed by JEP 359, and with JDK 15, they remained in preview with JEP 384. However, with JDK 16, Records are no longer in preview.

I have picked Records because they are definitely the most favored feature added in Java 16, according to this Twitter poll by Java Champion Mala Gupta.

I also conducted a similar survey, but it was focused on features from Java 8 onwards. The results were not unexpected, as Java 8 is still widely used. Very unfortunate, though, as tons of new features and improvements are added to newer Java versions. But in terms of features, Java 8 was definitely a game-changer from a developer perspective.

So let’s discuss what the fuss is about Java Records.

#java #springboot #java programming #records #java tutorials #java programmer #java records #java 16