EclipseSource Blog

Collaboration support is supported since September 2024. You can eve self-hosted the server infrastructure if needed. https://eclipsesource.com/blogs/2024/09/09/eclipse-theia-1-53-release-…

I don't find this a fair thing to say. Eclipse was/is de facto the standard IDE for Java and JavaEE development, not to mention it was/is widely used as an IDE for C development. You can still find prebuilt packages [0] that quickly get you off ground. I've built commercial products with Eclipse RAP [1] that are still used today. Eclipselink [2] for persistence is also a great tool. Eclipse EMF [4] for modeling - and I've used that A LOT when building databases and model structures for businesses. I have since then moved to other languages and tools, but much of today's software was made possible by the Eclipse team. And I thank them for all their great work. 0 - https://www.eclipse.org/downloads/packages/ 1 - https://www.eclipse.org/rap/ 3 - https://www.eclipse.org/eclipselink/ 4 - https://eclipsesource.com/technology/modeling/#emf (edit: added EMF)

Example usage https://eclipsesource.com/blogs/2016/07/20/running-node-js-on-the-jvm/

This is diffing PNGs? That sounds like a recipe for disaster. Here is what this looks like in the much denigrated Java Enterprise world: https://eclipsesource.com/blogs/tutorials/rcp-testing-tool-rcptt-basic…

Well, immutable data-structures use "structural sharing", internally. Search for it. For example, this image, [1], shows two data-structures (the green nodes), that internally share many nodes. Now, comparing those two structures can be done efficiently, because the shared parts don't need comparing. [1] http://eclipsesource.com/blogs/wp-content/uploads/2009/12/clojure-tree… (a random image I found on the internet that illustrates my point)

Ah, my mistake. Here it is again. http://eclipsesource.com/blogs/2015/01/15/fast-dev-roundtrip/ The video shows live-reload development in Tabris.js, with a developer app so you can test and debug on your device as you go. Pretty neat, huh? :)

Ian Bull's annual top 10 Eclipse features (for Luna this year): http://eclipsesource.com/blogs/2014/06/25/top-10-eclipse-luna-features…

I had trouble finding any useful information on the landing page. EclipseSource did a series of blog posts highlighting some of the new features, which at least gives me some idea: http://eclipsesource.com/blogs/2010/06/23/top-10-eclipse-helios-featur…

In order to understand the frame of reference for Om, you really need to watch some Rich Hickey presentations [1][2] (or have a good understanding of functional programming). The first one is more relevant to your questions here, the second is just because Clojure programmers have very specific definitions of "simple" and "easy" and because it's a good talk. [1] http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey [2] http://www.infoq.com/presentations/Simple-Made-Easy That said, on to answering your questions: > If data changes, it needs to mutate, right? ... Data doesn't change in this model (see [1]). Incoming events (keyup, network request, page load) occur and your program responds to those events by producing a new, immutable set of data that you're going to use going forward. Om apps keep one reference to the root of the data tree–Om examples use app-state as the name–which represents the official current state of the data. You can reasonably argue that swapping out app-state is changing data except that anything that had a reference to the previous root(s) still has that reference and you have to go dereference app-state to get the current value instead of having it changed out from under you. > If that's the way, how can you efficiently do updates on relatively large chunks of data? ... Or am I missing something and is it really not that bad? [3] http://eclipsesource.com/blogs/wp-content/uploads/2009/12/clojure-tree… Clojure(script)'s data…