I recently went to the New York one. It seemed to mainly be about cosplay (showing off your own cosplay, vendors selling cosplay-related supplies) and various kids activities. Although there certainly was drinking, and a car crash - probably caused by the drinking - very soon after the exit from the parking lot.
Then all those nav headers need to have a little button on the side to open a floating div with copy-pasteable content. Or, if needed - different versions of copy-pasteable content (as a command line for copy-pasting into the terminal, json, etc.)
This is a standard UI convention used by all internal dev tools at my current company.
There's a similar Russian tale in blank verse by Pushkin: https://en.wikipedia.org/wiki/The_Tale_of_the_Fisherman_and_... - probably either inspired directly by the Low German story or mediated through a version told to him in his childhood by his nurse (who in turn heard it from someone else).
In the Russian version, the fisherman's wife's final and mistaken wish is to be the Queen of the Sea, with the fish as her servant.
Google Authenticator can be local-only or synced to the cloud.
In local-only mode, the authenticator is bound to a specific device. You can manually sync it to additional devices, but if you lose access to all those devices, it's game over, you will get locked out of whatever accounts you secured with authenticator as the second factor.
In cloud-synced mode, it's synced to your google account, so if you lose your phone, you can restore authenticator state. But if your google account gets taken over, it's game over, the attacker has your authentication codes.
For one thing, because threads about BLM protesters and cars didn't blow up like this one with 2000+ comments.
For another, Dang judged - probably correctly - that a large fraction of people active on HN thoroughly hated Kirk. Without the warning, he might have needed to ban a lot of active and useful contributors, and he'd rather not need to do that.
If you sign up for electrical service for your house, and your shithead neighbor taps your line to power his array of grow lamps and crypto mining rigs, the power company will happily charge you thousands of dollars, and you will need a police report and traverse many layers of customer service hell to get a refund. If you sign up for water service and a tree root cracks your pipe, the water company will happily charge you thousands of dollars for the leaked water, and will then proceed to mandate that you to fix the broken pipe at your own expense for a couple tens of thousands more; and yes, that may well bankrupt you, water company don't care. So why do you expect different treatment from a computing utility provider?
> If you sign up for electrical service for your house, and your shithead neighbor taps your line to power his array of grow lamps and crypto mining rigs, the power company will happily charge you thousands of dollars
Unlike cloud services, your electrical service has a literal circuit breaker. Got a regular three-phase 230V 25A hookup? You are limited to 17.25kW, no way around that. If that shithead neighbor tries to draw 50kW, the breaker will trip.
If it were the cloud, the power company would conveniently come by to upgrade your service instead. A residential home needing a dedicated 175MW high-voltage substation hookup? Sure, why not!
Water leaks, on the other hand, tend to be very noticeable. If a pipe bursts in the attic you'll end up with water literally dripping from the ceiling. It is very rare to end up with a water leak large enough to be expensive, yet small enough to go unnoticed. On the other hand, the cloud will happily let your usage skyrocket - without even bothering to send you an email.
There are plenty of compute service providers working with a fixed cap, a pre-pay system, or usage alerts. The fact that the big cloud providers don't is a deliberate choice: the goal is to make the user pay more than they wanted to.
In addition to everything that's already been mentioned, another obvious difference is that energy and water are finite resources that are already provided at relatively low margins. Cloud services are provided at obscene gross margins. The numbers are all made-up and don't reflect the actual costs in providing those services.
I don't know in US, but having limits on how much electricity a house is able to take from the gride is absolutely something in some countries out there.
At least in my country the metering is done _in_ the house so my neighbour has to break and enter to tap the line behind the meter. I would probably notice well before bills would pile up. If he taps it outside, probably no one would ever notice if done right. The grid looses energy all the time. Not every kWh that goes into the network is billed in the end.
As always, it just doesn’t make an awful lot of sense to compare physical and virtual worlds. As in leaving your front door unlocked in rural areas vs not securing your remote shell access.
The first instance is difficult to fix as crime can often involve substantial losses to people and often there's no route to getting a refund.
The broken water pipe should be covered by buildings insurance, but I can imagine it not being covered by some policies. Luckily a broken water pipe is likely not as expensive as not having e.g. third party liability protection if part of your roof falls off and hits someone.
For your scenarios, I have the police, the public service commission, utility regulators, my elected officials and homeowners insurance to potentially help. Not that it always works, not that it's easy, quick or without pain, but there are options.
For the cloud, I have the good will of the cloud provider and appealing to social media. Not the same thing.
The idea is to sacrifice one part of the environment (municipal landfill and surrounding land) in order to have everything else reasonably clean and beautiful.
(Alternative being a thin layer of waste and garbage spread all over the planet. First World did that until 1970s; many poor countries still do it. Looks shabby and ugly.)
- In popular camping/hiking areas, there's just too much of it.
- In dry areas it can take decades to break down.
- In rocky areas it's really hard to bury it deep enough (and so people often don't).
- In some areas (like the deserts of the southwestern U.S.) the ground is really fragile and shouldn't be disturbed. Cryptobiotic soil can take decades or centuries to regrow.
- People often don't move far enough away from camp sites / trails / waterways before they dig a hole.
And even in areas where it's easy to dig, the soil is moist enough to it break down, and it's easy to move far enough from sensitive areas, people are just lazy and often don't dig holes that are deep enough or far enough away.
If people were super conscientious (maybe it works great in Japan?) and/or only did low density camping/hiking, it might not be a problem—and indeed in many areas it isn't really a problem. But I've also been to campsites where if you take 20 steps from the trail you can see 5 or 10 places with TP peeking out from the soil within a small radius—and who knows how many more that you can't see.
Helicopters are vulnerable to small quadcopter drones when landing and taking off. This limits some traditional uses of helicopters (anything that involves landing in enemy territory becomes much more risky) but still leaves others (shooting missiles at surface targets).
Helicopters are very effective at shooting down large fixed-wing drones.
Helicopters are very effective at sinking drone boats without air defenses, but are in turn very vulnerable to drone boats equipped with SAMs.
They are not talking about pulling in Chromium on a microcontroller. Their web server is on a microcontroller, so they want to minimize server side CPU usage and force the browser to do their XSLT transformation.
Since it's a microcontroller, modifying that server and pushing the firmware update to users is probably also a pain.
Yeah, I don't think XML + XLST is any better than or allows anything that sending say JSON and transforming it with JS wouldn't. However that would require changing the firmware, which as you mention may be difficult or impossible.
reply