logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git

State-of-sway-April-2017.md (3908B)


  1. ---
  2. date: 2017-04-29
  3. # vim: tw=80
  4. title: State of Sway April 2017
  5. layout: post
  6. tags: [sway]
  7. ---
  8. Development on Sway continues. I thought we would have slowed down a lot more by
  9. now, but every release still comes with new features - Sway 0.12 added
  10. redshift support and binary space partitioning layouts. Sway 0.13.0 is
  11. coming soon and includes, among other things, nvidia proprietary driver support.
  12. We already have some interesting features slated for Sway 0.14.0, too!
  13. Today Sway has 21,446 lines of C (and 4,261 lines of header files) written by 81
  14. authors across 2,263 commits. These were written through 653 pull requests and
  15. 529 issues. Sway packages are available today in the official repos of pretty
  16. much every distribution except for Debian derivatives, and a PPA is available
  17. for those guys.
  18. [![](https://sr.ht/ICd5.png)](https://sr.ht/ICd5.png)
  19. For those who are new to the project, [Sway](http://swaywm.org) is an
  20. i3-compatible Wayland compositor. That is, your existing [i3](http://i3wm.org/)
  21. configuration file will work as-is on Sway, and your keybindings and colors and
  22. fonts and for_window rules and so on will all be the same. It's i3, but for
  23. Wayland, plus it's got some bonus features. Here's a quick rundown of what's
  24. new since the [previous state of Sway](/2016/12/27/State-of-sway.html):
  25. * Redshift support
  26. * Improved security configuration
  27. * Automatic binary space partitioning layouts ala AwesomeWM
  28. * Support for more i3 window criterion
  29. * Support for i3 marks
  30. * xdg_shell v6 support (Wayland thing, makes more native Wayland programs work)
  31. * We've switched from X.Y to X.Y.Z releases, Z releases shipping bugfixes while
  32. the next Y release is under development
  33. * Lots of i3 compatibility improvements
  34. * Lots of documentation improvements
  35. * Lots of bugfixes
  36. The new [bounty program](https://github.com/SirCmpwn/sway/issues/986) has also
  37. raised $1,200 to support Sway development! Several bounties have been awarded,
  38. including redshift support and i3 marks, but every awardee chose to redonate
  39. their reward to the bounty pool. Thanks to everyone who's donated and everyone
  40. who's worked on new features! Bounties have also been awarded for features in
  41. the Wayland ecosystem beyond Sway - a fact I'm especially proud of. If you want
  42. a piece of that $1,200 pot, [join us on
  43. IRC](http://webchat.freenode.net/?channels=sway&uio=d4) and we'll help you get started.
  44. Many new developments are in the pipeline for you. 0.13.0 is expected to
  45. ship within the next few weeks - [here's a sneak peek at the
  46. changelog](https://github.com/SirCmpwn/sway/issues/1162#issuecomment-295012255).
  47. In the future releases, development is ongoing for tray icons (encouraged by the
  48. sweet $270 bounty sitting on that feature), and several other features for
  49. 0.14.0 have been completed. We've also started work on a long term project to
  50. replace our compositor plumbling library, wlc, with a new one:
  51. [wlroots](https://github.com/SirCmpwn/wlroots). This should allow us to fix many
  52. of the more difficult bugs in Sway, and opens the doors for *many* features that
  53. weren't previously possible. It should also give us a platform on which we can
  54. build standard protocols that other compositors can implement, unifying the
  55. Wayland platform a bit more.
  56. Many thanks to [everyone that's contributed to
  57. sway](https://github.com/SirCmpwn/sway/graphs/contributors)! There's no way Sway
  58. would have enjoyed its success without your help. That wraps things up for
  59. today, thanks for using Sway and look forward to Sway 1.0!
  60. ---
  61. Note: future posts like this will omit some of the stats that were included in
  62. the previous posts. You can use the following commands to find them for
  63. yourself:
  64. ```bash
  65. # Lines of code per author:
  66. git ls-tree -r -z --name-only HEAD -- */*.c \
  67. | xargs -0 -n1 git blame --line-porcelain HEAD \
  68. | grep "^author " | sort | uniq -c | sort -nr
  69. # Commits per author:
  70. git shortlog
  71. ```