Share me:

I started to use intelliJ since the release of Anrdroid Studio, not much however.

Recently I stared to check again this time more detailed and in-depth.

I also wanted to check what others think about this and probably having longer experience than I had.

There is a nice summary(http://developer4life.blogspot.be/2012/01/intellij-vs-eclipse.html):

Plugins: Eclipse marketplace offers 1,276 plugins, and the Intellij Plugin Repository offers 727 plugins. This difference is not to be taken lightly, since plugins for new technologies will usually be developed mainly for Eclipse (e.g. Android, Drools, Activiti, etc). Moreover, Eclipse is easier to extend. When working on a specific technology most chances are that if a plugin exists, it will be an Eclipse plugin.

Multiple projects: This is an Eclipse winner for sure. It has the ability to open multiple projects in the same window, giving the coder control over dependencies and relations. Intellij has an option to open one project with multiple modules, but we found it to be cumbersome, and in times a little buggy. If you are going to use a lot of projects together and hate to switch windows, Eclipse is your choice.

Multiple languages: We have stated that we will only examine the Intellij Community Edition that supports Java, Groovy and Scala. However, if you plan to create a Python server, combined with Ajax & Html, joint with a java web server, or any other exotic language combinations, than Eclipse is your choice.

Code completion & inspection: While Eclipse has the ability to add plugins such as checkstyle, this one definitely goes for Intellij. The default code completion and assistance in Intellij is faster and better. If you are a rookie developer, Intellij can improve your code.

Usability: Intellij user experience is much easier to grasp. The learning curve in Intellij is by far faster. It seems using Intellij makes developing easier and more natural. Dropdowns, code completion, quick view, project wizards, etc, are all possible both in Eclipse and Intellij, but the experience in Intellij is much more satisfying.

Performance: The more plugins are installed on the IDE, the more heavy it is for your computer. However, saying that, Eclipse handles very large projects faster. Moreover, both of the IDE’s seems to be RAM junkies. Projects usually open faster in Eclipse, as Intellij indexes the entire project on startup, but while working on an existing project, Intellij works smoother. For example we have a huge SOAP project, which is impossible to work on with Intellij, so some of us even learn Eclipse just for that.

Repository integration: Both of the IDE’s have SVN\GIT\etc plugins. No doubt Intellij’s plugin is more reliable, has better GUI and easier to use.

GUI builder: We found that the built in Intellij GUI builder is more comfortable, and as mentioned above, usability wise its easier to learn, and more enjoyable to develop.

Well I have exactly the same opinion:

IntelliJ seems cooler and easy to use

The user experience overall in IntelliJ is better.

Repository integration is more stable on IntelliJ (but who does that from the IDE, shell rullezz 🙂

Eclipse can handle big and more projects much more nicely

Eclipse quite more plug-ins and more updates also (also if you don’t like smth u can change it yourself)

Eclipse if the total winner when talking about integrating many different projects on many different languages

Eclipse is the absolute winner when comes to plug-in and RCP development

So finally my decision is I would use Eclipse overall and IntelliJ for single android projects.

Gradle Eclipse support is developed by the SpringSource STS team. You can either use it via STS or install it separately. The Gradle Eclipse plugin provides the best IDE integration so far. It allows you to import Gradle projects into Eclipse. The information from the Gradle build script is used to configure your project in Eclipse. The import wizard is pretty smart. You can do partial imports of multi-project builds. You can also choose different naming patterns for sub-projects. You can even define Gradle tasks that should be run before and after an import/refresh. Additionally the Gradle plugin provides a runner for executing Gradle builds. The Gradle plugin also detects Gradle build scripts and automatically enables Groovy editor support for those files. That gives you syntax highlighting, syntax check and auto formatting.

Jetbrains has added support for Gradle with IDEA 11. You can import a Gradle project like you can import a Maven one. There is much more to come. New versions of the Gradle plugin will be released independently of IDEA.

This however will not be so transparent to someone not knowing your code, so another good option is to declare a group Route in routes.php and put all secure routes there probably handled by different controllers and methods:

What is the best PHP REST API Framework?

Epiphany

The Epiphany framework is fast, easy, clean and RESTful. The framework does not do a lot of magic under the hood. It is, by design, very simple and very powerful.

The documentation provides a few conventions that we believe lead to well written code but you’re free to use any style you’d like. The framework never dictates how you should write or structure your application.

Flight

Frapi

Frapi is a high-level PHP REST API framework that powers web apps, mobiles services and legacy systems, enabling a focus on business logic and not the presentation layer.
FRAPI handles multiple media types, response codes and generating API documentation. It was originally built by echolibre to support the needs of their client’s web apps, and now it’s been open-sourced.

Guzzle

Guzzle takes the pain out of sending HTTP requests and the redundancy out of creating web service clients. It’s a framework that includes the tools needed to create a robust web service client, including: Service descriptions for defining the inputs and outputs of an API, resource iterators for traversing paginated resources, batching for sending a large number of requests as efficiently as possible.

Laravel

Laravel is a clean and classy framework for PHP web development. Freeing you from spaghetti code, Laravel helps you create wonderful applications using simple, expressive syntax. Development should be a creative experience that you enjoy, not something that is painful. A well written documentation is a big plus.

Restler

A RESTful API server framework that is written in PHP that aids your mobile / web / desktop applications. A framework, but with a difference – Restler is all here to bend and mend to your needs. Turn your classes and its methods into an easily usable and better Web citizen with Restler.

Writing Server is made easy and light with just 3 PHP files

Simplicity through writing object oriented PHP like

Public methods are automatically mapped to a URL

Customization options and plugin architecture

Supporting for different formats like json, xml, yaml, amf, plist and custom formats

Support for different authentication schemes allowing to add your own auth plugins

Tonic

Wave Framework

A compact PHP micro-framework built loosely on model-view-control (MVC) architecture and factory method design pattern. It is made for web services, websites, info-systems and is built around a native API architecture, caching and smart image and resource management. Wave is a framework that does not include optional libraries with a very small footprint, lightweight and speed in mind.

Wave comes by default with a view controller and a gateway intended for website functionality with clean URLs that also incorporates a front-end JavaScript controller.

Zend: Zend_Rest_Server

Zend Framework 2 is an open source framework for developing web applications and services using PHP 5.3+. Zend Framework 2 uses 100% object-oriented code and utilises most of the new features of PHP 5.3, namely namespaces, late static binding, lambda functions and closures…