Rich people seem to spend a lot of times in helicopters and private planes, which is dramatically more dangerous than commercial air travel.
I could off the top of my head name a few rich people that died from it. Hell, the titan submersible, while a very different animal, is a pretty clear indicator that vast wealth doesn't preclude a willingness to risk one's life in highly experimental "travel"
Maybe not the richest of people, but there's a significant amount of people who got their wealth due to their love/acceptance of risk. Climbing Everest is not cheap, is still very risky, and I presume it is more expensive than a cross-Atlantic trip on these jets.
Sure, but the main risk they'd be accepting here is that of spending an inordinate amount of time hanging around in an airport terminal waiting for a broken engine to be fixed.
It'd be hard to spin that as being anything like as heroic as the risk of being killed or maimed whilst climbing Everest!
And they want comfort. A 5-hour flight sleeping on a flat bed is a thousand times better than an economy seat on a 3-hour flight. Part of concorde's problem was the rising expectations of first class travel in the 90s. It was never going to be compatable with today's huge first class seats.
AI isn't automation. It's thinking. It automates the brain out of human jobs.
You can still get a job that requires a body. My job doesn't require a body, so I'm screwed. If you're say, a surgeon or a plumber, you're in a better place.
Why this example? One of the things automation has done is reduce and replace stevedores, the shipping equivalent of stacking shelves.
Amazon warehouses are heavily automated, almost self-stacking-shelves. At least, according to the various videos I see, I've not actually worked there myself. Yet. There's time.
> AI isn't automation. It's thinking. It automates the brain out of human jobs.
You can still get a job that requires a body. My job doesn't require a body, so I'm screwed. If you're say, a surgeon or a plumber, you're in a better place.
Right up until the AI is good enough to control the robot that can do that job. Which may or may not be humanoid. (Plus side: look how long it's taking for self-driving cars, how often people think a personal anecdote of "works for me" is a valid response to "doesn't work for me").
Even before the AI gets that good, a nice boring remote-control android doing whatever manual labour could outsource the "controller" position to a human anywhere on the planet. Mental image: all the unemployed Americans protesting outside Tesla's factories when they realise the Optimus robots within are controlled remotely from people in 3rd world countries getting paid $5/day.
Yes, AI is automation. It automates the implementation. It doesn't (yet?) automate the hard parts around figuring out what work needs to be done and how to do it.
The sad thing is that for many software devs, the implementation is the fun bit.
Except it isn't thinking. It is applying a model of statistical likelihood. The real issue is that it's been sold as thinking, and laypeople believe that it's thinking, so it is very likely that jobs will be eliminated before it's feasible to replace them.
People that actually care about the quality of their output are a dying breed, and that death is being accelerated by this machine that produces somewhat plausible-looking output, because we're optimizing around "plausible-looking" and not "correct"
I'm not sure if you'd consider London to be a safe city but these things won't survive in London either.
People are already pissed off about delivery ebike riders, who disobey laws and ride dangerously. But there's very little you can do about humans. A helpless robot that is causing a hazard to pedestrians? A ULEZ-style strike force will be mobilized to drive them out.
And what about blind and partially sighted people? The place for wheeled vehicles in on roads. If you want to exist in pedestrian areas then make a robot that can walk.
But putting that aside, the biggest problems these things will have in the UK is a completely different conception of walkability even compared to, say, NYC.
People walk everywhere, pavements are cluttered and crowded, the vast majority of roads are not grid-structured almost anywhere in the UK, etc. So much so that when US firms do consider testing these things properly in the UK they will have to pick somewhere like Bath or Worthing or Hove: enough wealthy people to try it, and easy, grid-structured roads. Not many other good candidates.
The second problem they will face is the nature of protest. People won’t vandalise them. There will, however, be extensive civil mischief: people will box them in, mislead them, cover their sensors with googly eyes and woolly hats, put traffic cones on them, and generally make the whole scheme unworkable. And that is if councils don’t outright ban their operators.
Fundamentally I think they should just use the road and keep to the right (in the US), like other slow moving vehicles. They’d probably be fine in bike lanes where they exist.
Maybe they could enter the sidewalk for half a block at a curb cut like a cyclist would do to complete a delivery.
There's a very clear and obvious reason they are on the sidewalk. Bikes are not "probably fine" in bike lines themselves though. Bikes are mainly visible to drivers. These things are too small to be in the bike lanes let alone in an actual lane of the road. They'll just be a small speed bump to most cars.
There are several languages that I could use and be economically successful with, but I refuse to use because I consider them to be poorly designed.
Using a bad language for 8 hours a day makes me irritable and it's impossible to prevent that irritability from overflowing into my interactions with other people. I'd rather that my conversations with the computer be joyful ones.
It was a design decision to make the syntax feel as familiar to Rust as possible. But I do agree that it's a bit verbose and that it won't hurt to add a .dispose() handle to the objects themselves.
You need unbounded recursion. Conditionals alone can’t do that. If you have some kind of conditional go to/jump if expression that’s a different matter.
You can emulate recursion with iteration and a push-down stack. If it doesn’t either recurse or offer both iterations (loops) and something that can act as a stack (at least an array or so) then it’s not Turing complete though. I have yet to see a stack or user-manipulable arrays in CSS.
> An aspiring teen could set up an RPi that modifies headers for all traffic on the network that the parental units never even know about
An aspiring teen could just have sex with another aspiring teen...
You won't stop teenagers from finding a way to be teenagers. Part of being a teenager is learning how to subvert the rules set by adults to fulfil one's hormonal imperative.
I can't promise anything this is a pet project. I might turn it into an open source project, and I might also provide some kind of service for a few bucks if it gets traction.
reply