Why should California taxpayers subsidize other Californians to buy EVs that are made in other states? Like if you care about emissions aren't the cars made in California using California's relatively green electricity, higher worker standards, and short distance to travel after manufacture better than ones made elsewhere? Even if you don't want to support Tesla, not even having a carveout for cars manufactured in the state seems insane.
There are a couple of arms commonly used in research around the $10k mark, namely the Franka Emika and UFACTORY xArm 6.
The ALOHA project uses the ViperX 300 6DoF, which is around $6500 but uses higher quality dynamixels with aluminum parts and bills itself as "research grade". I have one of these and I'd say it's expensive for what you get, but still cheaper than the "factory grade" robots. I will need a bimanual setup eventually and I'm probably going to get either an Emika or xArm since I'm already hitting the weight limits of the ViperX.
Sorry, my use of "intelligent" here was imprecise. They can clearly learn, but seem much less intelligent than other animals that we commonly eat, and not anywhere close to the same level of intelligence of animals that we generally do not eat, such as great apes, elephants, and whales.
I visited an experimental octopus farm in Hawaii once, expecting to come away feeling guilty about eating octopus since I had heard so much about how smart they are. It ended up having the opposite effect, since I learned that they only live 2 years and aren't social creatures. This is opposite of every other intelligent creature that we know of, and so I'm extremely skeptical of claims of their intelligence. They might show sophisticated behavior, but so do a lot of insects like ants and we know they aren't intelligent.
EDIT: sorry, when I say intelligent, I mean as intelligent as animals that we generally do not eat. I believe they are less intelligent than livestock, but can learn behaviors like most animals.
As noted in the quote, the CommonCrawl WARC files don’t contain images themselves, LAION used those files to find img tags and downloaded them themselves
I actually did have a check for AWS keys earlier today, but as far as I can tell all the AWS keys with well defined prefixes are key IDs and not true secrets. It will still pick up AWS keys with the random string detection.
lidar isn’t able to read the state of traffic lights as far as I know, and I believe lidar based systems detect the location of traffic lights from maps
I've been trying to not take my M1 Air for granted and keep it fast, so I've been using dbxfs instead of the official Dropbox client. I hardly notice it running and still have access to my Dropbox files when I need it.
The most successful I’ve been at this is clever uses of position: sticky. You have to fall back to absolute positioning and scrolling the fixed headers in JS on browsers that aren’t as advanced in their position: sticky support though.
I got bit by this the other day when returning a nil pointer to a struct as an error. It was incredibly frustrating when I finally figured out what was going on, and I'm curious if there's a good reason to distinguish between these 2 types of nil or if it was just an oversight/mistake during the language design process.
One thing that I've appreciated now that I've spent a decent amount of time writing Go as an individual developer is that it's much easier to jump into open source code and make small improvements and fixes because the language is very "context-free." When you're reading code, the control flow is always spelled out, property accesses never magically invoke getters, and it's generally hard to make things too complicated. There are things that annoy me but the downside is almost always bounded.
Having worked on mobile code sharing a lot at Dropbox, I would say that the bridging overhead may not be a huge issue depending on how you structure your code. The approach we took was to keep all the UI completely native in the platform's native language, and put only the networking/database/model logic in the shared code. This means that typically you only have to cross the bridging layer when you hit disk or network, which is already going to be heavily IO bound anyway.
I've heard of companies being successful using C# as the shared language, but in our case we wanted to distribute SDKs, so we picked C++ since it wouldn't require us to include a runtime with the SDK. It's definitely not the easiest way to do things though if you're not already familiar with C++.
I'm not as familiar with Android compared to iOS, but ease of debugging is definitely a real problem with C++ on Android. I haven't tried very many of the other cross-platforms options, but would consider ease of debugging as one of my highest priorities since it's one of the hardest things to engineer around.
Just to clarify things (I work on the iPhone app), the only thing being transmitted in plaintext are the names of the files, not the file data or username/password, and because we are using OAuth, no session cookie is getting sent so you can't steal credentials (a la firesheep). This is also not a technical limitation, we already use SSL in our app so sending metadata over https is a trivial change.
The only reason we send metadata unencrypted is for user experience issues: setting up SSL requires extra round trips , and because cell networks have a lot of latency this makes browsing your Dropbox slower. We are close to shipping our next release and we'll definitely be reviewing our policy before we ship, so what are people's feelings on this tradeoff?
To me, the more interesting part about minecraft's success is that it gets a lot of people doing things that look like work to me for fun. Also, it does this with a high learning curve and without using any kind of reward schedule mechanics that are in vogue now. As far as I can tell (and I've only watched others play), the appeal is based on the joy of creation and sharing your creations, and the difficulty of it actually enhances the experience. It just seems so fresh compared to what everyone else is doing.
Maybe it's just overzealous copywriting, but it seems like all they figured out is that a low GI, high protein diet is better than the other combinations they tested, and are far from solving anything rigorously.
Based on the little I know about this, it probably beat being almost any employee. With $6 million invested, sold for $50 million, wouldn't you need more than a 2% stake to earn a million on the sale? Could someone more knowledgable break down how that $50 million was likely distributed, and what number employee you would have to be to get a million? (also what's the tax difference between the founders award and a million dollar startup exit)
It's strange to me that you use Guns, Germs, and Steel as an example of the virtues of wheat, when Jared Diamond called agriculture "the worst mistake in the history of the human race." (The article itself supports the basic idea that hunter-gathers were individually healthier than farmers: http://www.environnement.ens.fr/perso/claessen/agriculture/m...)