517
Microsoft announces Python formulas in Excel... which have to get sent to the cloud
(techcommunity.microsoft.com)
this post was submitted on 23 Aug 2023
517 points (96.9% liked)
Technology
59594 readers
3363 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think you're comparing 47% to the wrong statistic. It's 47% of Kotlin developers do backend, not 47% of backend developers use Kotlin. I haven't seen any reliable backend languages survey yet.
It's not just side projects. Though admittingly most of the sources there are from a "talking kotlin" podcast which I suspect is tied to JetBrains, the projects discussed in the podcasts aren't just side-projects. For example "Allegro" is Poland and Slovenia's Amazon and almost all of their backend is Kotlin apparently. It backends tax collection in Norway and (part of?) Shazam which is owned by Apple which was why I put "Apple?", I'm not saying Apple's using it officially.
"Kotlin created against Swift" is completely speculative. The only things related they have is Swift started in 2010 while JetBrains announced it in 2011, but even then it's a stretch as Swift was only announced in 2014. You can't make something in response to something which doesn't exist yet.
Ah, right.
That makes a lot more sense.
It's interesting that Kotlin is also seriously used for server-side rather than just for frontend work in Android: is was not aware of that.
Indeed Kotlin being created as a response for Swift is speculative. The timings (launched one after the other separated by about 1-2 years) and the launch target platforms (both main smartphone OSes) were peculiar, as are the characteristics of both languages (they roughly added the same things over the languages they replaced, though that was the kind of "need" OO developers had been feeling at around that time and quite a few options came out, both new languages and new features for existing languages), but I'm not privy to whatever behind-closed-doors discussions there were on that so don't really know for sure.
As you say, maybe indeed Kotlin was being developed in parallel and then for launch piggy-backed on Google's need for "it's own language" in the smartphone market in response to Apple having lauched their own with quite some success - as I pointed out, it makes business sense to try as much as possible to lock-in developers to your own platform - since it would make sense for JetBrains to launch with a big partner with a large installed based.
Kotlin was announced in 2011 and Swift was announced in 2014; that's 3 years apart. Like you said, they do look kinda similar but I think that's the result of being designed with 2010s principles.
Kotlin also didn't launch on a smartphone platform, it just kinda released with the build tools without any initial target platform. Since JetBrain already owns IDEA, the most popular Java IDE, they just bundled that with Kotlin to launch the language. I think it's the opposite, Google piggy-backed off JetBrain's fame and install base in response to the Swift thing instead of also developing a new language. It isn't a lock-in either, JetBrains is quite independent of Android though they did kinda lock the language server to IDEA.