Hacker News new | ask | show | jobs
by BlueZeniX 5309 days ago
Ever since I've started programming in haXe, it became clear that the language you code in should never be completely tied to a single platform. This article hints at Flex dying and tech needing replacement, yet many parts of an application (lets call it domain model and business logic) should be unique and not rely on a specific platform or data exchange format.

When you write your data model in a language that works on client and server platforms, you save lots of duplication of effort and gain flexibility. The best example of experiencing the opposite I have is a fairly large application I worked on, where the backend developers designed a totally different set of classes around a (pretty much undocumented) XML structure than the frontend guys. Basically all communication happened through XML. Sure "it's an open format!", "it's human readable! (in a sense)", but taking over this project figuring out semantics and what was considered valid became a painful effort.

Your frontend should always use the same domain model as the backend. Designing the fundamental parts of your application without relying on an ORM, XPath, JSON, .NET, Scala case classes, Flash, Javascript, HTML5, Swing, whatever... makes you platform agnostic and shrug at the next internet technology death.

Am I happy Flash is considered dead? No, currently HTML5 lacks many features I rely on today and sanity (isn't it kind of bizar we consider cross-browser issues as normal?). Will my skills and all of my codebase die with it? Absolutely not.