Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Signet: Sign your work in the development console

github.hubspot.com

Post reply on HN
Print view View original

11–20 of 20 posts

Re: Signet: Sign your work in the development console

#11

Post by asperous »

afschwartz wrote: post #9
morgante wrote: post #5

I don't get the point of this. Why would I include additional JS on the page just to add something to the developer console?

It provides a way for developers to communicate with each other in a developer channel. Wouldn't it be both exciting and useful to be able to open the console of nearly any site and immediately get a link to the code or author on GitHub? Sometimes these sorts of links aren't appropriate on the site itself, especially in the case of contract/client work. That being said, performance is very important. Which is why we…

There's also this: http://humanstxt.org/, which similar to this, only it's completely browser compatible, accessible, scrapable by crawlers, easier to read, has no effect on page load times/bandwidth.

Not to take away from your work, I think it's interesting and well made. It does adds something to your sites (like an Easter egg, like putting comments in the html source).

Re: Signet: Sign your work in the development console

#12

Post by afschwartz »

asperous wrote: post #11
afschwartz wrote: post #9

Earlier quoted context omitted.

It provides a way for developers to communicate with each other in a developer channel. Wouldn't it be both exciting and useful to be able to open the console of nearly any site and immediately get a link to the code or author on GitHub? Sometimes these sorts of links aren't appropriate on the site itself, especially in the case of contract/client work. That being said, performance is very important. Which is why we…

There's also this: http://humanstxt.org/ , which similar to this, only it's completely browser compatible, accessible, scrapable by crawlers, easier to read, has no effect on page load times/bandwidth. Not to take away from your work, I think it's interesting and well made. It does adds something to your sites (like an Easter egg, like putting comments in the html source).

I think that's a fair point. humans.txt is fantastic.

However, the small cost you pay for including Signet gets you a more convenient and more discoverable way for a developer visiting your site to learn about you, the author. Is the cost worth that slight convenience? Definitely a toss up and will depend on the application and its needs.

Re: Signet: Sign your work in the development console

#13

Post by morgante »

afschwartz wrote: post #9
morgante wrote: post #5

I don't get the point of this. Why would I include additional JS on the page just to add something to the developer console?

It provides a way for developers to communicate with each other in a developer channel. Wouldn't it be both exciting and useful to be able to open the console of nearly any site and immediately get a link to the code or author on GitHub? Sometimes these sorts of links aren't appropriate on the site itself, especially in the case of contract/client work. That being said, performance is very important. Which is why we…

To enable this, you're asking developers to add a meta tag.

Given that the audience for this output is fellow developers, I'd think we're all capable of reading the meta tag directly without the need for an additional script.

5kb might not seem like much, but where speed is of importance every request counts and every byte matters.

EDIT: Sorry if I seem too negative. It's a cool hack and I can see why it'd be fun to add to personal websites.

Re: Signet: Sign your work in the development console

#16

Post by koudi »

Sorry, but this is IMHO useless. It doesn't work in all browsers (and causes errors/warnings in those unsopported), requires extra javascript and adds no real value. It just crams console with irrelevant data. There are better ways for this - humans.txt or html meta tags.

Re: Signet: Sign your work in the development console

#18

Post by graue »

peter-fogg wrote: post #2

Doesn't seem to be working in Firefox 25 on OS X. [00:06:34.535] SyntaxError: Using //@ to indicate source map URL pragmas is deprecated. Use //# instead @ http://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js:1 [00:06:35.468] Use of Mutation Events is deprecated. Use MutationObserver instead. @ chrome://divxhtml5/content/script.js:109 Chrome is good, though.

Huh. After trying this in Chrome it seems a lot less pointless. I wondered why you needed a JS library just to console.log a list of strings :)

(Apparently they modified it to degrade to that after you posted.)

Re: Signet: Sign your work in the development console

#19

Post by atesti »

Can someone explain what the technical important point is? It looks to me that console.log is capable of logging not just plain text, but even images (they inlude data-urls for a github icon). Is it complicated to do this?

Edit: I'll answer my own question: https://developers.google.com/chrome-developer-tools/docs/co...

They use the %c control character in the log message to emit css, including embedded icons

Re: Signet: Sign your work in the development console

#20

Post by zackbloom »

peter-fogg wrote: post #2

Doesn't seem to be working in Firefox 25 on OS X. [00:06:34.535] SyntaxError: Using //@ to indicate source map URL pragmas is deprecated. Use //# instead @ http://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js:1 [00:06:35.468] Use of Mutation Events is deprecated. Use MutationObserver instead. @ chrome://divxhtml5/content/script.js:109 Chrome is good, though.

I'm pretty sure neither of those errors are coming from signet.
Post reply on HN