1,125 karma · joined April 3, 2018
That's like wondering why the source + instrumented dev environment uses so much more resources than its compiled, optimized binary.
What a weird confusion to see on HN.
This doesn't seem weird or contradictory to me at all. Nothing seems cheaper to me than my girlfriend's Android phone with rubber bumpers built in. Meanwhile my iPhones with cases look brand new when I'm ready to sell them.
No wonder so many HN comments are grandstanding about how they dislike or don't need travel: they aren't talking about meeting other people or experiencing other cultures. They're just talking about weekend travel packages where they're shuttled around to take some pictures.
How incredibly boring.
Your VR idea like saying you've been to Prague because you spent extensive time in Google Maps street view: I wouldn't even bother.
Yet ads pay for everything that every HNer is too stingy to take out their wallet for, which includes almost every website/service, especially every website smaller than the websites HN likes to hate on.
It's like listening to people justify why they pirate media, crafting elaborate philosophical pieces when in reality they just don't like paying money for things.
There are components that are complex enough to warrant a view library, embedded in an application that's not. In fact, it doesn't take much complexity at all, in my experience. At which point loading a view library a la carte is your only real option.
What doesn't make sense about that?
Aside: I don't understand the premise of this thread that suggests it's a "SPA" just to, say, use React on a single page of an application. The whole basis of the "SP" in "SPA" is that the Javascript (state) spans multiple pages.
Also, if you're factually wrong about something, nobody owes you research even though it would be nice. You're still wrong even if you can't be bothered to click a few links, so it's a weird complaint. They didn't just have a "point"; they were right.
Finally, lighten up. It's just gaming-related chit chat. Nobody here is paid to use their free time to write comments on HN or to give you better links.
Then it would be bad for them, too.
The prevention measure you create for the remaining 10% (like a moderation queue + human review if you can afford it) is likely to only work because its workload is diminished 90% by a crude measure like ReCaptcha.
Your dismissal doesn't illuminate anything. It turns out that abuse prevention is hard and costly.
Add in the mobile-device issue and you quite literally have a solution that's lose/lose.
Now what about about literally every other entity in the world that has a website? The vast majority of which not being a business? Nor serving life-critical documentation to all of the country's disabled?
Once again, all trails lead back to you providing some alternative solutions instead of the empty catharsis of coming up with downsides to something in an internet comment.
Here's one of my own: Isn't it annoying that spambots show up the second I launch a website? Ugh! Well, got that out of the way. Now I need a solution.
What's yours?
Nobody is claiming it's perfect. But notice how nobody here is analyzing why people use ReCaptcha in the first place nor providing alternatives.
If you knew nothing of ReCaptcha and only read these comments, you'd wonder if it was a gag website operators put on their website for self-amusement, which is basically how I looked at homework as a kid. But I feel like this discussion is a bit more one-sided than I expected on HN, a place where I would've thought more people had experience running a website and how immediately effective ReCaptcha was the second you added a <textarea>.
But notice that you haven't suggested an alternative. You're just lamenting one of the few, generalizable, cheap resources a website operator has to avoid abuse in a world where it's only getting easier and easier for bad actors.
Your analysis is just as thorough as "but somehow it's OK to put locks on every door because some guys are abusing the system o_0?!" Food for thought: Is everyone encumbering their life with keychains for the fun of it? How do the trade-offs look? Do locks play any role beyond feeding the locksmith industry? What other options do people have and how do they compare with buying a $17 lock for their front door and installing it with a few screws?
Besides, if a relatively simple puzzle is too much to ask, then maybe you didn't care all that much to begin with. I can think of various platforms where this would be a good filter even if there was no such thing as abuse. ;)
Your anger would be better directed at the bad actors who ruin things for you, like how you need to buy a lock for your door. How much time in your life has been wasted by slotting a key into a hole? Ugh, doesn't anyone know this isn't the world I asked for?
An even cheekier way to drive the point home would be for a sex-stories website to have a slider in the footer to update all age values across the site.
If the human population was serious about quality-of-life improvement, they would eat healthy and exercise. But they don't. Most people in this forum don't.
Also, bits of class issues show up in the other complaints.
So, no, it's not just "what is a class" and it's a weird hill to die on. I feel like most of these responses to hooks in general just focus on the most trivial detail aka bikeshedding.
They were generous enough, but at the expense of uncertainty + you needing to play an active role in getting them to pay your bill. Depending on what sort of service you run, it may be a constant ordeal.
After getting some large CloudFront bills taken care of, I left and wondered what sort of person had the stomach it.
I'm certainly not using Xcode + Cocoa + the MVC abstraction for iOS/macOS apps because it's the superior way to build software. It has its own warts, like the effort it takes to swap out MVC with some other pattern, or how it comes with no async abstractions -- you'll just be writing callback code like JS developers had to before the Promise.
It's tempting to unmask "ugh, JS developers" as a bunch of idiots, but I think you'd only be kidding yourself if you think your pet environment is some global optimum.
For example, burned coffee is more of a caricature of its normal taste unlike, say, burned popcorn which tastes like charcoal. You could probably tell most people including me that some burned coffee is some local artisanal roast and I'd chalk up any changes in its flavor to that and move on.
People clearly just aren't making coffee purchases based on taste, so you have to liken the whole thing to people going to bars. At which point Starbucks is simply the well-known bar in town with no surprises. You know their hours, you know where it is, you know you can get a table and dominate it shamelessly for hours, and so do all the other people in your group.
Sure, you'd like to try one of those lil cafes around the block sometime, but it's something you procrastinate just like anything else that will introduce the slightest change in your life.
Would it be insufficient for a study to tell people to drink more water even though we know it's not the action of drinking water that helps us, but the cellular interaction with it once it's inside us? And even though people could connect saline bags directly to their nervous system?
So, I'm wondering what you're clarifying.
I built a SPA recently and learned pretty quickly to replace `on('scroll', handler)` with a set-flag-and-sweep-at-slower-interval solution to bring down CPU usage.
While something like React alone isn't slow, building a SPA means you're taking on a lot more responsibility, and there's a lot more things that can go wrong.
Even something like "when user clicks an item, make loader spin until server response, and then render the detail page with the data" can feel much, much slower even though it's not from a clock-time standpoint.
Aside: Using a slow device as your main testing device is a life-changer if you want to catch this stuff early. It's hard to ignore this stuff when you have to feel the pain yourself on every refresh. Good reason to always keep your old phone around.