• 7 Posts
  • 709 Comments
Joined 1 year ago
cake
Cake day: August 7th, 2023

help-circle


  • Yes, Android has issues but what I’m saying is that so far Linux on phones really hasn’t been able to compete. No one want’s a phone with no camera, no GPS, no apps and terrible battery. Making Linux phones is just super difficult and sadly I don’t see it happening anytime soon. Android is a good platform with lots of hardware and apps. You have Fairphone offering long tern support, f-droid offering privacy oriented apps and LineageOS offering stable OS. Getting more phoes to support it is a better bet than getting Linux to properly work on modern phones.


  • Yes, it’s all true but the issue is you can already do a lot of those things with a lot of cheap hardware that is is simply easier to support than old phones. And when it comes to phones being phones Android is really good and has a lot of apps. I think the problem with Linux phones getting more popular is that the overlap between desktop/server and mobile is very small. I mean I use my phone only for phone things and a lot of things I do on my phone I can do only on my phone (e.g. charging an electric car is basically impossible without a Android/iPhone). Having a phone that can do some things desktop/server can do but can’t do a lot of things a phone can do is pretty much pointless at this point.

    When we’ll get a proper Linux phone with full Android apps support and convergence it will be really awesome but I just don’t think there’s enough interest to get there at this point.


  • I honestly don’t really get what there is to gain by using “Desktop Linux”.

    More freedom I guess. I remember my n900 and how fun it was to just ssh into it and dig in my home directory, install apps with packet manger, edit config files with vi and so on. It really felt like having small Linux machine in my pocket. With Android everything is definitely more locked up but then again, I’m not sure what would I do if it was more open. Writing apps for Android is easier than for desktop (or just as easy), there are no more hardware keyboard phones so using terminal on them is terrible anyway and phones just work anyway so there’s no need to mess with the configuration. Personally I mostly gave up on the ‘Linux phone’ idea and if I need any new features I will simply write cross platform app that runs on Android (for example with tauri).


  • AOSP. Sad but true.

    When first pinephone came out I really believed it’s heading somewhere. It thought that it will be kind of like raspberry Pi (fun, cheap platform to play with) and that we’ll quickly see copycats and it will slowly grow the way Linux on desktop did. AFAIK nothing like this happened. You still can’t get a phone with decent Linux support which for me shows that we’re stuck with android. I think most people that would help Linux phone happen are simply satisfied with LineageOS so there’s no incentive to put as much effort into it as it requires.





  • This was written by someone who never dealt with user requests. Typical user not only doesn’t know how to define requirements in a clear way, they also don’t understand limitations of the technology, side effects their changes can cause or different aspects of usability, compatibility and accessibility.

    Those are the abilities that limit who can contribute to projects, not coding skills.

    So for example you want an adaptive rewind time. Is it on by default? Where is in the settings? How does it interact with current auto-rewind feature (can you enable both at the same time?)? How do you name it so that typical user knows what it does? It’s not that those are difficult questions to answer. It’s that you need think about all that before you start changing code other people will use. Typical users don’t have the knowledge or experience required to do it. And it gets way more complicated with bigger changes.


  • Yep, programming is fun but working as a programmer not so much. For me writing software is a creative activity. It’s fun to come up with problems and find solutions for them. In my personal projects I decide what problem I want to solve, choose the technology I think will be fun to solve it in and then come up with a solution I like.

    At work you are usually handed a problem you don’t care about (we’re decommissioning X, you don’t have to know why, just change everything to use Y), the solution is described in detail by someone else and you just have to turn it into some code using 5-10 years old stack.

    Fortunately at my current job I mostly do projects without much technical oversight (proof-of-concept type project) so I can choose how I want to do then. I dislike the company culture but I know that moving somewhere else would mean going back to boring coding agian.


  • What you said (if I understand you correctly, you didn’t give any examples) boils down to breaking standards established by the current browsers. The standards that web developers and servers universally follow. If you want to build browser that will not follow standards you might just as well render HTML in non-standars ways. Most pages will not work anyway.