Search results
From APIDesign
You searched for Future
There is no page titled "Future".
For more information about searching APIDesign, see Help.
Showing below up to 20 results starting with #1.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)
Page title matches
- The Future (2,302 bytes)
3: ...tion issues related to API too much. As the [[The Future|Epilogue]] suggests, it would be really more simp...
Page text matches
- The Future (2,302 bytes)
3: ...tion issues related to API too much. As the [[The Future|Epilogue]] suggests, it would be really more simp... - Blogs:JaroslavTulach:Daily Life (27,376 bytes)
273: ...carrier path? Well, maybe you should re-think you future! [[JavaScript]] is just another assembly language... - OlderBlogPosts (111,273 bytes)
187: Recently I saw the future of [[AOP]]. I thought one should say goodbye to A...
308: ...fferent languages, I've started to think about my future, but more importantly ''Arno Nyhm'' asked me to:
933: ...s April I wrote a [[netbeans:WinSys71PressRelease|future press release]] describing all the things we want...
1011: ...ortance of ''working backwards'' I gladly present future [[netbeans:WinSys71PressRelease|window system pre...
1341: ...e [http://wiki.netbeans.org/Fitness68PressRelease future press release] (as advocated in [[Chapter 16]], C... - Trust (4,434 bytes)
60: ...ue to mobile phones, it’s safer to eliminate “future” promises,
64: Promising heaven in the future doesn’t count. - Teamwork (2,433 bytes)
3: ...ne, however software projects of today and of the future are designed by teams. Keeping consistency in suc... - Evolving the API Universe (1,068 bytes)
3: ...ot good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompat... - Reviewers (3,307 bytes)
36: == Daily Life and the Future ==
50: * [[Image:Ok.png]]Epilogue - [[The Future]] - Outline (1,185 bytes)
37: * [[The Future]] - Cluelessness (3,942 bytes)
16: ...ur understanding, leaving the explanation for the future. - ThanksReviewers (12,358 bytes)
51: ...blogosphere]]. Thanks Jesse for all your past and future notes. - Have You Ever Wondered (13,635 bytes)
42: ...ot good enough? Have you been afraid of the API's future? Of numerous bugs, each creating another incompat...
44: ...ne, however software projects of today and of the future are designed by teams. Keeping consistency in suc...
52: ...tion issues related to API too much. As the [[The Future|Epilogue]] suggests, it would be really much simp... - APIDesignPatterns:Exceptions (8,610 bytes)
29: ...nal''' - your options for [[Ever_Changing_Targets|future evolution]] will remain more open. - APIFest08 (4,214 bytes)
67: ...e planned it in advance. It should be part of any future ''fest''. - APIFest08:Report (10,858 bytes)
37: .... The author of this solution managed to guess my future requirements and he changed nothing in the origin... - ExceptionExtensibility (3,165 bytes)
22: ...lue our users and want to support this API use in future. However we also want to please more and more use... - JDK (202 bytes)
3: The future of [[JDK]] is in modularization. See my effort to... - PropertyFiles (5,584 bytes)
29: ...our [[API]] users will be in deep problems in the future - as my [[OSGi]] manifest adventure shows. - Good Name (1,833 bytes)
5: In one section of [[TheAPIBook]]'s [[The Future|epilogue]] I was searching for a [[Good Name]] fo... - ClarityOfAccessModifiers (8,203 bytes)
88: ...ke life of [[API]] designers easy. Hopefully some future language will overcome this flaw and instead of p... - InfoQReview (12,017 bytes)
48: although software projects of today and of the future are designed in teams.
129: future evolution. A mode of this kind does not need diru...
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)
Follow
