3 ms·

I'm still waiting for Web Based interfaces to catch up to where we were with Visual Basic 6 and/or Delphi decades ago. It seems like this is a hint to move in a

I'm still waiting for Web Based interfaces to catch up to where we were with Visual Basic 6 and/or Delphi decades ago. It seems like this is a hint to move in a better direction. Today I learned what a Web Component was, and there's a lot more boilerplate and manual copying of properties than I'd like, but it seems better than digging around in the DOM with JavaScript. You all have my sympathy. It would be so much easier if we could just run mobile code without having to worry about all of the side effects it could cause. (Including the extreme side effect of taking out our systems completely).

zanellato19 3y ago
> I'm still waiting for Web Based interfaces to catch up to where we were with Visual Basic 6 and/or Delphi decades ago. It seems like this is a hint to move in a better direction. This is pure insanity, we left those in the dust decades ago. Those were horrible interfaces.
jwells89 3y ago
As someone who’s only dabbled in “modern“ front end (mainly a small project built with web components, my bread and butter is native desktop/mobile), I can’t help but think what continues to hold the web back from achieving something like VB6 is its batteries-not-included nature. As long as it’s necessary to re-invent wheels by building basic widgets from scratch, there’s going to be limits to how good the developer experience of front end web can be, as well as high churn because the common base that’s being built upon is so tiny. It’s like building a skyscraper atop of a food cart: technically possible, but all “solutions” are so stilted and full of trade-offs that there can be no consensus and inordinate amounts of energy get burned on constant re-engineering of the stilts.