1. 28
  1. 5

    I have been using this as my daily-driver since July and very happy so far.

    1. 3

      I just looked at the calling/texting demo video, and while it’s really cool to write a text in vim, the entire process seemed pretty time-consuming with several menus to navigate with the volume rocker, etc. Once you get used to it, do you find the UI as fast to use as a more conventional touch-based UI?

      1. 3

        I don’t use their calling/texting features (I’m a jmp.chat user) but I find the button shortcuts very handy for sure, and the UI is much snappier than Android so even an extra tap now and then doesnt add time overall IME.

    2. 5

      It looks amazing. I look forward to getting a pinephone once my current phone dies.

      I have looked at the repository and noticed that the programs are written in C. Would a different language be a better choice to write and maintain such an environment? It is hard for me to propose an alternative, I am mentioning this because it seems like C with all its advantages has many issues as well and maybe a fresh start (kind of new platform?) would allow using different tools. For tools as simple as https://git.sr.ht/~mil/sxmo-utils/tree/master/programs/sxmo_setpineled.c wouldn’t a shell script be a better choice?

      Additnally, the file mentioned above looks suspicious to me – sprintf to a 80 bytes buffer regardless of the input, no free to malloc, program can return a negative value.

      1. 3

        no free to malloc

        There is no point in freeing blocks at the end of a program

        To your larger point, I’m not surprised that suckless attracts a lot of C hackers, and I’m not surprised that C hackers prefer to write certain types of tools in C instead of bash.

        1. 2

          The C is fine – slightly overly clever. But I agree – it’s a lot of code to run:

          if [ $2 = white ]; then
          echo $3 > /sys/class/leds/$1:$type/brightness'
          1. 2

            Yeah, this specific program would likely be better as a shell script, especially since the C program calls sh to write to the brightness file anyway.

            1. 1

              especially since the C program calls sh to write to the brightness file anyway.

              That seems silly… are there any valid reasons why it wouldn’t just open the file and write to it directly?

          2. 1

            i really want to explore using D for this, with rust or zig as slightly less compelling options. i feel like all three would be better than C.

          3. 2

            This is incredible! If I ever go back to using a smartphone, this might just be what I’ll get…

            Stories with similar links:

            1. Sxmo: Simple X Mobile - A Pinephone UI that is simple and suckless via aleph 2 years ago | 22 points | 4 comments