There was a question about removing the back of telegram and keeping just the ui. Replacing it with xmpp. Lets say i am interested in somethenp like that:
Lets say you removed the telegram part. What library would you replace it with? For xmpp support.
Like i am looking maybe something starting in kotlin maybe. Since it has more support and such. Would conversations be able to be split back and front and "glue" it to a UI?
Or is there some other library
Besides the tigase kotlin library which i am definetily interested in
I just dont want to reimplement the whole world. Just the front :)
Or would you say not to bother and go to some java project like blabber and help 🤔
msavoritias
Im a begginer programmer so no idea what would be easier. Famous last words :P
moparisthebest
msavoritias: is it in kotlin now or Java or what?
msavoritias
Nowhere just starting
msavoritias
Just learning actually 😁
msavoritias
I just would like to start implementing all of xmpp or make my life harder✎
msavoritias
I just would not like to start implementing all of xmpp or make my life harder ✏
Apollohas left
moparisthebest
msavoritias: I mean if you want to use the existing UI and replace the backend what's the existing UI written in?
jubalhhas left
thomaslewishas joined
Kevhas joined
msavoritias
For conversations its java.
I was thinking to create a new UI in kotlin though. Since i have heard its more supported in android. 🤷♂️
msavoritias
Telegram is also java
msavoritias
With everything moving to kotlin i was thinking it would be better to go straight to kotlin.
pulkomandy
depends which Telegram you mean
pulkomandy
Telegram Desktop is in C++/Qt
sernickhas joined
marc0shas left
marc0shas joined
msavoritias
The android one
edhelas
So basically you're taking a plane and replacing the engine by changing the technology
lovetox
msavoritias, choose an existing project that you like and start contributing
edhelas
Sorry, but to me it looks like a bad idea
msavoritias
edhelas: that was the idea from the guy yeah. Personally i think its faster to write a new one
lovetox
the pros are you have actually a userbase from the start
edhelas
Better rebuild the thing from XMPP and "make it look like" Telegram desktop
msavoritias
Just wondering if it should java or kotlin
msavoritias
If its java i would just contribute to blabber maybe
xeckshas left
xeckshas joined
debaclehas left
msavoritias
A lot of the courses i saw were also in kotlin for android. So im like is it worth to still learn java today
Zash
Less talk, more https://github.com/DrKLO/Telegram/fork ?
sernickhas left
jubalhhas joined
dezanthas left
msavoritias
So basically my question is:
If you start android development tomorrow (again or not). Would you go with java or kotlin
Ge0rG
clearly kotlin
Schimon
> edhelas:
> 2022-06-09 08:23 (GMT+03:00)
> Sorry, but to me it looks like a bad idea
It's a temporary idea that may last for several years
Schimon
> edhelas:
> 2022-06-09 08:24 (GMT+03:00)
> Better rebuild the thing from XMPP and "make it look like" Telegram desktop
Good idea. Even better!
Ge0rG
msavoritias: you will need to know java anyway, to understand the libraries that you use
Schimon
FYI, imI'm focusing on both clients, mobile and desktop✎
Schimon
FYI, I'm focusing on both clients, mobile and desktop ✏
msavoritias
Ge0rG: what libraries do you have in mind for xmpp?
Is it feasible to "extract" the back of conversations and use it?
thomaslewishas left
msavoritias
I know of the tigase kotlin xmpp
msavoritias
library*
Ge0rG
msavoritias: Conversations wasn't using a library back then, I'm not sure if it was refactored enough to warrant such an approach. The go-to Java XMPP client library is Smack
Anton L. Šijanechas left
Wojtekhas left
dezanthas joined
thomaslewishas joined
msavoritias
Ge0rG: thank you :)
I will check this and tigase
msavoritias
But yeah my fear was that it would be too much work/pointless to seperate conversations from the ui✎
msavoritias
But yeah my fear was that it would be too much work/pointless to seperate conversations back from front ✏