To edit or add content to this Wiki, you can simply create a new account at http://wocommunity.org/account
.
98 respondants.
Top 5 countries
Country name |
% |
# of developers |
|---|---|---|
USA |
36% |
94 |
Germany |
14% |
54 |
Canada |
14% |
27 |
France |
9% |
42 |
Australia |
9% |
15 |
For how many years has your organization been using WebObjects?
Less than 2 years |
4% |
Between 2 and 5 years |
20% |
Between 6 and 10 years |
35% |
More than 10 years |
41% |
Which versions of WebObjects does your organization use?
|
2012 |
2011 |
2010 |
|---|---|---|---|
5.4.x |
93% |
87% |
86% |
5.3.x |
24% |
21% |
35% |
5.2.x |
5% |
3% |
9% |
5.1.x |
0% |
1% |
1% |
4.5.x (Objective-C) |
1% |
3% |
4% |
4.5.x (Java) |
0% |
3% |
2% |
4.0.1 |
1% |
1% |
1% |
Which platforms are used at your organization/department to DEVELOP with WebObjects?
Mac OS X |
96% |
Windows |
9% |
Linux |
9% |
Which platforms are used at your organization/department to DEPLOY WebObjects applications?
|
2012 |
2011 |
2010 |
|---|---|---|---|
Mac OS X Server |
52% |
59% |
68% |
RedHat/Fedora/CentOS Linux |
37% |
40% |
42% |
Debian/Ubuntu Linux |
23% |
21% |
10% |
Windows |
13% |
14% |
13% |
Amazon Linux |
12% |
12% |
2% |
Mac OS X "client" |
13% |
9% |
19% |
Solaris |
11% |
7% |
9% |
FreeBSD |
3% |
6% |
8% |
SuSE Linux/OpenSUSE |
1% |
1% |
0% |
Which database systems does your organization use with WebObjects?
|
2012 |
2011 |
2010 |
|---|---|---|---|
MySQL |
45% |
42% |
39% |
PostgreSQL |
38% |
44% |
39% |
Oracle Database |
28% |
28% |
27% |
FrontBase |
19% |
20% |
22% |
MS SQL Server |
14% |
14% |
12% |
H2 |
2% |
6% |
1% |
OpenBase |
6% |
8% |
8% |
Sybase |
1% |
2% |
2% |
Derby |
2% |
1% |
1% |
Amazon RDS |
0% |
1% |
0% |
DB2 |
0% |
1% |
2% |
HSQLDB |
1% |
1% |
1% |
SAP MaxDB |
1% |
1% |
1% |
BerkeleyDB JE |
1% |
N/A |
N/A |
Apache Cassandra |
1% |
N/A |
N/A |
Do you use Project Wonder in your project?
Yes, in all of them |
66% |
Yes, in some of them |
25% |
No, but we will use them later |
3% |
No, and we are not going to use it |
5% |
Which IDEs does your organization use for WebObjects development?
Eclipse with WOLips |
97% |
Xcode |
10% |
Project Builder |
3% |
Rolled out own |
1% |
Does your organization use JavaClient?
|
2012 |
2011 |
2010 |
|---|---|---|---|
Yes |
5% |
6% |
5% |
No |
95% |
92% |
95% |
No, but planning in the near future |
0% |
2% |
N/A |
Does your organization use DirectToWeb?
|
2012 |
2011 |
2010 |
|---|---|---|---|
Yes |
42% |
42% |
42% |
No |
45% |
47% |
58% |
No, but planning in the near future |
12% |
12% |
N/A |
Does your organization use Direct To Web Services?
|
2012 |
2011 |
2010 |
|---|---|---|---|
Yes |
8% |
8% |
3% |
No |
87% |
87% |
97% |
No, but planning in the near future |
5% |
5% |
N/A |
Does your organization consume SOAP services using WebObjects?
|
2012 |
2011 |
|---|---|---|
Yes |
32% |
40% |
No |
59% |
55% |
No, but planning in the near future |
9% |
6% |
Does your organization consume REST services using WebObjects?
|
2012 |
2011 |
|---|---|---|
Yes |
34% |
28% |
No |
43% |
50% |
No, but planning in the near future |
23% |
22% |
Does your organization provide REST services using WebObjects?
|
2012 |
2011 |
|---|---|---|
Yes |
46% |
32% |
No |
32% |
45% |
No, but planning in the near future |
22% |
23% |
Does your organization provide SOAP services using WebObjects?
|
2012 |
2011 |
|---|---|---|
Yes |
19% |
24% |
No |
72% |
69% |
No, but planning in the near future |
9% |
7% |
Does your organization use RIA technologies? If yes, which one(s)
|
2012 |
2011 |
2010 |
|---|---|---|---|
AJAX framework from Wonder |
71% |
79% |
71% |
jQuery |
45% |
36% |
N/A |
Cappuccino |
2% |
6% |
1% |
Adobe Flex |
5% |
6% |
6% |
SproutCore |
3% |
5% |
N/A |
Dojo |
2% |
3% |
N/A |
GWT |
4% |
1% |
2% |
YUI |
1% |
1% |
N/A |
Secret Project |
2% |
N/A |
N/A |
Sencha Touch |
1% |
1% |
N/A |
MooTools |
3% |
N/A |
N/A |
DHTMLX |
1% |
1% |
N/A |
Our custom framework |
3% |
N/A |
N/A |
Do you use WebObjects as a back-end to other Apple technologies, for example to communicate with a iPhone application? If yes, which technologies?
|
2012 |
2011 |
|---|---|---|
iOS apps |
32% |
29% |
Mac desktop (Cocoa) |
10% |
10% |
We don't, but will do in the near future |
37% |
31% |
Does your organization still use WebObjects for new projects?
Yes |
85% |
No |
12% |
mixed: WO + Grails |
1% |
Maybe integrate as back-end with iOS app |
1% |
looking for alternatives |
1% |
If you are stopping developing with WebObjects, what are the main reasons for dropping WebObjects at your organization?
Where it makes sense to use it, we will still use it. The space where it makes sense to use WO vs. Rails continues to shrink.
Apple has stopped updating it. We seem to be stuck with an aging version of WebObjects.
No support from Apple, no new versions, hard to find developers, no upper management support. Most people devs would prefer something more main steam like .NET or Java
Since WO is no longer being developed by Apple, we are looking for replacements for future development. Cayenne replaces EOF well. We have yet to examine the web framework side closely, but Tapestry will be the first candidate.
Plan on maintaining projects, but most new projects recently have either been easier to achieve in other frameworks, or required use of MamboDB or similar data stores for scale out needs.
the monitor who crash everytime. EOF is not threaded, ...
Mess with long in the tooth Apple WebObjects Frameworks, which are not open sourced. I am looking at stuff like Google App Engine as a replacement, or node.js. As long as it is clear that there is some corporate backing (App Engine) or Open Source.
- No development/bugfixes anymore to WebObjects 5.4.x (like 2.1Gb directaction upload limit)
- more standard Tomcat perspective (easier in Windows, Linux, ...)
No demand. Doing richer client-side apps with more "dumb" backends.
Our company focus is UI/UX development. We are teaming with other companies for programming. We still have some existing WebObjects applications that we will maintain.
EOL product.
Difficulty finding developers
Apple decision to deprecate the WebObjects product.
Risk factor from management point of view
Going for better technologies
Losing skilled WO developer
Lack of support from community