3 ms·

I think that is an important blog post. My idea for approach is to discuss those things on forums on the internet - at work on coffee breaks. Just to challenge

by ozim 5y ago

I think that is an important blog post. My idea for approach is to discuss those things on forums on the internet - at work on coffee breaks. Just to challenge own beliefs and see other arguments. While starting new project don't spend too much time discussing or blocking people. Because a lot of projects will just roll and arguing about starting project in functional paradigm is most likely just cost time and brings nothing. Best tool for the job most often is the tool that team knows best.

scns 5y ago
I have to disagree and risk getting labeled a member of the Rust Evangelism Strike Force. The service at NPM and that interview with that developer at Qovery paint a different picture. (Edit) Bleacher Report replacing 150 Ruby on Rails instances by 8 Phoenix on Elixir instances would be another example.
- ozim 5y ago
  Trying not to be totally contrarian :) so with following expressions I am not a smart ass, only setting up sentences in such way to convey what I think is hard problem in delivering software. But good luck if you have 5 X(lang) developers to make that decision to go with Rust. If you have to deliver v1 of a product and have limited budget, good luck hiring 5 brand new Rust developers. What I learned as boy scout - first you have to have people that want to do the work - having loads of money can help but most of the time we don't have unlimited supply of money. Having people who want to do the job beats everything. People that are deep in tech X(or lang) rarely switch to something else and then you still have to take into account that they will write X in Rust which might not be the best way of doing things. On the other hand if we assume spherical cows or unlimited budgets/unlimited time frames for a project - we can discuss getting X devs to write in Y language.

3 ms·

I think that is an important blog post. My idea for approach is to discuss those things on forums on the internet - at work on coffee breaks. Just to challenge

by ozim 5y ago

scns 5y ago
I have to disagree and risk getting labeled a member of the Rust Evangelism Strike Force. The service at NPM and that interview with that developer at Qovery paint a different picture. (Edit) Bleacher Report replacing 150 Ruby on Rails instances by 8 Phoenix on Elixir instances would be another example.
- ozim 5y ago
  Trying not to be totally contrarian :) so with following expressions I am not a smart ass, only setting up sentences in such way to convey what I think is hard problem in delivering software. But good luck if you have 5 X(lang) developers to make that decision to go with Rust. If you have to deliver v1 of a product and have limited budget, good luck hiring 5 brand new Rust developers. What I learned as boy scout - first you have to have people that want to do the work - having loads of money can help but most of the time we don't have unlimited supply of money. Having people who want to do the job beats everything. People that are deep in tech X(or lang) rarely switch to something else and then you still have to take into account that they will write X in Rust which might not be the best way of doing things. On the other hand if we assume spherical cows or unlimited budgets/unlimited time frames for a project - we can discuss getting X devs to write in Y language.