The first Distill publication[0] made tasteful use of minimal interactivity through JavaScript/d3.js[1] on top of SVGs. Many of the illustrations were initially drawn in GUI editors.
(Outstanding work by Shan Carter; it’s what I first saw of his style and it’s what made me want to join his team.)
Yeah, and that's my understanding. Nothing goes video -> text, or audio -> text, or even text -> text without first going through state space. That's where the core of the transformer architecture is.
And what else did Apple do? Build two “Pro” phones with even bigger batteries for these folks. Come on, let a thousand flowers bloom!
(Yeah that phrase has unfortunate Mao-era baggage, but personally I really just want the mini series back—which many also consider to have too little battery capacity—so I feel encouraged by Apple broadening the iPhone lineup.)
Seriously, it's bizarre to see this argument from people that Apple isn't caring about what people want in terms of battery life. Apple in their keynote called out that they made the Pro models slightly thicker for the sake of a larger battery! Like, why ignore the standard models of iPhone and only focus on the Air when making complaints?
You seem to sound dismissive, and it did sound wild to me too, yet that is indeed happening and well documented. The “wires” are kilometer long thin fiber optic cables that are spooled off the drones. See for example: https://www.businessinsider.com/unjammable-fiber-optic-drone...
I’m not disagreeing, but the magical difference to me seems that Apple _users themselves_ decided ahead of time to trust Apple, whereas _the developer_ would make the decision to trust a third party?
(My more jaded view is that such arguments are merely rationalizations, and that in 90% of these cases it’s mostly about which stack the people building an app have previous experience with… even though they explicitly claim the decision was made on technical grounds. ¯\_(ツ)_/¯)
I think your jaded view is likely correct, at least in this case but I can see the other argument. After all, even myself I choose to use iPhone over Android purely because I align more with their practices/policies around data vs. Google, which I guess means I also have decided ahead of time to trust Apple over another entity. But I also have no illusions when it comes to law enforcement access, outside of Apple's Advanced Data Protection, which Android/Google currently offers no alternative to.
> choose to use iPhone over Android purely because I align more with their practices/policies around data vs. Google
Based on what GrapheneOS shared, Apple forces apps to use their service. [1]. If you're a privacy conscious developer in, say, Switzerland, your data is being forcibly kept on US servers. You dont even have that choice.
According to GrapheneOS, Google gives you that choice with Android. That sounds better for privacy, if you ask me.
No argument from me there, Android can be better in some areas, and obviously GrapheneOS is going to be the better option above stock/skinned OEM Android if you value privacy and/or security.
But for those not willing to make the tradeoffs that GrapheneOS requires, Apple is probably the better choice IF you happen to trust Apple, or phrased differently - if you want Apple to be the only one spying on you vs. any number of third parties on Android, depending on which apps you install.
As for me, I have no particular love for Apple, despite being entirely in their ecosystem of devices, but I cba to play sysadmin at home and until Google/Android offers the equivalent level of E2EE as Apple's advanced data protection, I'm sticking with iPhone. I could piece together the equivalent myself, but there's something to be said of just having it offered OOTB.
“On the Fairphone 6, the battery is firmly screwed in. With the predecessors, it could simply be removed.”
Still awkward to turn that into the headline when it’s such a minor part of the review. The article was “translated with technical assistance and editorially reviewed”, but it’s just as off in the original. Maybe headline chosen by an editor, not the author?
Yep, lets you use normal .py files instead of using the .ipynb extension. You get much nicer diffs in your git history, and much easier refactoring between the exploratory notebook stage and library/app code - particularly when combined with the other stuff I mentioned.
Hm, I’m not sure from your comment if you’ve seen this: if you scroll down on an app’s App Store page, there’s an “Information” section with an “In-App Purchases” subsection that you can expand to see all In-App purchase names and their associated prices.
Even after you pointed it out, I really had to search the page for it and finally found it tucked away if the far bottom right corner of the page.. I can totally imagine that for those who do not know where to look specifically, that they'll never see this information.
Are you also on a mini? ;-)
Just because I really like bivector.net, despite its questionable web design choices: zooming out one level should make it so the animated “join our discord” no longer causes reflows.
This should be fixed, but as a workaround until then for those of us on slimmer viewports…
(Outstanding work by Shan Carter; it’s what I first saw of his style and it’s what made me want to join his team.)
[0] https://distill.pub/2016/augmented-rnns/ [1] https://github.com/distillpub/post--augmented-rnns/blob/mast...