Hacker Newsnew | past | comments | ask | show | jobs | submit | thrdbndndn's commentslogin

What I don't get is how the author can't pin the year down to anything narrower than "between 1994 and 1997," especially considering he wrote the article in 2002: only a few years later.

I'm not at all implying the story was fake; just this particular thing feels weird.


UX bug:

I don't use dark mode. Every time I open this site, it firstly shows in dark mode and then switches to light mode after 0.x seconds.


That’s because the HTML code is server-side rendered (SSR) with data-theme="dark" hardcoded on the <html> element, so on the initial page load the browser immediately renders with dark mode styles applied. After ± 500ms-600ms Nuxt’s JavaScript hydration kicks in (as this is a Nuxt app based on __NUXT__ at line 11,236), which detects your macOS system preference via prefers-color-scheme media query and updates data-theme to "light".


it shouldn't need to do this. Nuxt has a @nuxtjs/color-mode module which ensures that the correct colour scheme is applied before the browser starts rendering the html.

if the site author is lurking anywhere - may I recommend https://color-mode.nuxtjs.org ?


I am still checking the post, and I've already added color mode 1-2 days ago.

You can also expect some big changes to the UI very soon


This is much better than dark mode users getting flashbanged.


Not sure whether such "criticism" is welcome here, since it is ultimately subjective, but I will just be blunt and say: I disagree.

I like this style of writing as well, but I think this article overdoes it, to the point that it became somewhat irritating to read.

The part where I particularly feel this way is when the author spends two whole paragraphs discussing why YouTube (or its developers) chose to sample by "100" segments, to the extent that the author even asks, "If you work at YouTube and know the answer, please let me know. I am genuinely curious." Which, for lack of better words, I found ridiculous.


> Not sure whether such "criticism" is welcome here, since it is ultimately subjective, but I will just be blunt and say: I disagree.

If this was my post I'd certainly appreciate criticism.

> but I think this article overdoes it

Perhaps its overdone in places, to your credit the question about if 100 was an arbitrary number was a bit much. But, as a counterpoint, I found the related pondering of "might it make sense to have variable time duration windows" to be interesting. The interpolation YouTube ultimately selected is deceiving and variable density could be a way to mitigate that.

There's definitely a healthy balance and perhaps the author teeters on the verbose end, but I mostly just wanted to voice that I was surprised about the type of article it was, but not in an unpleasant way.


Criticism is definitely welcome!

You are likely right that I over-rotated on the "storytelling" aspect there. My curiosity about the "100 segments" stemmed from wondering if there was a deeper statistical reason for that specific granularity (e.g., optimal binning relative to average video length) versus it just being a "nice round number."

That said, I can see how dedicating two paragraphs to it felt like over-dramatizing a constant. I will try to tighten the pacing on the next one. Thanks for reading despite the irritation!


Windows struggles even with native apps, as soon as you have monitors using different scaling settings.

I'm currently using a laptop (1920x1200, 125%) + external monitor (1920x1080, 100%) at work. The task manager has blurry text when putting in the external monitor. It is so bad.


Yep, I've been running a Windows laptop plugged into a pair of monitors for the past ten years at work, and across multiple laptops and from Windows 10 to 11, this has always been a problem. If I undock to do some work elsewhere and come back, I either have to live with a bunch of stuff now being blurry, or I need to re-launch all the affected programs.

I also have programs that bleed from one monitor onto another when maximized. AutoCAD is one offender that reliably does this -- if it's maximized, several pixels of its window will overlap the edge of the window on the adjacent screen. The bar I set for windows is pretty low, so I'm generally accepting of the jank I encounter in it vs Linux where I know any problem is likely something I can fix. Still, that one feels especially egregious.


The new Windows 11 22H2 task manager?

Works just fine here (1920x1200 125%, 4K 150%, 1080p 100%).


Usually that is a monitor driver issue.


It's not, here is a good article about it: https://gist.github.com/valinet/d66733e5f1398856bb21bda466a2...

(And a workaround).

Unfortunately I cannot modify registry at work so I have to live with it.


I'm sure Markdown was already popular, but I agree with the OP that GitHub made it orders of magnitude more popular.

Previously its popularity was somewhat similar to RST.


Your link is wrong. It must be lower case .json.



Is the article itself written by the manufacturer or a 3rd party? It keeps saying "we ..." but then also "[i]t seems that ...".

Edit: apparently the site is translated from its original Japanese version, which explains these weird wordings.

The original article is here, which has more pictures too: https://audio-heritage.jp/DIATONE/diatonesp/d-160.html


What is "skill entropy"


> What is "skill entropy"

Skill entropy is a result of reliance on tools to perform tasks which otherwise would contribute to and/or reinforce a person's ability to master same. Without exercising one's acquired learning, skills can quickly fade.

For example, an argument can be made that spellcheckers commonly available in programs degrade people's ability to spell correctly without this assistance (such as when using pen and paper).


I did mean "atrophy" as others mentioned.


atrophy?


They think it's a smart way to say that the o.p. is dumb.


Nope, skill atrophy can affect anyone at any level.


I would like to read the original Chinese version as a native speaker. Is there any chance you post that (the article itself) too?



Wow, thanks. I vaguely remembered reading something about this years ago on Zhihu, and I didn't even realize it was the same article!


it's extremely slow and throws 502 from time to time, but not entirely unreachable here.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: