Thread: [SailfishOS] [STOPPED] Transponder, a native messaging client
View Single Post
marmistrz is offline marmistrz
2018-02-07 , 11:04
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#25
Originally Posted by MartinK View Post
though Pylint is already doing a pretty well & improving
https://github.com/PyCQA/pylint/issues/1646
https://github.com/PyCQA/pylint/issues/1651
https://github.com/PyCQA/pylint/issues/1660
https://github.com/PyCQA/pylint/issues/1631
https://github.com/PyCQA/pylint/issues/1630

This was more than enough to drop obligatory pylint check at work. Especially the first issue.

Originally Posted by MartinK View Post
On the other hand I think the static type checking provided by strongly typed languages is overrated - it will find only the most trivial issues, while any real mistakes in the application logic will still show up at only at runtime.
Just as an integral of a small function over a big set, if you have a lot of small, trivial bugs, that could be easily caught - that's a big burden.

As for the static checking in C++, yes, this is often not enough. Enter Rust!

Also in the Sailfish OS perspective - we have Python 3.4 (letst stable is 3.6), which compared to the ancient GCC version (4.8 I think ?) is substantially newer and should thus enable the use of resonably modern Python features, unlike with the default C/C++ compiler.

So I don't really see any real issues with using Python on this and I think it's a really good choice given the current state of the Sailfish OS toolchain.
There's the updated GCC by rinigus.
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 

The Following 3 Users Say Thank You to marmistrz For This Useful Post: