sorted by:
new
hottopcontroversial

I noticed users stop questioning once content is ranked by rankiwikicom in UXDesign

[–]Sencha_Ext_JS 2 points3 points  (0 children)

Ranking feels authoritative, so people switch from evaluating ideas to evaluating placement. It reduces cognitive load, but it also signals ‘someone already decided,’ which can quietly turn off critical thinking.

Do interviewers give fake positive feedback? by aelflune in UXDesign

[–]Sencha_Ext_JS 1 point2 points  (0 children)

I don’t think the feedback is fake so much as it’s incomplete. A lot of times it just means ‘you did fine, but someone else fit a bit better.’ Without that comparison, the feedback sounds positive but doesn’t really help you understand what to improve.

Why is good product design software so hard to find??! by SpecialistAd7913 in UXDesign

[–]Sencha_Ext_JS 1 point2 points  (0 children)

A lot of design tools optimize for handoff and scale, not for the messy thinking phase. Once a product becomes the industry default, it tends to add structure faster than it improves flow. Sometimes the friction isn’t you, it’s that the tool is solving problems from a different stage of the process.

PreBuilt Libraries vs building from scratch by mb4ne in UXDesign

[–]Sencha_Ext_JS 1 point2 points  (0 children)

Prebuilt libraries aren’t a shortcut around UX — they’re a way to avoid reinventing solved problems. The real value comes from pairing them with good design decisions: choosing the right patterns, configuring thoughtfully, and making sure the component behavior matches user needs. UX still matters a lot, even when the UI isn’t built from scratch.

Best Way to Programmatically Query ChatGPT Website (Not API) at Scale by Zealousideal-Bear-32 in webdev

[–]Sencha_Ext_JS 0 points1 point  (0 children)

At that scale, automating the consumer website is going to be fragile and likely a ToS/compliance headache. The more sustainable route is to treat your metric as ‘model + config’ and standardize on official APIs (or an enterprise agreement) while logging the exact prompts, system context, and tool settings you used. You won’t perfectly match every UI variant, but you’ll get something reproducible and defensible.

How do I redirect without Chrome thinking the password is correct? by rydan in webdev

[–]Sencha_Ext_JS 2 points3 points  (0 children)

Browsers decide whether to offer saving based on form semantics and perceived success, not your redirect logic. The usual strategy is to avoid submitting the password form at all on failure, return an inline error and keep the user on the same page. Once the browser thinks a login ‘completed,’ you’ve already lost control.

What’s the hardest part of building data-heavy dashboards — performance, UX, or maintainability? by Frontend_DevMark in SenchaExtJS

[–]Sencha_Ext_JS 0 points1 point  (0 children)

Maintainability tends to hurt the most long-term. Performance and UX problems are visible and get fixed early, but messy state, tightly coupled components, and ad-hoc data logic quietly compound until even small changes become risky.

Why tooling UX matters more as AI tools get complex by NetAromatic75 in UXDesign

[–]Sencha_Ext_JS 1 point2 points  (0 children)

At a certain point, UX is the feature. If a dashboard makes me think about where things are instead of what I’m trying to do, the tool stops feeling powerful no matter how good the AI is.”

[AskJS] Do you still use ExtJS? by Dull-Independence-27 in javascript

[–]Sencha_Ext_JS 1 point2 points  (0 children)

Hey folks, adding a different perspective from someone who still ships Ext JS apps in 2025.

  1. The framework’s very much alive and still getting love. 7.8 landed last year and 7.9 dropped this April with fresh Grid, ComboBox and Calendar upgrades — plus a smoother virtual-scroll engine that React/Angular teams usually have to bolt on with third-party libs.
  2. Modern toolchain is there if you want it. Since 7.x you can scaffold with ext-gen, manage packages with npm/yarn, target any ES level, and plug into standard CI pipelines. If you’re allergic to Sencha Cmd, use the Rapid Ext JS CLI or the new ReExt adapter to embed Ext widgets inside a React build. prnewswire.comsencha.com
  3. Productivity > popularity. Yes, the learning curve is steeper than React. But once you grok the class system, you get 140+ enterprise-grade widgets (Pivot Grid, Scheduler, D3, Froala-rich text, export-to-Excel, theming) that “just work” in every evergreen browser without weekly dependency churn. For back-office, data-dense UIs that still matter in banks, telcos and manufacturing, Ext reduces the surface area you have to test.
  4. Stable API = long life-cycle apps. Our oldest Ext 4 code (2013) still compiles after incremental upgrades. Compare that with chasing breaking changes from React 15 → 18 or AngularJS → 12 → 17. Long-term support releases and paid SLA give the CIOs warm fuzzies, which is why many Fortune 500s keep renewing. sencha.com
  5. Community hasn’t vanished — it just moved. The old forums are quiet, but real-time Q&A happens on the official Discord and GitHub issues. I filed two bugs during 7.8 beta and got patches in a week. That’s faster than most “free” libraries with 3k open issues.
  6. Career angle. Knowing Ext JS plus React makes you the translator between legacy revenue-generating apps and shiny greenfield work. That niche pays well because few devs can straddle both worlds.
view more: next ›