This is obviously untrue… do you use any of them?
201 karma · joined January 10, 2013
This is obviously untrue… do you use any of them?
He’s at the head of a stampede. Being near the front gives him influence over its direction; it doesn’t give him the ability to stop it. If Anthropic sits down, the stampede doesn’t stop. Anthropic just gets trampled.
That contradiction is basically the entire problem I was describing.
That said, if slowing this down were possible, I think it would have happened by now. Maybe he’s hoping the OAI/HF incident becomes something the industry can rally around, but it won’t. The fundamental problem is simpler: no one will slow down because no one trusts anyone else to slow down.
cabinet 200cm x 92cm top 3cm bottom 15cm scale 5
50cm \* \* 20cm
\* drawer door door drawer
\* drawer ^ ^ drawer
\* ^ ^ < drawer
\* > drawer drawer <
So I inspected the odd shaped element and noticed it would overflow. Probably fine for your purposes.Super cool!
import Button from "@cool-lib/core/button";
import Link from "@cool-lib/core/link";
import Widget from "@cool-lib/core/widget";
This is similar to what lodash does too. Still have more imports, but only one package.json dependency! And the same perf gains.
I hope that other data grid libraries can mimic some of this to improve web accessibility. These components can be really tedious to interact with today
- It's easier to control your SVGs with clearly defined props
- You can bake in accessibility into your illustrations
- Unlike to icon fonts which load the entire font, you can leverage modern module loading practices to only load the SVGs you need (i.e.: import HackerNewsIcon from '...')
- Unlike in-lining SVGs, the resource can be cached, bundled, and re-used multiple times without duplicating the contents.
- This tool automatically strips away `id`s so you don't have id collisions.
- Since it's a component, you can modify it to, for example, show a different SVG under a different locale if the English design doesn't translate well.
This has helped our little design system team off-load the incoming requests to add new icons back out to the requesting teams. And if an icon doesn't meet the requirements of our system, consumers can continue to use them in their own projects while still being aligned on props and a11y.
Hope you all find this useful too!
constructor(props) { super(props); this.func = this.func.bind(this); }
Is better if you care about performance.
Not sure of similarities to brain training games, but I would bet there is something there.
One question: does this work with React? I found this Github https://github.com/kwnccc/react-popmotion but it isn't part of the main Popmotion organization. I would be willing to pay a license fee for something well maintained with React support.
FYI, The pay structure I agree with most for web libraries is a non-recurring fee, 1 year upgrades and support, the versions I purchased are useable indefinitely but I can buy a new 1 year license for the newer versions and more support. Up to you how you do it though!
Lots of space in this area.
"There are only two hard things in Computer Science: cache invalidation and naming things." -- Phil Karlton
You can add something like Tab Cookies or Self Destructing Cookies. You can also add something like uMatrix to the mix.
If you really want to go far, add a "User-Agent Switcher" type extension.
I wouldn't add more than this though, it starts to be overkill. Also do note: I used to use noscript and it works well, but going from 0 JS on a domain to all JS on a domain isn't ideal. If you want ultimate security, add noscript as well but maintain the others so that when you whitelist a url you can still expect to be safe.