3 ms·

I think that if you want a page to impress or make a splash then sure, you always have to move to the next greatest thing, however, I don't work for them but I'

I think that if you want a page to impress or make a splash then sure, you always have to move to the next greatest thing, however, I don't work for them but I've paid for Telerik Kendo Controls (the react ones specifically)since they were released, before then, the AngularJs ones and it's been great - it keeps my (albeit internal app) UI development stable, fast and looks great with minimal fussing about. It's been years now and it feels very stable and quick. The switch from AngularJs to React was the only unstable part, but it was at an inflection point in the number of apps I had to support and develop, so the change was actually welcome. YMMV (edit - I just realized I spent the weekend experimenting with MAUI, so I'm full of it)

Etheryte 4y ago
I had to read your comment twice to be sure we're talking about the same Kendo. I've consulted for a number of companies over the years who have used it (or tried to use it), ever since the jQuery version to up until now, and it's always been pure pain. I understand how their components work, I understand the underlying architecture because I've stepped through it too many times with a debugger, and I still always fail to understand how they have any happy customers. Perhaps there is a good experience to be had if you only use the components exactly the way the documentation examples use them, but the moment you step outside that narrow path, things fall apart. Never mind custom code, simply using two different components from their library together doesn't even always work. The first time I had a bout with Kendo was some odd ten years ago, and then I was sure it was simply me not understanding the framework. After all, every component library has its own kinks and it takes a while to get up to speed. After seeing them again and again many times over the years, I've changed my opinion. In my eyes, Kendo is what I like to call an MBA trap. It ticks all the boxes that an MBA manager going by a feature checklist is looking for, but under the hood it's garbage software. I'm glad you've had a good experience, at the same time I don't think I will ever stop recommending everyone to stay away from Kendo.
- bigmattystyles 4y ago
  I don't agree with you but I don't disagree either. Our use cases are very vanilla, and now that I have quite a bit of sway in my team, when people deviate from the showcased Kendo way, I push back and see if the desired way deviating from Kendo is a necessity or a nice to have. If it's the former, we sometimes have the experience you described, though I've often be helped by stackoverflow, their forums or Kendo's support team. (We pay for the 24 hour tier). If it's the latter then I force the Kendo way. FWIW, their ODATA v4 support OOTB with dotnetcore webapi with its ODATA v4 out of the box with an EF model is the perfect pattern for most of our use cases. But again, I don't disagree with you either - but I would stress that any alternatives I've seen have their same range of issues.
  - syntaxfree 4y ago
    You’re glowing, man.
    - deleted 4y ago
      [deleted]
    - bigmattystyles 4y ago
      I moisturize nightly.

Etheryte 4y ago

I had to read your comment twice to be sure we're talking about the same Kendo. I've consulted for a number of companies over the years who have used it (or tried to use it), ever since the jQuery version to up until now, and it's always been pure pain. I understand how their components work, I understand the underlying architecture because I've stepped through it too many times with a debugger, and I still always fail to understand how they have any happy customers. Perhaps there is a good experience to be had if you only use the components exactly the way the documentation examples use them, but the moment you step outside that narrow path, things fall apart. Never mind custom code, simply using two different components from their library together doesn't even always work. The first time I had a bout with Kendo was some odd ten years ago, and then I was sure it was simply me not understanding the framework. After all, every component library has its own kinks and it takes a while to get up to speed. After seeing them again and again many times over the years, I've changed my opinion. In my eyes, Kendo is what I like to call an MBA trap. It ticks all the boxes that an MBA manager going by a feature checklist is looking for, but under the hood it's garbage software. I'm glad you've had a good experience, at the same time I don't think I will ever stop recommending everyone to stay away from Kendo.

bigmattystyles 4y ago
I don't agree with you but I don't disagree either. Our use cases are very vanilla, and now that I have quite a bit of sway in my team, when people deviate from the showcased Kendo way, I push back and see if the desired way deviating from Kendo is a necessity or a nice to have. If it's the former, we sometimes have the experience you described, though I've often be helped by stackoverflow, their forums or Kendo's support team. (We pay for the 24 hour tier). If it's the latter then I force the Kendo way. FWIW, their ODATA v4 support OOTB with dotnetcore webapi with its ODATA v4 out of the box with an EF model is the perfect pattern for most of our use cases. But again, I don't disagree with you either - but I would stress that any alternatives I've seen have their same range of issues.
- syntaxfree 4y ago
  You’re glowing, man.
  - deleted 4y ago
    [deleted]
  - bigmattystyles 4y ago
    I moisturize nightly.