Page 2 of 3
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 10:00 am
by Adrian
This is a great review. A nice present for the new year.
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 10:38 am
by asqwerth
Jerry3904 wrote:asqwerth wrote:Also, the review gives the impression that apart from things like browsers and kernels (which he called "key components"), the applications in MX repos are all "old' or rather, Debian Stable packages.
I've gone through his package list and their versions, with these results:
--3 packages with difference in major numbers (13%)
--5 packages with difference in minor numbers, excluding kernel (21%)
--2 significant errors by DW (qt, gtk+)
If the first is correct, then we might want to look at those: python, mesa, gcc
I have to admit I wasn't looking at the DW list of packages. I was just thinking about the programs and apps in the MX repo that can't be found in Debian, or those that are newer than the versions in Debian repos.
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 10:39 am
by Jerry3904
I was just trying to see what he was basing his opinion on, and that was the only thing I could come up with. Posted the errors on DW.
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 10:59 am
by malspa
I was actually just looking at and comparing the results of the dpkg -l command from my Stretch (Xfce) installation (updated through today) and from the MX-17 live session (downloaded a couple of weeks ago). Not sure if these files would be helpful or informative to anyone here... I got kinda bored with looking through them, myself.
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 11:07 am
by malspa
Anyway, I thought it was a good and fair review.
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 11:48 am
by chrispop99
A DW reader has just commented that he thought there should be USB images available for download. Perhaps this is something that should be considered?
Chris
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 11:49 am
by dolphin_oracle
chrispop99 wrote:A DW reader has just commented that he thought there should be USB images available for download. Perhaps this is something that should be considered?
Chris
what's the difference between a usb image and a hybird iso?
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 1:42 pm
by fanisatt
There is always room for improvement....as long as there is a healthy "distro-mindset" !!
The speed of software developments in Linux today obviously varies from field to field.
Some "things" are running too much and some others are not !
...and somehow comes a big update one day and after that .... no boot...or no cute.....anymore !
This is what I mean with the word "distro-mindset"....
Therefore , I think that a serious and modern distribution should provide (as a matter of priority) strong balances and a general situation of harmony !!
Modernization is good and I like it but .... never at the expense of harmony and security.
I can see these good features here in MX-17 !!
I can't see in the above review any report about the nvidia-settings advanced tab.....
I had seen it (first time) in manjaro linux and after that I read about the 20-nvidia.conf and other details.... Anyway I could see video without screen flickering for first time in my 7-8 years linux life.....!!! (The same here !!)
It is a very serious matter for the everywhere troubled and disappointed nvidia users like me.
Sorry for my poor English....! I heavily use the google translator....
Best Regards !
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 1:48 pm
by rokytnji.1
Meh, I put my 2 cents in. Let's see if they publish it. It is the Emachine review/comment.
Re: Distrowatch MX-17 review
Posted: Mon Jan 01, 2018 2:01 pm
by richb
@fanisatt, Very thoughtful and well written piece. I totally agree with your comments. I would venture say that is the MX philosophy. Nothing is rushed for the sake of novelty. The release cycle has been a point release mid year and a new one at the end of the year. The final release has followed the Debian release cycle as we all know is certainly not rushed. In the interim the developers continue to modestly make improvements and the package team keeps applications up to date responding to requests and with their own initiative. The other key is that the dev team listens to users needs, and issues. I think the end result speaks for itself and most reviewers agree.