Monthly Archives: April 2016

Java and Red hat

Sometimes, the best objectives just don’t exercise.

Such is the situation with Red Hat-sponsored Nodyn, an free attempt meant to slot the Node.js server-side JavaScript system to the Java Exclusive Device, providing Java’s wealthy set of pedaling to Node. The venture is no more in effective growth due to a failure for making the well-known JavaScript additions, npm, perform together with it, said Mícheál Ó Foghlú, CTO of Red Hat Cellular.

We took as far as we could go,” he said, including that without npm, it was hard Nodyn to obtain grip, as the third-party segments are crucial. “The npm JS segments don’t actually all function in that JVM atmosphere. So it causes it to be a bit challenging to develop up the group and the grip.”

Node and Java still can stay well together and return details via such systems as RESTful API phone calls, said Ó Foghlú, but Nodyn was never created into any items. Everyone is still able to play a role to the venture, even though it has not been continuing to move ahead. ” free, it’s still there but we’re not placing so much power in it. We’re placing more power into Node itself.” Red Hat functions as system vendors of the Node.js Base, which manages growth of system.

Red Hat is, however, still fascinated in the free Vert.x venture, which provides a JavaScript-to-JVM link, Ó Foghlú said. An solution to Node, Vert.x provides a tool set for programs on the JVM. “What that does is it delivers the Node design to some other ‘languages’,” he said. The Node design would function Node’s light and portable, non-blocking IO structure. Languages presented in Vert.x consist of JavaScript, Java, Cool, Dark red and Ceylon. With rule operating in the JVM, Vert.x allows use of JVM pedaling, Ó Foghlú said.

Acknowledging the popularity of combined surroundings, Red Hat looks to link Node.js and Java.

The company is using the Node program administrator to create connections connecting Node.js to ActiveMQ, the Java texting service, said Wealthy Sharples, mature home for product control at the Red Hat app systems business team.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

5 Myths About Embedded Java

1. Java is slow.

Back in 1995, when Java was first launched, the Java exclusive machine (JVM) used very simple methods internal to run rule. All bytecodes were interpreted; line synchronization was basic, and storage control simple.

With over 20 years of growth, everything has shifted on so that the JVM now uses flexible selection and much more innovative line control, with a variety of pile templates and garbage-collection methods to choose from (including a pauseless enthusiast in the Zest JVM from Azul).

2. Java is dead.

The death of Java has been prediction almost since it was first launched, but it reveals no indication of passing away or even decreasing in its reputation. A look at factors such as the TIOBE catalog or the RedMonk Development Terminology Positions continually reveals Java as the number one or two language used by designers.

3. Java is freed from charge.

Strictly discussing, Java is not 100 % free (because Java is gradually just a trademark). What was the Sun (and now the Oracle) execution of the Java Development Kit (JDK) was launched under a GPL certificate (with Classpath exception) at the end of 2006. This is the OpenJDK venture and, since Java SE 7, has been the referrals execution for the Java SE requirements, as described through the Java Group Process (JCP).

4. Java does not experience from memory leaking.

In ‘languages’ like C and C++, the designer is accountable for all storage control, both assigning and clearly signaling that it’s no more needed (through phone calls like malloc and free). Java has automated storage control. When an item is instantiated, the JVM allocates area for it on the pile. When the program rule no more has any sources to an item, its area can be recycled by the rubbish enthusiast that operates regularly without anyone’s knowledge.

The key point here is that, in order to be garbage-collected, all sources must be eliminated. If a software preserves sources to factors even when they’re not needed and keeps assigning more factors, this will have the same effect as a storage flow in the conventional sense. Eventually, the JVM will run out of 100 % free storage to spend to new stuff.

5. Multi-threading in Java is difficult.

Before Java SE 5, this would have been a reasonable opinion. To create supportive multi-threaded rule, you only really had four APIs to work with (from the Thread class): wait, sleep, disrupt, and inform. This was difficult to get right.

To make life easier, the Concurrency resources (designed by Doug Lea, Lecturer of Computer Technology at New You are able to University) were included to the standard category collections. This offered higher-level abstractions such as semaphores, mutexes, read-write hair, and nuclear functions. Since then, some new APIs have been included, as well as improvement the fork-join structure for specific, recursively decomposable problems.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

The existence of Java vulnerabilities is proved

More Microsoft windows customers are setting up areas, but the Oracle Java and The apple company QuickTime issues are even more intense than they were last season, according to Secunia reviews on the 2010 first one fourth. Individuals may think their PCs are protected because they are working Microsoft company windows Upgrade, but most are still at threat because of risk in third-party applications.

Secunia’s figures are based on Microsoft windows PCs working its free Personal Application Examiner, so they only signify a part of the market. Because PSI encourages individuals update insecure software, most non-PSI customers are probably in a more intense place.

In the January-March one fourth, 93.9 % of UK customers had repaired their Microsoft windows based pc, and 96.2 % had repaired other Microsoft software, such as Microsoft Office (PDF). However, 11.9 % still had unpatched third-party software. The figures for the USA were a little bit worse: 93.5 % had repaired the OS, 96.1 % had repaired other Microsoft software, and 12.7 % had unpatched third-party software

The significant issues are Apple’s QuickTime and iTunes, Oracle Java JRE, and Adobe Audience.

In the UK, for example, unpatched Java set ups risen from 36 to 41 % in contrast to the first one fourth of last season, and unpatched QuickTime set ups improved from 55 to 61 %. Luckily, for most customers, both applications can be removed without a important charge. (Adobe Innovative Package customers may have a QuickTime issue.)

Java is a long-running issue, but things may enhance. Oracle has been pressured by the US FTC to apologise for misleading customers about its protection up-dates, and it has been required to weblink to something that uninstalls old editions.

Adobe Audience is another long-running problem: it had 121 weaknesses, which is almost as many as The apple company iTunes (130). Unfortunately, more than 50 percent the Adobe Audience set ups were unpatched.

QuickTime for Microsoft windows is a increasing issue because The apple company has lastly given up on it. Unfortunately, many customers may have skipped the protection signals, eg from US-CERT.

In its full review, available free on demand, Secunia mentioned at Microsoft company offered 67 % of the Top 50 programs running on PCs but third-party programs experienced 79 % of the weaknesses. (The table below reveals the 20 most-commonly set up programs.)

In the Top 50 programs, areas were already available for 84.6 % of the weaknesses found, and there were 23 zero-day weaknesses, in comparison to 20 in 2014.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

Java is ahead of everything else

Rod Johnson has came back to JAX after eight a very extensive period of lack. A lot has occurred since 2008 and most of his forecasts have come real, apart from one: that OSGi was going to be an essential technological innovation.

“Java is doing just fine”

The designer of the Springtime structure decided with the results of the TIOBE catalog, which indicators the reputation of development ‘languages’, and opined that not only is Java no.1 in conditions of terminology reputation, but it has handled to get before everything else. “The condition of Java is really, really healthier,” Brown gushed.

The good purpose why Java is doing well, Brown said, is because it has tailored and now performs particularly well with bins. It brings in key components for microservices such as support finding and routine breakers, but there’s also been a efficiency cutting-edge in Java in the situation of Springtime Start.

The increase of microservices

Some of the key changes since 2008 were that the web browser stopped to be the main way in which individuals absorbed programs, the speed of modify multiplied and developer-oriented solutions such as GitHub increased. However, the most essential change is still growth of microservices because different customers have different needs, which modify at different prices. There are at least two explanation why microservices perform many in the IT field nowadays: first, because more compact solutions fit on contemporary components and second, because microservices fit how individuals want to operate —hence Amazon’s two-pizza group concept, namely that a group should be sufficient to be fed with two chicken wings.

“We stay in an era of terminology fragmentation”

We’re going to see more Java, but also a lot more non Java, the CEO of Atomist declared in his keynote. One of the most essential training that we discovered from Rod Brown was that contemporary programs are going to include more ‘languages’. For those who are asking themselves about the next Java, that may as well be Java.

Still, it’s possible that the next Java won’t be as big as Java because the era of prominent ‘languages’ is gone now. Consequently, designers will have to understand at least one other terminology —other than Java—, especially if it’s Scala or Instant.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

Is Java stuck up with mobile devices?

Over the last a few several weeks, as part of my Smart cellphone Success Analyze as a dyed-in-the-wool iPhone and iOS customer, I’ve been submerging myself in the world of Android operating program — particularly, low-cost Android operating program devices made mostly in Chinese suppliers.

I’m not an extensive newbie when it comes to Android operating program. Actually I used Android operating program for several years before providing up on it this year. I am also competent in the essential techniques structure of the OS itself and how it operates on various ARM-derived rubber styles.

One of the goals of my Success Analyze is to see if a lower-cost Android operating program cellphone can, in reality, substitute my much more costly iPhone 6S. Three several weeks into quality, I am progressively of the viewpoint that the response is yes.

I still have my issues with Android operating program cellphone components and the OS itself, but they are not deal-breaker issues in any respect. All of these eventually are resolvable, and in time the OEMs, Search engines and the Android operating program designer group at large will find methods to them.

But fixing some issues will need hard options. One of those may be an extensive essential re-architecture of the Android operating program OS itself, in order to cope with what I consider to be an important flaw: considerably greater source usage in comparison to iOS.

Android’s Achilles high heel, aside from the “toxic hellstew” of protection areas and fragmentation which is outside the opportunity of this post and my Success Analyze sequence — is Java.

Java, beyond being an object-oriented development terminology with a C-like format, is the main efficiency atmosphere within Android operating program itself that operates many of the applications and user-land procedures in the cellular OS.

The execution/runtime atmosphere for applications coded in Java is a Java Exclusive Device, or JVM. A JVM can run on any processing system. That’s one of its best features. You can run Java applications on any program that operates a suitable JVM, and regardless of whether they have the same program structure.

The structure can be Apple or AMD x86, it can be IBM POWER, it can be Oracle’s UltraSPARC. Or it can be one of the many variations of ARM-derived processor chips.

So the program operating the JVM could be a mainframe, a big metal UNIX program, an x86 server, a PC, a Mac, a smartphone, a product, or even a smartwatch or a microcontroller in an included program.

Java’s mobility variety is impressive: It machines from the most important techniques with large levels of storage and CPU to the actual, low-power processor chips that are extremely resource-constrained.

The only thing they need in typical is a JVM, and the rule is basically convenient between methods with minimal variations.

There are different kinds of JVMs, such as server-side (J2EE), Java Conventional Edition on PCs and Mac pcs (J2SE) and Java Small Edition (J2ME) which was once used on foolish cellular mobile phones and the traditional BlackBerry.

Each of these sorts of JVMs have different efficiency and source usage information because they are focused towards different kinds of techniques.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

JDK Array Sort

In this article, we will discuss one of the JDK 8 feature called parallelSort. Before getting into the details of parallel sort, we will see sort method implementation.

The sort method will use the “merge” sort algorithm or Tim Peters’s list sort algorithm to sort the elements. “Merge” sort will use divide and conquer methods to sort the elements. The lager array will be divided into two parts and then each part of the elements will be divided further until there are no possible way to divide. The individual chunks will be sorted based on an “insertion” sort algorithm and then the results will be merged. To sort the larger array, it will have performance problems.

To avoid this, in JDK 8 we have a new feature called “ParallelSort“. This method will make use of “Fork/Join” framework. This will make use of all available processing power(On multicore processors) to increase the performance. Fork/Join framework will distributes the tasks to worker threads available in the thread pool. The framework will use “work stealing” algorithm. The worker threads which doesn’t have work will steal the work from the busy worker threads.

The Arrays#parallelSort method will decide whether to sort the array in parallel or in serial. If the array size is less than or equal to 8192 or the processor has only one core, then it will use Dual-Pivot Quicksort algorithm. Otherwise, it will use parallel sort.

public
static void parallelSort(char[] a) {
int n = a.length, p, g;
if (n <= MIN_ARRAY_SORT_GRAN ||
(p = ForkJoinPool.getCommonPoolParallelism()) == 1)
DualPivotQuicksort.sort(a, 0, n - 1, null, 0, 0);
else
new ArraysParallelSortHelpers.FJChar.Sorter
(null, a, new char[n], 0, n, 0,
((g = n / (p << 2)) <= MIN_ARRAY_SORT_GRAN) ?
MIN_ARRAY_SORT_GRAN : g).invoke();
}

The sample demo code is given below.

import
java.util.Arrays;
public
class SampleArrayDemo {
/**
* @param args
*/
public static void main(String[] args) {
double[] arr = new double[10000001];
for (int index = 0; index < 10000000; index++) {
arr[index]= Math.random();
}
System.out.println("The starting time" +
System.currentTimeMillis());
Arrays.parallelSort(arr);
//Arrays.sort(arr);
System.out.println("The end time" +
System.currentTimeMillis());
}
}
Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

Java to IOS has a very Impressive Technology

RoboVM, which introduced The apple company iOS cellular database integration to Java developers, has been stopped.

The device converted Java bytecode into local ARM or x86 rule, presented a Java-to-Objective C link, and reinforced Android operating system growth. It was obtained by cross-platform tools source Xamarin in Oct, which in turn was bought by Microsoft company in Feb. Now, the technologies are being nixed completely.

“Over the past few weeks, we’ve been dealing with the groups at Xamarin and Microsoft to evaluate know-how and business conditions of RoboVM to determine the path forward for the products,” said RoboVM CEO and co-founder Henric Muller. “After looking at the complete scenery for cellular growth with Java, the choice has been made to wind down growth of RoboVM.”

Discontinuance, Muller said, would have no impact on programs developed with RoboVM that were already delivery. “If your app is currently operating, it should proceed to operate unless The apple company presents a splitting change in iOS — just like any other iOS app.” For Android operating system tasks and programs built in RoboVM Studio room, designers can start and gather these in in Android operating system Studio room or IntelliJ Idea. Any cross-platform RoboPods used on Android operating system and iOS should proceed to operate in those tasks, subject to splitting changes, he said. RoboPods are rule collections and bindings for third-party services.

For programs still in growth, RoboVM is suggesting alternative Java SDKs that focus on iOS. Developers also can slot Java resource rule to C# and use Xamarin pedaling for Android operating system programs. Supporting or paid RoboVM permits can be used until Apr 17, 2017, and reimbursements are available.

The cessation follows a choice in Nov to take RoboVM out of free, stating a lack of group efforts and opponents using the rule. RoboVM, though, had once been considered as a appealing procedure for Java designers to build for iOS even as The apple company rejected to allow the Java Exclusive Machine on its popular cellular phones. Microsoft company on Thursday morning hours dropped to provide further discuss the destiny of RoboVM.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

New APIs and Python, Java and software development kits

Reasoning support agency iLand has released a new API along with new growth packages for Python, Java, and Google Golang. The aim is to give program designers an alternative choice when handling cloud applications.

The API, along with Python, Java, and Golang application growth packages (SDKs), can offer DevOps, IT functions, and handled companies, “another vector of customisability and adaptability to customer interface with cloud on their own terms”, the organization said.

Is this the end of the API economy?

Is this the end of the API economy?

Does the unexpected closing of well-known APIs mean the end of the API boom? Or is it time for a move to a old and maintainable future

iLand is expecting that the APIs will help in its cloud facilities promotions, which run on its Business Reasoning Services-Advanced Protection (ECS-AS) system. According to the organization, these incorporate security, conformity, catastrophe restoration, back-up, tracking, and resource management with the aim of assisting cloud adopting.

The ECS system is part of iLand’s free Apache Cassandra information factory, which is the after sales that is designed to give brilliant management, automated, and confirming abilities.

The organization also has a “cloud console” so that allows customers to handle performance from one web-based customer interface, the organization said. iLand’s CTO Bieber Giardina, the organization is trying to help designers enhance the visibility of what they are doing.”As a person you want to be able to see what you are doing and why,” he informed ZDNet.

“Users want only one lite of cup. They want all of these different components and, especially their VMs, all working through that individual lite of cup,” and to do that, a lot of products need to work through the same APIs, Giardina said.

Recently the market has seen a mindset modify towards API, he said. Several decades back, “people did not discuss about them very much but now they view the significance and they want the right ones and the best ones”.

Giardina confirms. “A couple of decades back nobody was referring to them, now everybody is and they want the best.”

He also believes other parts are suffering from a identical trend. “Every three to 5 years the market has to go through this,” he said. “There will be the best concept and individuals discuss about it and then also try this comes along and requires over. We can see this occurring with DevOps. It’s the best concept and now many more individuals and then everybody will be doing it.”

iLand said preliminary uses for the API consist of DevOps and processes automated to help designers and techniques technicians can quickly rotate up exclusive devices or set up techniques using their current implementation resources, while functions groups can accessibility and creatively incorporate cloud information together with their other tracking resources in only one show or system functions middle.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

Using Javascript Frameworks and Google’s Crawling Suggestion

At SEJ Peak on Wed, Maile Ohye from Google was requested about websites that are created using new JavaScript frameworks and modern style element they can create fantastic looking websites, but when it comes from searching viewpoint, they can definitely cause creeping and position issues with not just Google but all look for search engines.

Ohye said it is best to always check in Google Search System with the bring and provide device to make sure that Google is able to both spider and provide the site effectively. She said that there are always new Javascript frameworks being launched.

As many SEOs know, the intense websites that web developers come up with don’t always mean they are also SEO or online look for engine friendly. And there are often discussions in the Google Website owner Help boards from website owners with these wonderful websites that Googlebot can’t process effectively.

So prior to releasing a website, especially one that uses a lot of programs to provide the site, always use Google’s bring and provide device to make sure it is working – and being indexed – as designed.

Despite some labeling, syntactic, and standard collection resemblances, JavaScript and Java are otherwise irrelevant and have very different semantics. The format of JavaScript is actually produced from C, while the semantics and style suffer from the Self and Plan development ‘languages’.

JavaScript is also used in surroundings that are not Web-based, such as PDF records, site-specific web browsers, and pc icons. More recent and quicker JavaScript exclusive machines (VMs) and systems built upon them have also improved the reputation of JavaScript for server-side Web programs. On the consumer part, JavaScript has been typically applied as an considered language, but more recent web browsers perform just-in-time collection. It is also used in game development, the production of pc and mobile apps, and server-side network development with playback surroundings such as Node.js.

JavaScript was initially created in 10 days in May 1995 by Brendan Eich, while he was working for Netscape Emails Organization. Indeed, while competitive with Microsof company for user adopting of Web technological innovation and systems, Netscape considered their client-server providing a allocated OS with a transportable form of Sun Microsystems’s Java providing an atmosphere in which applets could be run. Because Java was a opponent of C++ and targeted at professional developers, Netscape also wanted a light-weight considered terminology that would supplement Java by attracting nonprofessional developers, like Windows Visible Basic.

Although it originated under the name Mocha, which was formally called LiveScript when it first delivered in try out produces of Netscape Gps 2.0 in Sept 1995, but it was relabeled JavaScript when it was implemented in the Netscape web browser edition 2.0B3.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page

What is Java profiling? What is its use?

If you are operating applications on top of JVM and want to be able to information them in manufacturing, on-demand, without impacting your app’s efficiency and customers, study on! Screenshots, functions, and other luscious factors is further down.

Do you run any applications on the JVM? How are you finding bottlenecks in your applications once they are in manufacturing, so you can improve them? If they become slowly, how are you finding which section of the rule in your app is slow?

Maybe you look at analytics like Garbage Selection. Maybe you run instructions like jstat to see if various storage private pools are complete or if there are too many FGCs (Full Garbage Collections). Or perhaps you run jstack or do destroy -SIGHUP PID and look at line dumps?

All of these are affordable approaches… until your facilities develops and/or you get fed up with walking around, sshing to devices, operating jstat and jstack or destroy with sudo so you have adequate privileges to operate those instructions, and so on.

Another way to deal with this is to basically have your conventional profiler connected to the procedure, or try to connect it on the fly, but that tends to be a challenge, needs more guide perform, and we all know full-blown profilers generally reduce applications concise where they could become useless. In brief, such profiling strategy is not really appropriate for manufacturing.

There’s Got to be a Better Way, Right?

Indeed, there is. Fulfill SPM‘s On-demand Java Profiler!

This low-impact profiler is meant to help you recognize bottlenecks in your manufacturing atmosphere without delaying your applications. It provides a wealthy research into the important rule, much like an average profiler.

What Kinds of Apps Can You Profile?

The SPM profiler can information anything that operates on top of the JVM. This indicates it can information Java applications, Scala applications, even factors like Clojure and Cool. You are not restricted to profiling only your own applications – the applications you developed. You can also use it to information any of the other SPM Integrations that run on the JVM – you information your web applications operating in Tomcat, Jetty, JBoss, or Glassfish, you can information Solr or Elasticsearch, Ignite, Kafka, Surprise, and so on.

How to Profile Your App With SPM

If your SPM broker edition is 1.29.2 or more recent, you’re set. If you have an mature edition upgrade it first.

Don't be shellfish...Email this to someonePrint this pageTweet about this on TwitterShare on StumbleUponShare on TumblrShare on LinkedInShare on RedditDigg thisShare on Google+Pin on PinterestShare on FacebookBuffer this page