![]() But AWT was too simplistic, and Swing, at least at the beginning, not fast enough. Certainly, with Java we could write graphical user interfaces that ran on different platforms. Instead of painstakingly writing apps for Windows, macOS, and Linux, we could focus on one platform, the browser. Yet, if that's true, why a new paradigm? Even more, is the desktop still relevant? It has been declared dead many times since the Web and the browser became ubiquitous. It proves that the underlying ideas and concepts are sound, flexible, and sustainable. This is not necessarily bad, on the contrary. To put it another way: their architecture is several decades old. What's important: most of the established desktop frameworks date back many years, even back to the early days of the operating systems they run on. Liking or hating that is a matter of taste. The other two platforms let the developers decide. Only Apple is strict regarding tools, frameworks, and programming languages to use for Mac apps. On macOS, Windows and Linux, things are a little different. It took until summer 2020 to release the first alpha versions to the public. Apple introduced SwiftUI during WWDC 2019. Googles cross platform framework Flutter (the first stable version appeared at the end of 2018) is declarative by design. The Web and React have been pioneering the movement ten years ago. ![]() Declarative UI frameworks are steadily displacing their imperative predecessors.
0 Comments
Leave a Reply. |