I don't really understand where is this need to compress the logic into where small chunks comes from. In result we get single line of code which has multiple statement conditions, different paths, and it's not possible to grasp in one go.
Other practical example why ternary is bad: Many code-coverage solutions break on ternary because they don't correctly see that one of the branches was missed in tests.
I don't think rewrite the in Scala was great decision, business wise. Fast forward 15 years its way lower on popularity than Ruby. Not sure what they use these days though.
Results from outsourcing can vary. You might end-up with totally unmatched 5 candidates and complain that there is no good people on the market. How would asses that the agency did good job (or any job at all)?
Types are helpful in large codebases, but in Web Apps they tend to get into the way more than they help. You can still use semi-typed constructs in Ruby, but you have the freedom to choose where you need them.
After moving to writing web in Go (from Ruby) I am still baffled how much more boiler plate there is and how much slower things move because of this. Types are great when you want to refactor some things, but thats just part of the job.
In Ruby I loved how can you just quickly jump into REPL or just do inline breakpoint to inspect state: `scope.map(&:names).last.tally.sort_by(&:last).reverse.first(10)`
Something like this is such a chore in Go that I simply skip it more often than not.
> it uses a lot of special characters, which makes writing the code slower
Could you point out where do you get your data from? Anything to back-up your claims that Rails is in decline and Elixir/Phoenix is growing? For a time not long ago I was heavily into looking for an Elixir gig, but couldn't really find offers, while there were still tons of offers for Rails development.
This project pretty much pivoted into https://dragonruby.org, a framework for making 2d games in Ruby. It's pretty active and in-development, but has nothing to do with building cross-platform apps per se. No idea why this was posted.
I do ask this question in a initial questionnaire. I list bunch of technologies and just require this input. I do agree with all the points in the article, but my goal is to have relative scale. I am not able to verify all the needed technologies, but I can do verify few. Whatever the scale candidate choose, I assume its consistent. If someone self-scores 9/10 out of Postgres and doesn't understand basic things, I can safely assume his other 9/10 are worthless.
Despite their shady practices I still only book through Booking.com when I to unknown places for the firs time. At the end of the day Booking sticks to customers when theres an issue and all the Venues/Hotels seem to care about their relation with Booking.
Other practical example why ternary is bad: Many code-coverage solutions break on ternary because they don't correctly see that one of the branches was missed in tests.