everyone's saying it "drove upside down" - kinda missing the point - this car IDLED upside down.
It went forward a little, but yes not really driving. But the upside down part is just a demo of the vacuum thingie technology, not the main point
Readit Newsashenke commented on · Posted by u/zfg_
> "He explained that I was looking at a plan for a restored ecosystem. It was also a perfectly adapted money machine. There was a large area where the ancient elephants could graze, and this would be funded, in part, by carbon-offset payments from governments and corporations. The carbon value of a single elephant is about two million dollars, he told me. (An elephant increases biodiversity, in part, by spreading seeds in its dung and by crushing dense vegetation on forest floors, giving slow-growing trees the space to survive.) He added that the interesting educational opportunities and “sexiness factor” of Colossal’s creations would make its carbon credits “trade at a premium.”"
So it's a startup, valued at 10 billion?! How exactly do they plan to make money?
Seriously, could anything be more 21st-century? Resurrecting extinct animal species (ones that supposedly went extinct naturally, mind you, not because of humans – what's the point then?) just to reintroduce them into parks and sell carbon credits.
Paywalled so I have to ask, why the dire wolf? Why not an animal that humans drove to extinction like the dodo bird? Is it because dire wolves sound cool and were in video games?
From the article, it looks like they have multiple teams working on multipe animals at the same time. But the dodo team is going slower than the mammoth and the wolf :
> Keyte added that her team was still a long way from bringing back the dodo. For one thing, the methods for growing and manipulating the embryonic precursors of avian sperm and eggs in a lab setting have been developed for only two birds: the chicken and, recently, the goose. Keyte said, “It’s been almost twenty years since culture conditions for the chicken were established, and those culture conditions have not worked for other bird species, even ones that are really closely related, like quail.” She added that, despite the dearth of related research, her team was getting better at growing the sperm-and-egg precursors in birds: “We’ve gotten to the point where we feel like we can start doing some migration assays”—a technique for studying how the cells in an early embryo begin to differentiate. Once the researchers got the basic method for growing bird cells down, they could use the technology not just to develop a dodo but also to help replenish populations of endangered birds. The team had already identified some species that could use the help.
I think a competent 5yro could make a better pelican on a bicycle than that. Which to me feels like the hallmark of AI.
I mean, hell, I have drawings from when I was eight of leaves and they are botanically-accurate enough to still be used for plant identification, which itself is a very difficult task that people study decades for. I don't see why this is interesting or noteworthy, call me a neo-luddite if you must.
The complexity is that it's not a drawing : It's SVG.
So it's code that must, in the end, display a pelican, so it's one step further.
ashenke commented on Go European: Discover European products and services goeuropean.org/... · Posted by u/doener
This redirects to the submission link!
ashenke commented on Making any integer with four 2s eli.thegreenplace.net/202... · Posted by u/LorenDB
ashenke commented on Trick to find commands in the terminal quickly github.com/madprops/blog/... · Posted by u/Toby1VC
For these commands I want to rerun, but not often enough, I add a comment to the command like `yay - Sc # clear pacman and yay caches` so it's easier to search in the future
> On top of that, once you finally get a feature merged and deployed, it can often happen that there’s a bug causing users to have a poor experience. Since your new feature lives directly in the code, deactivating it requires rolling back the code you merged, building it, waiting for the tests to run, and redeploying the application
Why aren’t you using feature flags to gate new behavior/functionality?
This is literally what the article advocates.
It pushes things to the extreme where every code you write would be on the main branch and behind a feature flag
Virtually everything is easier. How much easier is up for debate.
Part of the issue is that everything is interlocking. Small gains in multiple places end up feeling so, so much nicer, even if they may not seem like it. So for example, the index in git is a workflow pattern in jj, not a built in feature. This means that you don't have `git reset` with `--soft` vs `--hard` vs `--mixed`: You just have `jj edit`. This decision also means `jj rebase` can be entirely in memory, which means it's fast. But that wouldn't matter if conflicts weren't a first-class concept in jj, so things like rebase always succeed and immediately. Which doesn't sound like a big deal but you find yourself being able to rebase way more often and way more easily...
It's not that git is bad. And it's not that it's bad at a specific thing. It's just that taking some of the other sides of some of the tradeoffs means that you get something that's smaller but also more powerful. And that's cool.
I think the "mega merge" plus `jj absorb` might be one of the more flashy things: https://steveklabnik.github.io/jujutsu-tutorial/advanced/sim...
but I don't even do that. The basics are still just nicer.
So I've been hovering around jj for a while, trying to understand how it works, without suceeding in having a good mental model around it.
I looked at this megamerge workflow and it's the first one that "clicked" for me (even though I'm not sure I understand the magic behind jj absorb, but I'll look into it).
One thing though is that I don't quite understand how it would work in the context of a real git repo. Let's say I work on two branches, main and feature1, I'd create a [merge] commit that is has the two bookmarks as parents. But if after a fetch main has new changes, do I need to discard the current [merge] and recreate it again ? I can't find a way to just say "Update the parents so they track these bookmarks".
I just tried it on a real repo, working on a change in a branch, then on a change on another branch, then adding a third branch I needed to work on that was not a parent yet, but this seems like a lot of boilerplate to always recreate my megamerge setup so I think I'm missing something