7 ms·
The trouble with Salesforce is that it’s turned into the very thing they set out to replace. It’s big, unwieldy, clunky, and frustrating to use. It’s “SaaS” wh
by JCM9 5y ago
The trouble with Salesforce is that it’s turned into the very thing they set out to replace. It’s big, unwieldy, clunky, and frustrating to use.
It’s “SaaS” which was an upgrade on what they replaced initially, but seems like they’re increasingly the ones bound to be “disrupted.”
- Firehawke 5y agoScope creep from hell.
- joshribakoff 5y agoRetool recently released “modules”, and it made me think the same thing, that this is one step closer to the thing they’re trying to replace. Resolving merge conflicts in json (which is what defines a retool app) is another area where the benefits of “yes code” become more obvious. “No code” is not something I’m convinced is good. I personally think embracing code (but making it optional) leads to a platform more developers would enjoy To pick on salesforce a bit, notice how the example of how to define the drop down they are using XML. That’s not “no code”, it’s just a constrained form of coding. Basically any library or framework that embraces code can also offer higher level abstractions just like Retool or Salesforce, without having to have the “no code” part to solve the problem. “No code” is also tangential to being a saas product, these tools could work more like codesandbox than dreamweaver or frontpage, for example.
- CRConrad 5y agoBut was one supposed to write that code in the example oneself? I thought it showed code generated by this venerated "no-code" tool... If that's not the case, then the whole "no-code" moniker is marketing BS.