826 karma · joined March 6, 2013
Unfortunately, in practice, Apple have proven to be entirely incompetent at achieving that protection. The App Store is 90%+ garbage and scams. It's completely unusable for any form of discovery. Even when you know exactly what app you're looking for, you have to wade through copycats, typo squatters, and even paid adverts trying to distract you from your search.
Sideloading is full of risks, and I don't love it. But it's at least a little bit of competition to push Apple towards make the App Store useful again.
For the overwhelming majority of jobs, you get paid only what's in your contract. If that number is not enough, fine, renegotiate it if you are able. But employers cannot be expected to pay you more than you're entitled to.
Like most accessibility features, you don’t need to have a condition to find value in this one
The post says the process starts up quick enough that the process being temporarily unavailable isn't noticeable - but what if the process _doesn't come back_? It's also impossible to do blue/green deployments this way.
It's clearly not a solution suitable to large-scale deployments. The simplicity has its trade-offs.
This is a strawman. Commenter said anything about the right to free speech, only about the willingness to be exposed to opposing viewpoints.
We all know that Bob is not obligated to listen to Alice, and he is not required to host a venue for her opinions. But Bob's eagerness to run away to a place where there is no risk of seeing Alice's view, while not necessarily bad (if you want to live in a bubble, live in a bubble), it is _not_ a virtue.
I know this is more of a comment on the state of AI models than Transformers.js. It's probably not even representative of state-of-the-art image classifier models. Just a fun example of how these things learn.
(A collaborative doc would probably be a better venue for that, of course.)
Apple names are fun! It's a nice thing!
I mean even when Apple uses sequential, numerical names you can't always answer the question of which came first: the iPhone 8 and iPhone X (10) were announced ~simultaneously! And there wasn't even a 9!
My point is it really doesn't matter which big cat or California landmark came first. It's trivial to find out if you want to, but it's not terribly important to encode that in the name you're using to identify your product.
It’s like saying pizza is awesome, therefore ice cream is not.
Both are awesome! It just depends what you’re trying to achieve at that point in time. A language’s type system is not, in absolute terms, an advantage or disadvantage. It’s just a design choice, each with their own trade-offs that we must consider.
(*I said _often_, meaning I concede that it is sometimes actually not cheaper: please resist the urge to provide counter-examples, I know of their pricing trickery!)
This comparison breaks down in a few ways: with the car, I realise the value of it immediately, as I get to drive it around, whereas for a service that only activates on my death, the value is only _potential_ until that actually happens.
Also, I can terminate my car lease and feel OK about it, I have already realised value, it did its job. If I pay for this service for a year, but I don’t die, have I realised any value? Maybe marginally in the peace of mind I will feel while alive, but there’s no arguing that the optimal way for me (or more realistically, my estate) to get the most value for money is to buy just one year of service, and then kick the bucket in that same year?
Edit: I’m not saying any of this necessarily wrong, it’s just a really interesting quirk of pricing incentives
+1 to this. Especially at the 16-years-experience level. Maybe earlier in someone's career where their primary focus is how to fit in and ship stuff without getting stuck all the time. But at ~staff level, your thinking and your contributions become a lot more language-agnostic (not entirely, but mostly)
Lots of these made for a nice showcase but should never be used in a product ever - just horrendously unintuitive. For some, I wouldn't even know they were checkboxes if the page wasn't titled "here's a bunch of checkboxes". But a few of them were actually quite nice, accessible, and pleasantly useable.
Ultimately it seems that the checkboxes that were closest to the native OS checkboxes were the ones I enjoyed trying the most. I guess that's a predictable outcome. But it might be an indication that the further one strays from the OS defaults, the less good of a design it is? Maybe checkboxes are a solved problem, and there is only narrowly limited room for a brand to apply its personality on form controls before they become less usable for the sake of being "unique".
#33 was by far my favourite, for the record.