Well, that didn't take long: within a week of applause for Microsoft's decision to open-source PowerShell, a comment-war has broken out over
curl
andwget
.For those not familiar with these commands: they're open source command line tools for fetching Internet content without a browser. Apart from obvious applications like downloading whole sites (for example as backup), they're also under the hood for a lot of other toolsets (an example the author is familiar with – GIS tools use
curl
and/orwget
to fetch maps from Web services).For some reason, Microsoft's team decided to put aliases for
curl
andwget
in Windows PowerShell – but, as this thread begins, those aliases don't delivercurl
andwget
functionality.The pull request says the aliases should be spiked: "They block use of the commonly used command line tools without providing even an attempt to offer the same functionality. They serve no purpose for PowerShell users but cause confusion and problems to existing
curl
andwget
users."
-- submitted from IRC
(Score: 2) by Marand on Wednesday August 24 2016, @06:05AM
It's easier than that. If you look at a comment's heading, it says something like "$NAME commented $TIME ago", right? The $TIME portion of that heading is a link to that specific comment.
It just has absolutely no visual indication that it's a link because Github's designers all became pants-on-head retarded at some point. Which is also why everything on Github is bold for me in Linux, because they did a terrible hackjob attempt at using "system fonts" by default, and as a result, it defaults to using Roboto because I happen to have it installed...
(Score: 2) by NotSanguine on Wednesday August 24 2016, @08:06AM
Even better! Thank you kindly, sir or madam.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 3, Funny) by NotSanguine on Wednesday August 24 2016, @08:09AM
It's better because now I know how to link to specific comments. But you're right, the design (if you can call it that) is quite poor.
How does that old saw go again? "I may be slow, but my work is poor." Yes, I think that's it.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 2) by Marand on Wednesday August 24 2016, @12:37PM
Glad I could help.
Seems like lately Github's website is more trouble than it's worth. Some random things that come to mind:
• The poorly displayed comment links that require treating the webpage like an old-style adventure game where you blindly hover over anything that might be interesting in the hopes of finding the macguffin needed to continue
• Huge waste of space on comments for the damn +1 emoji bullshit
• If you're viewing a repository, the search box now searches within the repository, with no clear way to search site-wide again. Know how you do it? You hit backspace on the empty search box... How's that for fucking stupid, hidden, magic UI bullshit?
• The Roboto thing I mentioned, where it tries to use system fonts and ends up looking weird. The actual problem is that the CSS used for text now is -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";, in a misguided attempt to use system-default fonts instead of browser-defaults. So, if you happen to have a font installed that's from a different system that's closer to the head of the list, you get that font. Here's what it looks like, [imgur.com] along with my Stylish tweak to make it tolerable again on my system.
Probably more, but I usually interact with github through git on the CLI, thankfully. They really went all-in on the "social" bullshit and seem to be determined to make the site as uncluttered and usable as Facebook.
(Score: 0) by Anonymous Coward on Wednesday August 24 2016, @05:58PM
Yeah, the method I described -should- work, even on pages when there is no obvious thing to click (in this case, the date within each post).
We should note here that some page "developers"[1] don't understand the concept of accessibility[2] and especially not the concept of a #FragmentIdentifier.
In the article which spawned one of my recent submissions [soylentnews.org] I found one of those.
In those cases, I add a critique to the URL [insidehighered.com]
(and the editors typically remove those).
[1] ...and a bunch of those "developers" just reuse someone else's page boilerplate without understanding what the tags within it do.
[2] Folks who are blind and use a text-to-audio screenreader as well as folks who use a text-only browser really hate those poorly-educated guys.
(The very first thing on any page that doesn't start its main content at the very top of the page should be a Jump to content link.)
Note: I have special emotions for the guys who include one of those--and don't check to see that it actually WORKS.
-- OriginalOwner_ [soylentnews.org]