transport to other towns is generally not a spur of the moment thing. checking a timetable is a lot easier for people in rural villages than using an app. one train every two hours is the norm here, and they stop at villages of a few hundred people.
i mean, they can’t work with a few thousand people. you’d need a few thousand pods, because they only take two people. and they can’t turn around by themselves, or navigate switches (look at the wheel profile), so you need new infrastructure for that. and they say that you order them via an app but since they can’t just go wherever you need to wait for a free track, so depending on where you are on the line you could need to wait for your ordered “pod” to navigate almost the entire system, waiting at stations behind other pods for who knows how long.
what’s more, this idea isn’t new: single-rail “gyrotrains” were invented in 1910, but never took off because of the extra mechanical complexity involved compared to jush using a normal train. and before you say “modern tech fixes that”, the main problem was that gyroscopic precession would fling the cars off of corners. that’s a physics problem which these pods appear to have solved by going extremely slow.
so, we have here a system that’s vastly more expensive, complex and unreliable than scheduled rail bus service, proposed to fix the same problem as scheduled rail bus service. just buy a rail bus.
multiple things are possible
gotta look at that graph per capita, sweden had a much smaller population in the 70s.
wrong order.
SD started rising before the “immigrant wave”, since we’ve had high immigration numbers since the 70s, but the shootings and bombings only started five years ago. they’re mostly being carried out by people who were less than ten years old during that time. so the violence is, in a way, home-grown.
“essentially”. fuck off. i started this entire chain saying that it’s good that python is getting faster, and you shut that down too. you’re obviously only here to start fights. i’m not interested in continuing this.
when the hell did i say python is supposed to be slow? i just said it’s supposed to be used as a high-level glue to hold low-level things together. different tools have different uses. you’re complaining that a saw is a bad hammer.
explain sweden, please
not really…
what are these numbers?
why are you so combative?
it’s like that Mythbusters experiment where they fire a football from a truck. if something falls off of a vehicle, it’s still moving at the speed of the vehicle.
now being behind an unevenly packed lumber carriage when approaching a tunnel, that would make me nervous.
but like, most of the standard library is written in c. most popular libraries are written in c. they’re built that way because python is a flexible way to glue functionality together. that’s the point of python: it’s easy. if i want performance, i port part of the logic to a compiled language. but most of the time that’s not necessary.
just like how with git, we have lfs. we build what we need when we need it. i don’t understand your tone here.
pretty sure it’s a stoat. ferrets are much larger, and least weasels don’t have black tails (at least i think the tail is black).
Edit: actually, it’s probably a least weasel. the paws aren’t as light as on stoats.
i mean, that’s what you’re supposed to do. python is a glue language, after all.
not exactly: https://benchmarksgame-team.pages.debian.net/benchmarksgame/box-plot-summary-charts.html tl;dr it can be true, but not necessarily. fast python code is on the magnitude of 1/5th the speed of go.
the thing with python is that there is a huge difference between fast and slow code. in go, only really slow code is slow, and in rust even slow code is fast.
go is also not a fast language. it’s about halfway between python and c.
but they all solve different problems so that’s ok.
it doubled in speed from 3.9 to now, so it’s getting there.
the smurfs are three apples tall, she may have mixed them up