To edit or add content to this Wiki, you can simply create a new account at http://wocommunity.org/account.
87 respondants.
Top 5 countries
Country name |
% |
# of developers |
---|---|---|
USA |
26% |
49 |
Germany |
18% |
50 |
Canada |
11% |
24 |
France |
8% |
16 |
UK |
8% |
22 |
For how many years has your organization been using WebObjects?
Less than 2 years |
5% |
Between 2 and 5 years |
10% |
Between 6 and 10 years |
33% |
More than 10 years |
52% |
Which versions of WebObjects does your organization use?
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
5.4.x |
94% |
93% |
87% |
86% |
5.3.x |
17% |
24% |
21% |
35% |
5.2.x |
10% |
5% |
3% |
9% |
4.5.x |
4% |
1% |
6% |
6% |
4.0.1 |
1% |
1% |
1% |
1% |
Which platforms are used at your organization/department to DEVELOP with WebObjects?
Mac OS X |
98% |
Windows |
9% |
Linux |
8% |
Which platforms are used at your organization/department to DEPLOY WebObjects applications?
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
Mac OS X Server |
51% |
52% |
59% |
68% |
RedHat/Fedora/CentOS Linux |
45% |
37% |
40% |
42% |
Debian/Ubuntu Linux |
30% |
23% |
21% |
10% |
Windows |
15% |
13% |
14% |
13% |
Amazon Linux |
14% |
12% |
12% |
2% |
Mac OS X "client" |
10% |
13% |
9% |
19% |
Solaris |
9% |
11% |
7% |
9% |
FreeBSD |
6% |
3% |
6% |
8% |
SuSE Linux/OpenSUSE |
1% |
1% |
1% |
0% |
Which database systems does your organization use with WebObjects?
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
MySQL |
52% |
45% |
42% |
39% |
PostgreSQL |
51% |
38% |
44% |
39% |
Oracle Database |
24% |
28% |
28% |
27% |
FrontBase |
20% |
19% |
20% |
22% |
MS SQL Server |
9% |
14% |
14% |
12% |
H2 |
5% |
2% |
6% |
1% |
OpenBase |
2% |
6% |
8% |
8% |
Sybase |
2% |
1% |
2% |
2% |
Derby |
2% |
2% |
1% |
1% |
Amazon RDS |
0% |
0% |
1% |
0% |
DB2 |
0% |
0% |
1% |
2% |
HSQLDB |
0% |
1% |
1% |
1% |
SAP MaxDB |
1% |
1% |
1% |
1% |
Do you use Project Wonder in your project?
Yes, in all of them |
66% |
Yes, in some of them |
29% |
No, but we will use them later |
0% |
No, and we are not going to use it |
6% |
Which IDEs does your organization use for WebObjects development?
Eclipse with WOLips |
97% |
Xcode |
8% |
Project Builder |
6% |
IntelliJ IDEA |
3% |
Netbeans |
1% |
Rolled out own |
1% |
Does your organization use JavaClient?
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
Yes |
3% |
5% |
6% |
5% |
No |
95% |
95% |
92% |
95% |
No, but planning in the near future |
2% |
0% |
2% |
N/A |
Does your organization use DirectToWeb?
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
Yes |
39% |
42% |
42% |
42% |
No |
56% |
45% |
47% |
58% |
No, but planning in the near future |
5% |
12% |
12% |
N/A |
Does your organization use Direct To Web Services?
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
Yes |
8% |
8% |
8% |
3% |
No |
85% |
87% |
87% |
97% |
No, but planning in the near future |
7% |
5% |
5% |
N/A |
Does your organization consume SOAP services using WebObjects?
|
2013 |
2012 |
2011 |
---|---|---|---|
Yes |
33% |
32% |
40% |
No |
66% |
59% |
55% |
No, but planning in the near future |
1% |
9% |
6% |
Does your organization consume REST services using WebObjects?
|
2013 |
2012 |
2011 |
---|---|---|---|
Yes |
43% |
34% |
28% |
No |
39% |
43% |
50% |
No, but planning in the near future |
18% |
23% |
22% |
Does your organization provide REST services using WebObjects?
|
2013 |
2012 |
2011 |
---|---|---|---|
Yes |
53% |
46% |
32% |
No |
27% |
32% |
45% |
No, but planning in the near future |
20% |
22% |
23% |
Does your organization provide SOAP services using WebObjects?
|
2013 |
2012 |
2011 |
---|---|---|---|
Yes |
25% |
19% |
24% |
No |
73% |
72% |
69% |
No, but planning in the near future |
2% |
9% |
7% |
Does your organization use RIA technologies? If yes, which one(s)
|
2013 |
2012 |
2011 |
2010 |
---|---|---|---|---|
AJAX framework from Wonder |
80% |
71% |
79% |
71% |
jQuery |
62% |
45% |
36% |
N/A |
Cappuccino |
1% |
2% |
6% |
1% |
Adobe Flex |
6% |
5% |
6% |
6% |
SproutCore |
2% |
3% |
5% |
N/A |
Dojo |
0% |
2% |
3% |
N/A |
GWT |
5% |
4% |
1% |
2% |
YUI |
1% |
1% |
1% |
N/A |
Sencha Touch |
1% |
1% |
1% |
N/A |
MooTools |
2% |
3% |
N/A |
N/A |
DHTMLX |
1% |
1% |
1% |
N/A |
AngularJS |
2% |
N/A |
N/A |
N/A |
Backbone |
3% |
N/A |
N/A |
N/A |
Do you use WebObjects as a back-end to other technologies, for example to communicate with a iPhone application? If yes, which technologies?
|
2013 |
2012 |
2011 |
---|---|---|---|
iOS apps |
60% |
32% |
29% |
Mac desktop (Cocoa) |
9% |
10% |
10% |
We don't, but will do in the near future |
32% |
37% |
31% |
Android |
4% |
N/A |
N/A |
Does your organization still use WebObjects for new projects?
Yes |
83% |
No |
13% |
yes, but fewer |
1% |
Not currently, but may in the future |
1% |
Not sure yet |
1% |
If you are stopping developing with WebObjects, what are the main reasons for dropping WebObjects at your organization?
risk perceived from management
We stop using WebObjects because of the poor performance in production and due to the new technologies available such as .net.
Developer availability; market dominance of other languages (we are leaving Java more and more in general)
WO is not OpenSource
Core frameworks still owned by apple, too buggy, no chance to make them better. Wonder ist good, but only a workaround.
JEE (JSF/JPA) meanwhile at least as good as WO (sigh...)
Hard to find/hire developers
Excellent, but too small community.
No official certificates (like Oracles OCP)
We are not planning to stop using it any time soon but we will probably think about this if other frameworks get killer features that won't find their way to WO.
Finding new developers for WebObjects
Rather small community
Lack of documentation
Existing (better?) open source alternatives. Our clients want open source solutions.
Scarcity of developers
tied to JDK 1.5.
lack of affordable/knowledgable developers.
due to being obscure - inability to to train new developers.
Seaside is easier / more flexible and all the code is at your fingertips. Fully open source. Don't like how WO proper is closed source. Don't like how hard it is to keep WOLips in tune with Eclipse upgrades. Don't like how hard it is for new people to setup and install WO. But, WO is still a nice system and powerful in its own right.
Null Client knowledge about WO
Talent, especially locally, is hard to find.
WebObjects is stuck at 5.4.3 with apparently no active development. I don't like Eclipse, so there is no future in WebObjects for me.
Lack of evolution from Apple
WebObjects is finally starting to lag behind in terms of its library use. For example the concurrency code is outdated and in memory caching could be handled much better with libraries like Google Guava.
If we ever did come to that point, I imagine it would be because we couldn't find qualified developers who were both able and interested in learning WO.