Search results
From APIDesign
You searched for Future
For more information about searching APIDesign, see Help.
Showing below up to 50 results starting with #1.
View (previous 50) (next 50) (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... - Future press release (31 bytes)
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,939 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... - TypesOfDependencies (4,985 bytes)
21: ...mple ant or maven, or whatever will appear in the future). - Blogs:JaroslavTulach:Daily Life:YetAnotherAwesomeReview (2,283 bytes)
12: I have to repeat the theme of [[The Future|the epilogue]]: The exploration of the [[API]] wo... - AOP (4,779 bytes)
29: ...is is the style majority of us will code in short future. Old [[AOP]] is dead, long live [[annotation]] ba... - EliminateFuzzyModifiers (8,118 bytes)
89: ...ention very likely is (especially in the light of future optimization suggested in [[AlternativeBehaviour]... - ClarityOfTypes (6,491 bytes)
42: ...ss in [[Java]] and moreover they are well set for future, as [[evolution]] story of this pattern is quite ...
48: ...iders]] of the ''Provider'' interface may need in future. - Lookup (7,917 bytes)
40: ...rily know all the ways your UI will change in the future. Other modules want to add actions (to popup men...
53: ...to your code without adding needed flexibility or future-proofing - then it's the wrong tool for the job. - ClearDefinitionOfVersion (1,810 bytes)
1: ...ited amount of releases. It is clear that in some future release, the set of methods will have to change. - Dependency Injection (7,651 bytes)
13: ...'BankAccount'' [[Java]] interface, as that limits future [[evolution]] as argued in [[Code Against Interfa... - Swing (2,055 bytes)
1: ...[[GUI]] for [[Java]] (in spite of many seeing the future in [[JavaFX]]; while everyone should be looking a... - OSGiAndNetBeans (10,580 bytes)
25: ...dles. Or, if people find out that [[OSGi]] has no future, they may rewrite all the bundles to [[NetBeans]]...
33: ...ts similar resource provider injection [[API]] in future, the [[Netigso]] could then run with any [[OSGi]]... - Scala (2,590 bytes)
14: Why has the so called language of future pollute its core libraries with trash like this? ... - Modular Java SE (19,537 bytes)
3: ...let's stick with one: we want to reach a point in future, when it will be enough to download just a limite...
117: ...es that mean whoever uses [[JavaBean]]s module in future, needs to install applet module as well? - Bugzilla (11,016 bytes)
87: ... meaning of ''won'tfix''. It does not predict the future, it does not mean "the issue does not and will no... - Closures (3,889 bytes)
23: ...handle combinators more and more effective in the future. - InvokeDynamic (11,361 bytes)
70: === Diverging Future ===
74: ...er than with [[invokeDynamic]]. Turns out that in future we are likely to have fast dynamic languages on t...
78: ...le by removing/deprecating [[invokeDynamic]] from future [[JVM]] spec and replacing it with a '''newFromAM... - Protocols (4,179 bytes)
21: ...ce now things shall be well set for a [[evolution|future growth]]. Both sides of the communication can now... - API Patch (4,634 bytes)
20: ...ix is applied (and subsequent changes are made in future) one can easily verify that the original intentio... - Karel (1,531 bytes)
1: ...ulach|me]]) which will be more and more useful in future to effectively deal with multi core programming. - DVBCentral (1,413 bytes)
19: ...pdateTask|AutoUpdateTask]], it will simplify your future upgrades! - Hotswap (11,992 bytes)
102: The chances this could improve in future are not high, imho. Even functional languages are... - Enum (7,264 bytes)
13: ...es at first and change them to regular classes in future? Well, because this is (almost) impossible with [...
71: ... set of values to infinite number of instances in future. - Distributed development (3,460 bytes)
13: ...simplest solution at the moment - why think about future development? Why be afraid that a workaround may ... - APIvsSPI (6,917 bytes)
29: ...ntAPI]] to form an ''open space'' to help us with future changes:
33: ...'''final''' and as such it may safely grow in the future. Moreover it has package private constructor (ano...
83: ...n contains new ''open space'' (so it is ready for future [[evolution]]). The whole set up is displayed on ... - Checked exception (11,009 bytes)
15: ...rently (and the number is expected to grow in the future), and having a duplicated set of classes is clear... - JDeveloper (6,776 bytes)
5: ...nths and those who stayed had little faith in the future. Still, I hoped we would get a chance to prove th...
19: ...g [[OSGi]] could be natural next step sometime in future. - OrderOfElements (7,000 bytes)
42: ...ports multiple releases of [[JDK]]s and for close future, we are going to continue to compile with [[JDK]]...
60: ...ixed order (at least when running on [[JDK]]7 and future releases). This might cause one time failures, bu... - OSGiCon (2,205 bytes)
5: ...s self confidence and [[JDeveloper|trust]] in the future. See in action the [[Netbinox|result]] we created... - RangeDependenciesAnalysed (8,811 bytes)
83: ...n]]) and for many purposes users can rely on such future defined open range. On the other hand, when somet... - Harmony (4,902 bytes)
25: ...g that can be re-used! As such I'd expect that in future the ''compact1 profile'' will be the [[JDeveloper... - JavaFX (5,054 bytes)
61: But who cares about [[JavaFX]] anymore, when the future is in [[DukeScript]], right?
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500)
Follow
