WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2026 Poal.co

193

I looked at chatterbot and then looked at botframework. Chatterbot takes seconds to setup and looks easy enough to work with assuming you have the space for the model. BotFramework looks like this almost cryptic pile of crap which makes zero sense, and it uses a custom model, or custom adapters which makes it a pain in the ass to load date into it without writing custom adapter code. Like why cant they just make stuff simple, instead of overcomplicating crap?

I looked at chatterbot and then looked at botframework. Chatterbot takes seconds to setup and looks easy enough to work with assuming you have the space for the model. BotFramework looks like this almost cryptic pile of crap which makes zero sense, and it uses a custom model, or custom adapters which makes it a pain in the ass to load date into it without writing custom adapter code. Like why cant they just make stuff simple, instead of overcomplicating crap?

(post is archived)

[–] 3 pts

If you keep going with "chat products" like i started with, google has had about 6 different ones over the years (chat, hangouts, wave, duo, etc.). Chat is very basic, people send a chunk of data, and the company records that data and forwards it to other people. Google has never even come close to the functionality we had with icq back in the 90's. The problem is that to introduce a product it has to go through many levels, then those levels come back with "business requirements" and then all the levels (and horizontal entities) have to discus and figure out the final requirements, and then they go into production.

What you end up with are things like "not able to use on a computer", and then it doesn't get traction. duo could have been the product people used instead of zoom; many companies/schools have google contracts, most people have google accounts, most people have android phones, but their product didn't have basic features that would allow it to be used for basic video chat.