3 ms·
We're currently in an era where UI mostly means doing react type stuff or IOS/Android native, for whatever very loose definition of native you wish to use. A t
by jillesvangurp 6y ago
We're currently in an era where UI mostly means doing react type stuff or IOS/Android native, for whatever very loose definition of native you wish to use.
A trend that is interesting here is jetpack compose and swift UI, which are both inspired by react but better in the sense that they make full use of their respective type systems to make things like data bindings a lot less painful than they are in react. At least that being painful must be a reason why they keep changing how that works in every major release.
Add internal DSLs to the mix and you are basically looking at a nicer way to do UIs. That's only covering mobile currently unfortunately. However, Jetbrains just announced Compose Desktop which brings this to the desktop as well. If they figure out how to target web and IOS with this, they could very well have a winner.
For the web there is currently something called Fritz2, which runs via kotlin-js and basically adds very similar style bindings to a react like component framework. It's fully written in Kotlin and I've been meaning to give it a try so I can use my multi platform kotlin libraries there as well without having to figure out react and how to make that play nice with things like co-routines, data classes, etc.
For me the trend here is new UI frameworks originating outside of the javascript world gaining traction and eventually ending up running in a browser as well. IMHO it's that that is ripe for disruption.
- PaulDavisThe1st 6y agoFrom TFA: -------- Is desktop still relevant? I believe it is! I watched an interview recently, between an Android developer and an iOS developer. One was asking: “Does someone still writes desktop apps?” To which the other answered: “I have no idea… Maybe?” Both of them were recording it on a desktop, in a desktop application, while having a call over another desktop application. Multiple other desktop apps were probably used for post-production. None of those were written by magic elves or left to us by a mighty ancient civilization. The desktop might be less trendy, but only because it’s harder to sell useless crap here. ----------- "react type stuff" and iOS/Android do not cover this, but you probably knew that.
- jillesvangurp 6y agoI've not encountered a single desktop application project in the last 15 years in this industry. Very different from my first 10 years when I was even involved in that kind of thing a couple of times. I'm on Linkedin. Recruiters seem to have a fine talent to ask me for just about anything involving software spanning the entire spectrum of frontend, backend, embedded. Most of it is for stuff I don't even have on my CV. Based on that, I don't think I've seen even a single request for anything desktop based in the last ten years. Plenty of react and other web based stuff. Plenty of Android, IOS, and even Symbian when that was still a thing. Lots of backend in all flavors (even got a haskell one the other day). But not things like Swing, JavaFX, etc. That just doesn't happen. Not even rarely. I'm sure there's a parallel world where enterprises still run JVMs on ancient windows XP boxes that are no longer supported where they feel compelled to commission new applications. Just haven't come across any such project. It's not just less trendy from my point of view but dead as a doornail. Not a thing anymore that people actively recruit for. What little UI I come across on my own desktop tends to be either web based (electron) or native (I'm on a mac so mostly objectiveC and swift these days).
- PaulDavisThe1st 6y agoAt this point, desktop apps are not the domain of enterprise. They tend to be consumer focused, particularly for creatives (video, audio, graphics, etc. etc.). Most of the development for these apps takes place in smaller contexts (not necessarily startups). It also tends to require skills that most programmers these days don't have in abundance (largely because of the industry structure that you describe above). But none of that will involve Swing or JavaFX etc., because these are just not performant enough for the type of apps that are still required to remain native/desktop. I run a mid-size highly complex native/desktop FLOSS project, and it is just jaw-dropping for me to encounter people who say they have 5-16 years experience as a software developer but cannot consider compiling software. This happens regularly in the context of our project.