5 ms·

Especially because a lot of the standard dev libraries are outdated or get outdated quick

yoz-y 10y ago
Well. One problem with development for Linux is that the libraries get outdated pretty quickly forcing you to chase the dependencies. I think programming against the LTS releases is not that bad of an idea. And there is always an option to go bleeding edge and just pull dependencies from sources.
- ageofwant 10y ago
  I use stock ubuntu with i3 on a Dell XPS 13, with no issue. Once I moved to i3 I realised I just don't care about the DM of the day. Dependencies go in their docker containers, where they belong. OK that's not true: I can only use 2.4G wireless, and sometimes I have to unmute system audio after using headphones.
  - yoz-y 10y ago
    I have not yet had the time to look into containers, but from what I understand it does indeed look like a solution to this problem.
- rbanffy 10y ago
  Can you give more details on this? I've been using Debian, Ubuntu and Fedora (as well as OSX/macOS) for ages now without any issues like the one you describe.
  - yoz-y 10y ago
    If you wish to distribute binaries rather than source for users to compile, you can not rely on the system libraries because that can get updated in a non compatible manner any time. Thus you need to package all of them all the way up from libc with your application (basically what windows and macOS apps do). So in regards to the original criticism of elementary not being updated often enough, I do not think it is an issue for development because it gives you a longer living target. As long as you get the security updates.
    - rbanffy 10y ago
      Usually distros don't change libraries in dangerous ways within a major release. For Debian, "stable" remains as it is for a very long time and even "testing" doesn't change much. Red Hat also maintains the environment stable to a fault. If you want to package for Ubuntu and Fedora, you'll have to probably build for every six-month/one-year release.
      - yoz-y 10y ago
        We agree. That is why I think that elementary not having the latest greatest libraries (it is an ubuntu lts under the hood) is not a problem and more of a benefit.
  - jeena 10y ago
    Let's say you write an app in Qt, Ubuntu 14.04 (LTS) has Qt version 5.3 but you want to use this cool new feature from Qt 5.7, you can pull the Sources and build Qt 5.7 on your computer and get it working. But obviously when you distribute it, other people who don't have Qt 5.7 installed yet because they are on a LTS distro will not be able to use it.

yoz-y 10y ago

Well. One problem with development for Linux is that the libraries get outdated pretty quickly forcing you to chase the dependencies. I think programming against the LTS releases is not that bad of an idea. And there is always an option to go bleeding edge and just pull dependencies from sources.

ageofwant 10y ago
I use stock ubuntu with i3 on a Dell XPS 13, with no issue. Once I moved to i3 I realised I just don't care about the DM of the day. Dependencies go in their docker containers, where they belong. OK that's not true: I can only use 2.4G wireless, and sometimes I have to unmute system audio after using headphones.
- yoz-y 10y ago
  I have not yet had the time to look into containers, but from what I understand it does indeed look like a solution to this problem.
rbanffy 10y ago
Can you give more details on this? I've been using Debian, Ubuntu and Fedora (as well as OSX/macOS) for ages now without any issues like the one you describe.
- yoz-y 10y ago
  If you wish to distribute binaries rather than source for users to compile, you can not rely on the system libraries because that can get updated in a non compatible manner any time. Thus you need to package all of them all the way up from libc with your application (basically what windows and macOS apps do). So in regards to the original criticism of elementary not being updated often enough, I do not think it is an issue for development because it gives you a longer living target. As long as you get the security updates.
  - rbanffy 10y ago
    Usually distros don't change libraries in dangerous ways within a major release. For Debian, "stable" remains as it is for a very long time and even "testing" doesn't change much. Red Hat also maintains the environment stable to a fault. If you want to package for Ubuntu and Fedora, you'll have to probably build for every six-month/one-year release.
    - yoz-y 10y ago
      We agree. That is why I think that elementary not having the latest greatest libraries (it is an ubuntu lts under the hood) is not a problem and more of a benefit.
- jeena 10y ago
  Let's say you write an app in Qt, Ubuntu 14.04 (LTS) has Qt version 5.3 but you want to use this cool new feature from Qt 5.7, you can pull the Sources and build Qt 5.7 on your computer and get it working. But obviously when you distribute it, other people who don't have Qt 5.7 installed yet because they are on a LTS distro will not be able to use it.