We do. We hear it less often because no-one is talking about how Waymo changes how we all need to work or whatever, that's all.
47,766 karma · joined October 14, 2011
We do. We hear it less often because no-one is talking about how Waymo changes how we all need to work or whatever, that's all.
You can actually do that in Java too with static initialisation blocks.
> 3.0 was a big missed opportunity to kill a lot of the deprecated cruft.
Maybe. 3.0 already came damn close to killing the language. If they'd made the changes any more radical it could easily have been another Perl 6.
You'll note that even Java now recognises that "public static void main(String[] args)" was pointless ceremony.
> Python scripts were meant to be lightweight and free of the tyranny of enterprise OOP which was epitomized by Java. But people found out that keeping track of types in your head is laborious and error-prone, and getting a compiler to check {that the shape of your objects and function calls match} is a huge productivity boost. And so Python 3 enabled static type hints... which, like I said before, Java had from day zero.
Java didn't have "hints", it had mandatory types everywhere. Which, again, they've now recognised was a bad idea and gradually removed. Having a type system is a good idea, and maybe if Python had taken more inspiration from OCaml (or more people had used OCaml instead of either Java or Python) we'd all be better off, but the early-2000s-Java cure of mandatory types everywhere was worse than the disease.
> To make matters worse, static type hint features were introduced progressively over the years, leading to things getting deprecated from the `typing` module and moved to things like `T|None` and `list[T]` and `collections.abc`.
Which happens in any language that evolves over time. Java, despite having a type system built into the language from day 1, now has about ten different deprecated sets of nullness annotations with overlapping functionality.
> I really don't think having top-level (module) variables and functions in Python is a good thing, especially because then they are duplicated as fields and methods in classes. In Java, fields and methods (whether static or instance) can only be placed in classes, and I think this particular straitjacket is a good thing.
Nah. No other language has adopted Java's approach, for good reason. Functions and values are easier than classes and the language shouldn't force you to complicate your code when there's no need to.
> Probably the most tragic example is the ways to build up strings in Python: `+` and str(), `%` operator, `str.format()`, f-string.
It sucks, but what's the alternative? Either a language dies young or it lives long enough to have a bunch of deprecated crap in it.
Interesting, but we're not talking about sport cycling, we're talking about ordinary commuting.
> helmets are quite effective at injury reduction.[1]
Your citation provides no support for your claim.
> Anecdotally I've flown over my handlebars and hit my helmet without serious injury, and I'm sure I would have been in much worse shape otherwise.
This is why we don't make public policy on the basis of anecdotes.
> On cars the law requires seat belts and airbags and a variety of other legally enforced safety measures.
All of which are a lot less unpleasant at the point of use than helmets.
> If you have a study suggesting that helmets would significantly help I'd be curious to see it.
The rates of head injury are comparable (something like a factor of 4 difference), head injuries are very common in car collisions, helmets are already routinely used in motor racing. The evidence is no weaker than that for bicycle helmet use.
Doesn't that cause security issues by making it possible to put other people's private servers (that you want to do XSS-type attacks against) into your domains or something? I have a vague memory of it being a security no-no somehow.
A form that is still extremely rare. No-one seriously advocates helmets for car passengers, for example, even though the injury rates are very similar.
> be hit by a car
Cars don't hit people, drivers hit people.
> They don't prevent you from doing anything you would otherwise do.
They're annoying enough that they do, in practice if not in theory. To say nothing of the fact that drivers pass you closer and more dangerously if you're wearing a helmet.
> helmets are a fantastic example of reasonable PPE, not overactive safetyism.
Quite the opposite.
Why? It's not like drivers have to pay up when they hit someone, as long as they weren't drunk. And in the unlikely event that a driver does get made to pay the big risk is medical bills, so the incentive is to make sure the car is set up to always kill anyone they hit.
Eventually, but what's the typical lifecycle of a company? And if e.g. Treehouse succeeds or fails, was that because of their 4 day work week or because of any of the hundreds of other reasons a company might succeed or fail?
It keeps the semantic web people busy not doing too much damage. Otherwise we might get an XHTML3 or CSS4 based on RDF triples or some such horror.
So when a library adds a new method, it silently changes which method client code calls? That's a bit too magic IMO. I think the best you can do is be case-insensitive and ban methods that differ only in case (or, if you want to extend the idea a bit more radically, ban having things in the namespace within Levenshtein distance x of each other, and then you can autocorrect errors smaller than x/2).
That's probably more to do with the increasing popularity of China-style national firewalls/tracking (sorry, "age verification") than ads.
It's not like buying an ICE or hybrid instead of an EV helps with this scenario at all.
Which this company didn't. They managed 125b of assets belonging to other people, they didn't have 125b of their own.
The problem is that the business logic tells everything else what to do and has authority to do everything that the program can do. Exploiting that way is fiddlier (it's like doing ROP only more so), but ultimately once the software gets into an unintended/unexpected state it's game over.
> It's just that we are used to coarse-grained permissions and abstractions defined back in 1970s. E.g. an app gets access to entire network stack and then can do anything - send telemetry, spam, download code, etc. If we had more high-level comms layer on top of app it could be much more inspectable.
Many have tried. If you try to require fine-grained permissions and user in the loop people just say yes to everything. Ultimately the user thinks they want to do the thing they said to do, and asking them again won't change that.
The argument is that there were enough people who voted against Biden-Harris, or against the DNC process, to swing it.