Personally I don't care about speed for this category of language. I just bring it up because Python is one of the most used languages, is even slower, yet that's never held against it. Just seems like a lazy way to dismiss Ruby. Yeah, it's not as fast as C, Go, Rust or Java. Everyone knows and raw speed obviously isn't the point of a dynamic scripting language...
Python is one the most popular programming languages. Ruby fits into a similar category as Python (high level, interpreted scripting language, very dynamic, has a rich ecosystem with tons of existing code). Being faster than Python makes it more attractive to use, or port Python codebases to.
And with Java, and with Go, and with Rust, and with pretty much any language offering some form of FFI.
But they're used with Python, and good luck convincing your interviewer that it should be used with Ruby.
In what other language is MVT offered other than Python? That seems like a good example of unique language specialization and not reflective of a Ruby gap relative to any other language. I also don't think that's something you'd bundle & reuse in another offering. In my opinion that's the primary value proposition of building within an ecosystem
These are great suggestions:
1. Clean up your component structure
2. Document with machines in mind
3. Sync with your dev team on structure
4. Start small with one component
Luckily, there is Ember.js, which provides the best developer and user experience for a decade now, with smooth and consistent update and improvements.
Still the best choice for huge, corporate frontend projects.
The problem is, it's not just Apple, the entire software industry has taken a turn for the worse. Everything has automatic updates these days: my phone, my watch, my computer, my TV, my car, and every single app I use on these platforms, and they are constantly breaking stuff, undoing functionality, loosing data and occasionally ruining devices permanently. I've been on the other side of these things too, with panicked-laden all night coding sessions trying to fix a bad update that went out. I've been in the software industry for almost 25 years now, I'm not sure what the answer is but the direction things have gone is unacceptable.
Actually you can use the whole attribute name as selector, like data-test-user-name-input, and if you need a dynamic id, you can add as a value: data-test-product-item="book" ;)
