Live data from Hacker News

Comments by a developer inside the Windows Media Player source code

pastebin.com

41–50 of 135 posts

Re: Comments by a developer inside the Windows Media Player source code

#41

This is why I love open source. In LibreOffice, cruft like this is often removed due to the embarrassment factor.

Indeed. One of the first things I did after adopting a package was remove a well understood and unnecessary exploitive. One person noticed and gave it the looking eyes emoji.

Re: Comments by a developer inside the Windows Media Player source code

#42

Earlier quoted context omitted.

It was removed from Microsoft code too. This is an old snapshot of the code, almost two decades old. Since the 2002 TWC initiative, anything from easter eggs to things like that are all very strongly banned, and actively get removed as they're discovered.

Not surprising. No fun is allowed anywhere anymore. just dull flat interfaces with grey and black colors. people can say what they want about windows xp and vista but they had soul. todays OSes are souless. Looking at you windows 10..

Looking at you Reddit...

Re: Comments by a developer inside the Windows Media Player source code

#43

Earlier quoted context omitted.

Knowing developers who choose to write above an 8th grade reading level for no reason... they used that word to feel superior and make everyone who reads it feel stupid.

Your comment says more about you than the author. It was a rarely-used but well-known word in use in school in the 80s and 90s.

It's used in the Paul McCartney song "Famous Groupies" (on the 1978 Wings album "London Town").

Re: Comments by a developer inside the Windows Media Player source code

#44
post #21

Earlier quoted context omitted.

Neither does YouTube, likely the most popular video playing entity today, respect the spacebar on iOS.

I think you’re mistaken, YouTube (in all the forms I use it with a keyboard at least) supports spacebar as a pause key. Your browser might try to pop you down half a page if the thing that is selected or highlighted on the page is not the video player itself though. But it works 100% of the time in fullscreen.

Youtube itself changed the space bar behavior from context specific (pause if player in focus, scroll of comment in focus) but they rolled that back so space is always pause.

I like the context sensitive behavior and wrote a grease mo key script to restore it.

Re: Comments by a developer inside the Windows Media Player source code

#45

The bug here is in media player to listen on key-up events. Mouse-button-up makes sense because the user can move the mouse to cancel the click. But key events should be on key-down and that's how it is done most of the time. So if you use key-up you run into these problems.

> But key events should be on key-down Why? I like how keyup is less ambiguous: it avoids the question “what do I do if the user is holding the key down?” I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply. For video editing mainly. I’m not saying keyup is the only answer. Just that there isn’t one obvious answer.

Keydowns have the physical button analogue: when you press a physical button, it immediately closes the contact, it doesn't wait until you lift your finger again.

Not saying key down is better than key up, there are certainly arguments for both.

Re: Comments by a developer inside the Windows Media Player source code

#46

This is why I love open source. In LibreOffice, cruft like this is often removed due to the embarrassment factor.

It was removed from Microsoft code too. This is an old snapshot of the code, almost two decades old. Since the 2002 TWC initiative, anything from easter eggs to things like that are all very strongly banned, and actively get removed as they're discovered.

I assume in the modern day of git and code review on commit diffs, its harder to slip things in than it was in the 90's.

Re: Comments by a developer inside the Windows Media Player source code

#47

One of the ugly hacks you do in SAP to make it work is reading/changing variables and structures inside the SAP standard code because there is no API exposing them. It is blessed officially as doing a "dirty" assign.

> there is no API exposing them.

If there's no API exposing them but there's a way to make use of the internals with a dirty assign then sounds like the internals are now part of the API.

Re: Comments by a developer inside the Windows Media Player source code

#48
post #41

This is why I love open source. In LibreOffice, cruft like this is often removed due to the embarrassment factor.

Indeed. One of the first things I did after adopting a package was remove a well understood and unnecessary exploitive. One person noticed and gave it the looking eyes emoji.

> well understood and unnecessary exploitive

Probably not what you intended to say. "Expletive" or "exploit"?

Re: Comments by a developer inside the Windows Media Player source code

#49
post #21

Earlier quoted context omitted.

Neither does YouTube, likely the most popular video playing entity today, respect the spacebar on iOS.

I think you’re mistaken, YouTube (in all the forms I use it with a keyboard at least) supports spacebar as a pause key. Your browser might try to pop you down half a page if the thing that is selected or highlighted on the page is not the video player itself though. But it works 100% of the time in fullscreen.

YouTube's keyboard handling is Insanely Intuitive™, I must absolutely agree.

Usefully, the up/down keys don't change the volume unless the player is also focused.

What's incredibly sad is that j/k/l were agreed upon to rewind/pause/forward the video, and these generally work unless you're in a textbox... but dedicated keys were not similarly approved to control the volume.

--

My current winner for Absolutely Favorite Piece Of YouTube-Related Keyboard Functionality©®℠ is...

YouTube Music (https://music.youtube.com/)... which uses a different set of fundamental keyboard shortcuts to YouTube. [;]=pause, [j]=next, [k]=prev, [l]=forward, [h]=rewind.

There are two disasters here.

The first is that == . "Nooooo! I was 2 hours?? and how many seconds??? into this video... >.The second disaster is that it's obvious a Vim user clearly argued successfully for Music to use Vi-style hjkl, but both the key choices and how they are presented in the UI could not be less intuitive, regardless of whether the user also uses Vim or not.

I copied above exactly how the UI (in the [?] popup) lists the sequence. Specifically, the whole thing is shifted left by 1 position, wrapping [h] around to the right. Fixing that to show the sequence how a Vim user would expect, it looks like: [h]=rewind, [j]=next, [k]=prev, [l]=forward.

But then, any Vim user is going to be utterly confused by this sequence, not only because of the mild readjustment of assigning up/down to prev/next and left/right to seeking - but because Vim "up" [j] is assigned to "next", and Vim "down" [k] is assigned to "prev".

Upside down playlist much?!?!

I no longer use YouTube Music, solely because of the number of long videos I have rewound and lost my position in.

I'm also incidentally trying to passively commit hjkl to memory (you know, the whole spaced repetition thing), and all the above was just too confusing.

Re: Comments by a developer inside the Windows Media Player source code

#50
post #38

Earlier quoted context omitted.

I’m not sure what you’re trying to say here; pulchritude twice as rare as disharmonious, which is relatively rare. It’s an order of magnitude rarer than effervescent, as an example, which is a word I would consider uncommon but in most people’s vocabularies. And given how much more common pulchritude is - surely physical beauty is one of the most common subjects in any language - while disharmony and effervescence ar…

Except that pulchritude beats disharmonious for over a hundred years. And even now, it’s half as common as disharmonious, which is a commonplace word. But if you think that a word like “disharmonious” is in any sense rare, then I don’t think I can convince you with data.

When compared to "harmony" usage of the other words is basically zero. Harmony is a common word, and it is the root which makes "disharmonious" easy to understand despite its extreme rarity.

Even "disharmony" is far more common than "disharmonious."

Post reply on HN