Live data from Hacker News

Chrome Extension Programming: Illustrating a Basic Survival Skill

karpathy.ca

21–25 of 25 posts

Re: Chrome Extension Programming: Illustrating a Basic Survival Skill

#21
"That’s the passive aggressive look of Twitter telling you that there are two more tweets to show, but also refusing to actually show them. That would be too useful to their users. Instead, they want you to stop what you’re doing and click the button to load the new tweets."

I dunno, I actually like that feature.

Re: Chrome Extension Programming: Illustrating a Basic Survival Skill

#22

"That’s the passive aggressive look of Twitter telling you that there are two more tweets to show, but also refusing to actually show them. That would be too useful to their users. Instead, they want you to stop what you’re doing and click the button to load the new tweets." I dunno, I actually like that feature.

Interesting, Based on my own discussions with friends and my own experience, it's considered strictly annoying and done likely to save bandwidth or something. Can you explain what you like about it?

Re: Chrome Extension Programming: Illustrating a Basic Survival Skill

#23
post #13

Earlier quoted context omitted.

You can already write dev tools extensions. Or did you mean something else? http://developer.chrome.com/extensions/devtools.html

That's cool but I meant the ability to get an idea for an extension, create it, and load it without leaving Chrome. Chrome already has Codemirror and some ability to store files using snippets, so why not extend that to create things? I realize this an exceptional use case but it'd be great to see Chrome fit Steve Yegge's QWAN concept, where one of the ideas is that a system should be modifiable and extendible withou…

Ah, now I understand. I believe the Stylebot extension lets you live-edit a page and then save the edits. Don't know about things more complicated than CSS though.

Re: Chrome Extension Programming: Illustrating a Basic Survival Skill

#24
post #23

Earlier quoted context omitted.

That's cool but I meant the ability to get an idea for an extension, create it, and load it without leaving Chrome. Chrome already has Codemirror and some ability to store files using snippets, so why not extend that to create things? I realize this an exceptional use case but it'd be great to see Chrome fit Steve Yegge's QWAN concept, where one of the ideas is that a system should be modifiable and extendible withou…

Ah, now I understand. I believe the Stylebot extension lets you live-edit a page and then save the edits. Don't know about things more complicated than CSS though.

Thanks. I'll take a look at Stylebot. I'm pretty convinced what I'm looking to do isn't possible with default Chrome, but it might be, and I'd guess that I'm not the first person to wonder this.

Re: Chrome Extension Programming: Illustrating a Basic Survival Skill

#25

"That’s the passive aggressive look of Twitter telling you that there are two more tweets to show, but also refusing to actually show them. That would be too useful to their users. Instead, they want you to stop what you’re doing and click the button to load the new tweets." I dunno, I actually like that feature.

Interesting, Based on my own discussions with friends and my own experience, it's considered strictly annoying and done likely to save bandwidth or something. Can you explain what you like about it?

I like knowing which tweets I've read. If it says that there are new tweets, can click it and see the new tweets appear. If they just appeared on the feed, I wouldn't know as easily which tweets are new. Does that make sense? I guess I just like being able to load the new tweets on-demand.
Post reply on HN