Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Progress Software to Acquire Telerik for $263M

online.wsj.com

Post reply on HN
Print view View original

11–20 of 58 posts

Re: Progress Software to Acquire Telerik for $263M

#11

Post by aswerty »

emp_ wrote: post #9
ninv wrote: post #6

Telerik makes awful .Net components. I have used them in past. I was frustrated with their breaking changes, they had the worst release management. Every year they used to release new version and used to outright removed the methods or replace the signatures. No Deprecation!

In the past 8 years I've been involved in more projects to remove Telerik than to use it. The performance and long term maintenability of these drag and drop with no code! components are never well advertised. But I guess it solved a massive issue when companies thought design was cheaper with a consistent skin, forgetting that their programmers would still need to layout everything.

I'm using the Telerik Reporting product. I have to agree that the promoted drag and drop approach is pretty pathetic. Though using it at a programmable level hasn't been too bad. I've been able to do most things I've needed to do without too much heartache.

Re: Progress Software to Acquire Telerik for $263M

#12

Post by astral303 »

ninv wrote: post #6

Telerik makes awful .Net components. I have used them in past. I was frustrated with their breaking changes, they had the worst release management. Every year they used to release new version and used to outright removed the methods or replace the signatures. No Deprecation!

I've had good luck using their Kendo UI Web components in an Angular context. Their Grid component is hard to beat.

Re: Progress Software to Acquire Telerik for $263M

#14

Post by the_ancient »

fit2rule wrote: post #4

This is a fascinating move for Progress Software, who seem to have managed decades of survival through the onslaught of SQL and MySQL/Postgres cutting into their market .. and so to see them acquiring Telerik now is really interesting. Progress were, once, one of the major players in the database space (and still are in many vertical markets) so it could really be an interesting development to see them rise again. Co…

They survive because of vendor lockin, too many companies have years or decades of work in to using that system and it would be far too costly to move.

If your starting a project from scratch today you are not using progress, Legacy is their only business.

They know it, which is why they are buying up companies like this.

Re: Progress Software to Acquire Telerik for $263M

#18

Post by andwaal »

ninv wrote: post #6

Telerik makes awful .Net components. I have used them in past. I was frustrated with their breaking changes, they had the worst release management. Every year they used to release new version and used to outright removed the methods or replace the signatures. No Deprecation!

I have to strongly disagree. I have used their Sliverlight components in every SL project I have been involved with for the last four years and I could`t live without them. They are professional components for enterprise which does something that a open-source project could seldom( maybe never) do, support all the odd-cases needed. These are all the weird cases that no one would bother to implement in an OS-project, since it`s very seldom needed, but since they know that their customers might need this functionally they have already implemented it. Just look at the feature list for their GridView component for SL and try to match that with an OS-project. Combining this with good support and you got a winner.

As a result the good experiences I had with their components in a SL context I am know adopting their KendoUI components together with ReactJs. So far all the points made above for SL still stands for KendoUI.

Re: Progress Software to Acquire Telerik for $263M

#19

Post by hipsterrific »

Telerik wasn't half bad when I was the only .net developer for a hospital system with 3,000 employees. It made short work for me since building AJAX-y controls meant less time building business rules.

The controls are really bad, they produce a lot of awful JS. Also, with newer frameworks such as angular, knockout, ember, et al...building reusable JS components got simpler. I haven't yet used KendoUI but haven't had a need too, building my own was far more fun (and with OData, not that much time either).

I did use their reporting product a lot but even that was too heavy and cumbersome.

Post reply on HN