TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Is unobtrusive javascript/gracefully degradation important anymore?

11 点作者 ashchristopher超过 14 年前
Twitter's new interface doesn't degrade gracefully (thought they do link to old twitter). What are the communities thoughts on this subject? I am working on a project and I spend 60% of my front-end time making sure that it works without JS even though I have every intention of it being used with JS enabled? Is it a waste of time? Should I focus on releasing the product and to hell with degrading gracefully?

4 条评论

CPops超过 14 年前
Devoting such a significant percentage of your time and resources to what likely amounts to less than 1% of your users doesn't sound like a wise business decision in most circumstances.
评论 #2209018 未加载
评论 #2209383 未加载
grok2超过 14 年前
I think, yes, for content oriented sites (seo benefit, helps to allow people to continue to view content, etc), but if it's an app/utility site, I think there is no point in adding to your workload...
评论 #2209388 未加载
评论 #2208886 未加载
blahedo超过 14 年前
Yes it's important, no it's not a waste of time. Aside from the people who intentionally turn off JS in their browser, there are people with readers or other interfaces that don't support JS (or, not well), and most bots trying to crawl and find and possibly link to your content are going to behave, at best, unpredictably in the face of a JS-heavy site.
bmelton超过 14 年前
I suppose I'm in the minority here, but at least the way I build applications, I build in the 'vanilla' way first and foremost.<p>Submissions go to another page, as do clicks and all that jazz. It's quicker for me to get the MVP up and running first, and then later add the JS niceties.<p>Obviously, there are use cases where this is flipped around -- mapping, for example, and I'm sure many others -- but at least for me, I don't understand why it's even a hardship to make it work for nonJS users, as that's what I always build first.<p>Workflow aside, you're probably right, at least for end users. Almost every device worth supporting out there is 'modern' enough that they support jQuery, Dojo, et al.<p>The real trick is of course the other important devices that aren't users. Search engines. Crawlers aren't necessarily capable of following your application flow without graceful degradation, and in this day and age, that likely matters as much or nearly as much as actual users.