|
Probably not on the list because of the number of other surveys saying Swift has largely overtaken ObjC.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Probably.
But still Java/Kotlin are at the moment a "pair" (for Android) compareable to ObjC/Swift for iOS. And Kotlin is there, but ObjC is not.
While Swift nowadays has more devs than ObjC (totally understandable when I think about the cruel strange syntax of ObjC... a miracle how this language could be successful EVER), Kotlin still looks for ppl to adopt it.
I personally do like Kotlin very much but still, the support in Android Studio has its flaws... It's not a "first grade citizen" as it has been promised.
Every project still gets the Java Folder structure and no Kotlin folders by default... You always feel like a foreigner when u start to code Kotlin in an Android project.
I hope this gets better in Studio 4.0
|
|
|
|
|
I suspect we're talking a mixture of work and hobby development here.
It would be interesting to know if some of the more obscure selections are actually being used in anger.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
PeejayAdams wrote: are actually being used in anger.
In the case of several of them, they always make developers angry ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Well, I've often said that Javascript shouldn't be included in any discussion about languages ...
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
...of a company bringing ios, android and windows to the customers.
so we have
C++ for low level (SIP)
C# for windows
Objective-C/Swift for iOS
Java/Kotlin for Android
And of course SQL for the database... what else?
Currently evaluating Xamarin and other platform-independent options... but honestly... I am not sure if they ever make it out of our playground repository
modified 15-Jul-19 8:39am.
|
|
|
|
|
|
Isn't that a framework, not a language?
|
|
|
|
|
It's a C++ framework so it kind of implies the language.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
No it doesn't. I'm sure it can be used with other languages.
|
|
|
|
|
It is a C++ framework and it definitely can not be used with other languages.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
PIEBALDconsult wrote: I'm sure it can be used with other languages. I can't say it with certainty, but I would not bet anything on that afirmation
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
It's a C++ API making heavy use of compiler macros. While not impossible, its design would make any API wrappers massive fugly affairs (and MFC is fugly enough on its own).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
You don't want to use MFC with C++, never mind any other languages...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
That's been my suspicion since the 90s. I Don't recall ever hearing anything good about it.
|
|
|
|
|
I'm sure there's some sadist somewhere who has wrapped with C exports and built a DLL.
|
|
|
|
|
Perhaps you are thinking of MVC?
|
|
|
|
|
I still use it and one other guy here does too. We must be about the only three people who do.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Well, in my former workplace we didn't beause they were too advanced, not joking.
Win32 API and VB6 were our main GUI tools.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Yep, those certainly are advanced.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Four - me too. We have an active product that got its start using VC6.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: We have an active product that got its start using VC6
Us too - although it's gone through several other Visual Studio versions since then (2003, 2008, 2010 and now 2013, with a probable upgrade to 2017 or maybe 2019 in the next year).
And we've moved from MFC to Qt for new components, although we still have two from around 2005 that a) still use MFC, and b) still work fine (so there's no reason for updating them).
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
We're still using VS2008 as our primary development tool, even though we purchased licenses for VS2015. Our workload is such that VS2019 will be obsolete before we have time to update. It's not even that we can't update the code. The problem is that there isn't sufficient time and people to do the regression test necessary.
And I know full well all of the smells that last statement gives rise to.
Software Zen: delete this;
|
|
|
|
|
I feel your pain - I'm just glad that as our product is itself a tool for testing embedded system software, it's particularly easy for us to have automated whole-system regression tests. We just run existing tests that our (internal to our company) customers have used & verify that all the output artifacts remain the same (except where we expect the changes, of course).
If it makes you feel any better, we're particularly bad with unit tests - we have a few, but probably less than 1% coverage. And when we started, we had no SCM, and then when we did get SCM, it was SourceSafe...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Stuart Dootson wrote: when we did get SCM, it was SourceSafe. We're still using SourceSafe. Three or four years ago we thought about converting to git, and even had a pilot project moved to it. Between layoffs and shuffled responsibilities, it didn't happen .
Software Zen: delete this;
|
|
|
|