3 ms·

its like saying most of the seg fault caused is not due to use of C. Common langauge pattern / design choices made php to have bugs/ spaghetti code. At the end

its like saying most of the seg fault caused is not due to use of C. Common langauge pattern / design choices made php to have bugs/ spaghetti code. At the end developer control many thing but that doesn't mean language don't have any fault.

simion314 6y ago
It is not fair to bring C into this, C is an old language and when all the kernels and core libraries were created it was the best tool for the job. You hate C please go and contribute to the many rewrites and one day 25 years from now maybe we will have an OS written in some language that is cool now but would be outdated then. My advice is use the best tool for the job when possible, if you don't have a choice then learn to accept that most of us work with less cool languages/frameworks/projects ... the skill we bring is to find solutions for our customers and implement this solutions as best we can with the tools we have, most of the time a developer should be spending reading stuff(documentation,articles, code), thinking and the least time should be spent on typing code or tooling.
- giantDinosaur 6y ago
  If we want to really reduce typing we should make everyone program in Haskell (and start a national effort to improve its tooling) ;)
  - simion314 6y ago
    I think you misunderstand me , my point is think more and type less. Is not about clever one liners or languages with less verbosity but better implementations and abstractions and you can implement a good solution in a lot of languages. An example would be where a dev needs to implement X, then he goes on Google , finds some code sample , copy-pastes it, tests it, then changes here and there to make it work. The issue is that he maybe forgot to read the documentation for the functions used in the sample, or did not think that the sample is incomplete (maybe missinfg input sanitation) or is outdated or the solution was already in the project code if he only have asked or looked around in the code. Other example is when a dev wants to solve X, installs a package from npm that does X but does not understand it and in fact that npm package is just a few lines of code that you could have read, learn something, find limitations and improve that.

simion314 6y ago

It is not fair to bring C into this, C is an old language and when all the kernels and core libraries were created it was the best tool for the job. You hate C please go and contribute to the many rewrites and one day 25 years from now maybe we will have an OS written in some language that is cool now but would be outdated then. My advice is use the best tool for the job when possible, if you don't have a choice then learn to accept that most of us work with less cool languages/frameworks/projects ... the skill we bring is to find solutions for our customers and implement this solutions as best we can with the tools we have, most of the time a developer should be spending reading stuff(documentation,articles, code), thinking and the least time should be spent on typing code or tooling.

giantDinosaur 6y ago
If we want to really reduce typing we should make everyone program in Haskell (and start a national effort to improve its tooling) ;)
- simion314 6y ago
  I think you misunderstand me , my point is think more and type less. Is not about clever one liners or languages with less verbosity but better implementations and abstractions and you can implement a good solution in a lot of languages. An example would be where a dev needs to implement X, then he goes on Google , finds some code sample , copy-pastes it, tests it, then changes here and there to make it work. The issue is that he maybe forgot to read the documentation for the functions used in the sample, or did not think that the sample is incomplete (maybe missinfg input sanitation) or is outdated or the solution was already in the project code if he only have asked or looked around in the code. Other example is when a dev wants to solve X, installs a package from npm that does X but does not understand it and in fact that npm package is just a few lines of code that you could have read, learn something, find limitations and improve that.