-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no 32bit for linux but still for windosh** #17328
Comments
yeah, 32-bit Windows has a way bigger market share, so it's still supported. All I can suggest is to switch to either 64-bit Linux or 32-bit Windows. |
my laptop is 32bit only.. of course is 3GHZ cpu with radeon gpu enought to use in office.. upgrade to 64bit is buy a new one.. is nonsense.. |
is it a hello from 2002? |
i buy it in 2012.. windo xp still support many laptops and is widelly used in some countires.. win-crap still made 32bit apps. for those devices.. but linux developers just forgotten that? what a kind of vision is that? |
I have 32-bit laptop too. Why I can't use telegram? I live in a poor family, and can't buy new laptop and phone. Please, back 32-bit linux support. |
You bought Pentium 4 in 2012? Well, it's a pity. My condolences.
Windows XP is not supported by tdesktop, as well.
It's a pragmatic vision: at the time of dropping support, market share of 32-bit Linux builds was 0.1% IIRC according to statistics @john-preston got from server developers. No one will make a build for you personally. |
give me the money then! puff what a response is that?
in any case still works in win7 32bit
unfair and pretty bad.. now i uderstand mr robot series!! |
The fact you're not the target audience doesn't mean someone should give you money... |
Ok, I will compile on my shit laptop client without ad (and it will no blocked) with 32-bit support. Special for my friend. |
Were there difficulties keeping the 32-bit Linux build building, or was it just dropped because of few people using it? |
I don't really remember. But dropping a build means -4 hours of building when doing a release |
i guess it cannot be.. cos the only work ins on w2in32 api.. not in linux one.. of course i not seen the code .. cos i am here as user |
There are distributions that still have 32-bit builds, I guess you can install one and ask its maintainers to add tdesktop to their repositories. So mr. robot-ish, right? |
problem are in 32bit in my firend's person.. is a bad thinking that hole world has money to upgrade hardware.. that machine is windo7 32bit with desktop telegram 32bit.. i have no access, he chat me! |
ask to support Windows 98 🙈 |
It's Windows 7. |
again .. do you check the update complete pictur5e. are you playing or take it in serious? win7 with lasted updates! |
I mean ask to support Windows 98 because someone somewhere uses a PC from 90's |
It was ~20 years since the last 32-bit processor has been manufactured, c'mon! |
please stop cringle.. is a computers firends: windows7 with dual core 2 duio .. 8Gb ram.. |
core 2 duo is a 64-bit processor |
i mean is a person that is not in my side.. is not the point of the topic.. my point is that we cannot force people to made complete upgrade is a cost that is ridicule! puff well thanks in any case! is clear whay M$ rule the world! |
imagine your friend used Windows 98 and you came here to support Windows 98 because he is poor... |
@Aokromes you closed cos a person like @ilya-fedin just take the issue as a jocke.. i guess is related to #17330 so all of you are wrong ther's more people wanted this |
That is widly incorrect : As of 2022, the current Raspberry Pi model runs a 32bit distro due to its 32bit GPU. And that is just the first example that comes to mind. |
rpi is arm while the talk here is about x86 |
Steps to reproduce
i try to connect using 32bit linux and cannot do
Expected behaviour
connect to telgram network
Actual behaviour
there's 3 king of build for windo but none of 32bit for linux:
Operating system
linux 32bit
Version of Telegram Desktop
2.6
Installation source
Static binary from official website
Logs
The text was updated successfully, but these errors were encountered: