4 ms·
> "If they want to ship a product with good UI/UX quality, then they should learn the supported languages." The time sunk in learning a new programming languag
by ZenoArrow 9y ago
> "If they want to ship a product with good UI/UX quality, then they should learn the supported languages."
The time sunk in learning a new programming language is not inconsequential. You can get to a basic level of proficiency relatively quickly, but being productive in a language takes time and effort.
If I took your approach I'd constantly need to switch languages and rely on glue logic to piece them together. Just because a language is 'the best' at one thing doesn't mean it's always the right choice for a project that has multiple requirements. Should all regular expressions be written in Perl? Should all mathematical operations be written in Fortran? Should all macros be written in Common Lisp? Should all data structures be described in Idris?
- pjmlp 9y agoWhich is what we do in consultancy, and I am talking about personal experience here. We deliver projects in Java (Swing, JavaFX, Android, JEE, Spring), .NET (Forms, WPF, ASP.NET, UWP), C++ (NDK, .NET, Java native methods), Objective-C/Swift (iOS), PL/SQL(Oracle), Transact-SQL(MS SQL Server), pg/SQL (PostgreSQL), JavaScript(Web). Every 6 months or so, we tend to switch customer and respective project stack, being able to proficiently jump between technology stacks is expected.
- ZenoArrow 9y agoThat's not what we're talking about though. What we're talking about is developing outside the bounds of battle-tested stacks. To use another example, let's say I was writing an app in C#. Should I use a JVM GUI library just because I liked it better than the .NET ones? Even if it's technically possible, it's far from optimal.
- pjmlp 9y agoWe have done it a couple of times via IKVM, to access libraries like Lucene or MarvinView. We also have projects with application servers written in JEE, using native desktop GUIs in WPF, talking via REST to those servers.