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

The Single Piece of JavaScript on HN

blog.watchandcode.com

Post reply on HN
Print view View original

91–100 of 195 posts

Re: The Single Piece of JavaScript on HN

#91

Post by hnmcs »

mchahn wrote: post #69
hk__2 wrote: post #60

Earlier quoted context omitted.

That would make the whole downvote system useless. Just post spam comments everywhere then delete them after a day and you’ll always have a positive karma.

Ok, I"m facing an armageddon of downvotes but why the heck was this downvoted? He made a point, that while arguable, is a valid comment. Maybe the discussion of downvoting is bringing more downvotes. Jeeez. Edit: My upvote brought him back to zero, for now.

I see things more in terms of signal/noise considerations.

Rational minds can disagree, and intelligence can't understand much-greater-intelligence (so lessers might downvote much-greaters for that reason, besides the first-mentioned reason), but you don't have to worry about armageddons of downvotes. Or the balance of votes.

Just upvote what you consider "signal", and downvote the worst kinds of noise.

Thus you, my parent comment, are barely voted on at all, while the one by jewbacca rises to the top all day, no matter the weather.

Re: The Single Piece of JavaScript on HN

#92

Post by microcolonel »

smadge wrote: post #81

A few weeks ago I turned off javascript in my browser out of principle and to see if progressive enhancement was still a thing web developers cared about (hint: it's not). I was pleased that HN worked fine, and the only annoying thing was that voting caused a page reload. It's nice to see this get the attention it deserves! Developers! You probably don't need javascript to achieve 90% of your goals. It will just slow…

For me it doesn't bother reloading; but it shows up when I reload.

Re: The Single Piece of JavaScript on HN

#93

Post by microcolonel »

mintplant wrote: post #76
TazeTSchnitzel wrote: post #73

Earlier quoted context omitted.

I feel like there must be a simpler way than that.

That's what I thought too, at first. Some of the iterations I went through before reaching this point: - Links for the up/down arrows with target= , that set "visibility: hidden" on :visited. But oh, only color-changing CSS properties are allowed for :visited selectors. - Links for the up/down arrows with unicode ▲ and ▼ that set their color to the page background color on :visited, using a sibling selector to hide t…

You could put each of them in an .

(now to hide from the abuse, and hope my karma doesn't fall below the voting threshhold for suggesting this)

Re: The Single Piece of JavaScript on HN

#94

Post by pdkl95 »

seanalltogether wrote: post #3

If we ever make it around to a second piece of javascript on here, can I request that it be a collapse comment function? I promise i won't ask for anything else.

https://greasyfork.org/en/scripts/12493-hacker-news-folding-...

I wrote this a while ago, which seems to work. I reused the vote arrow with 1/4-turn rotation, placed on the other side of the comment header line to avoid confusion.

Re: The Single Piece of JavaScript on HN

#95

Post by tim333 »

iamleppert wrote: post #68

Why isn't this wrapped in a react component and written with ES7 lambda functions, transpiled from JSX (using babel of course)? God I hate what has happened to the web these days.

The funny thing is that it's always been possible to write a bit of plain javascript but you don't seem to get much respect for that compared with the buzzword stuff.

Re: The Single Piece of JavaScript on HN

#96

Post by catshirt »

aaronbrethorst wrote: post #25
gordonzhu wrote: post #11

Earlier quoted context omitted.

What's most fascinating to me about this isn't the simplicity, it's that this code has lived for so long with almost no changes. It's a great counter-example to all the recent articles about JavaScript fatigue. It's good for us to see real examples of sites that aren't caught up in the framework of the week hype. At the end of the day we're trying to make stuff that works. ES5 vs ES6, React vs Angular vs. Ember vs. A…

For the majority of cases that I've seen, these arguments are simply excuses to avoid doing real work. It's way more fun to decide whether your amazingly awesome Unicorn startup is going to use React or Angular, or Express vs. Rails, or whatever than it is to actually go through the hard work of building a customer base and making money.

maintaining software is a real thing.

for the majority of cases i've seen, these arguments are to save developers time and the company money.

my gut & feelies tell me there is truth to "it doesn't really matter what technologies you use" but my brain and experience tell me that is objectively false.

Re: The Single Piece of JavaScript on HN

#97

Post by oldmanjay »

mchahn wrote: post #77
krapp wrote: post #74

Earlier quoted context omitted.

Downvotes aren't worth worrying about on Hacker News, nor are upvotes. They do tend to even out in time so that only the really objectionable comments get downvoted a lot (and eventually flagged) but because pg more or less decided that there didn't need to be a standard for either, I treat them as worthless.

I take it personally which I know I shouldn't. I think others are the same. You can tell when people say "Why was I downvoted?!". Everyone wants peer approval. Also you get the same feeling you get when you are being denigrated by someone who doesn't have the backbone to come out and say who they are. I say you get the feeling, not that it is true.

Feeling slighted is fine, but it's best to keep the reaction off the site unless you want more downvotes.

Re: The Single Piece of JavaScript on HN

#98

Post by mintplant »

microcolonel wrote: post #93
mintplant wrote: post #76

Earlier quoted context omitted.

That's what I thought too, at first. Some of the iterations I went through before reaching this point: - Links for the up/down arrows with target= , that set "visibility: hidden" on :visited. But oh, only color-changing CSS properties are allowed for :visited selectors. - Links for the up/down arrows with unicode ▲ and ▼ that set their color to the page background color on :visited, using a sibling selector to hide t…

You could put each of them in an . (now to hide from the abuse, and hope my karma doesn't fall below the voting threshhold for suggesting this)

I thought of that, but then the arrows don't hide immediately after you click them as on HN - they'd still be visible until the request completes. So you'd end up with the same problem: hiding both arrows when either is clicked without using JS.

(I assume you mean putting each pair of arrows in an , rather than each individual arrow.)

Re: The Single Piece of JavaScript on HN

#99

Post by nostrademons »

catshirt wrote: post #96
aaronbrethorst wrote: post #25

Earlier quoted context omitted.

For the majority of cases that I've seen, these arguments are simply excuses to avoid doing real work. It's way more fun to decide whether your amazingly awesome Unicorn startup is going to use React or Angular, or Express vs. Rails, or whatever than it is to actually go through the hard work of building a customer base and making money.

maintaining software is a real thing. for the majority of cases i've seen, these arguments are to save developers time and the company money. my gut & feelies tell me there is truth to "it doesn't really matter what technologies you use" but my brain and experience tell me that is objectively false.

The reason "it doesn't matter what technologies you use" is because successful software gets rewritten multiple times anyway.

It matters a lot eventually, but having an "eventually" to worry about is a nice problem to have.

(There's also a big perspective difference between being an entrepreneur writing initial code for a project vs. an engineer hired to maintain & grow that code. Code quality, architecture, and technology choice matters a lot to an engineer who will be working with it directly. It matters a lot less to a business that can swap out engineers until they find ones who enjoy working on that codebase. The fact that you even have money to hire engineers usually indicates that the existing code is getting the job done. The business only gets screwed when the code quality is so bad that nobody can make sense of it, and the environment changes in a way that requires modifications.)

Re: The Single Piece of JavaScript on HN

#100

Post by catshirt »

nostrademons wrote: post #99
catshirt wrote: post #96

Earlier quoted context omitted.

maintaining software is a real thing. for the majority of cases i've seen, these arguments are to save developers time and the company money. my gut & feelies tell me there is truth to "it doesn't really matter what technologies you use" but my brain and experience tell me that is objectively false.

The reason "it doesn't matter what technologies you use" is because successful software gets rewritten multiple times anyway. It matters a lot eventually , but having an "eventually" to worry about is a nice problem to have. (There's also a big perspective difference between being an entrepreneur writing initial code for a project vs. an engineer hired to maintain & grow that code. Code quality, architecture, and tec…

but, there are many instances where software would not get rewritten with proper technical foresight in the first place.

i take your point none the less- there are contexts where it doesn't matter.

Post reply on HN