1
point
jarboot
Joined 282 karma
- "Needs to be gone" is the operative phrase here. An alias of `description-long` to `description_long` has no specific technical need to be removed.
The conditions that lead to having two tokens pointing to the same functionality should be prevented, but in this case it is a "de facto" alias which no amount reasonable amount of labor could fix.
- The current approach of the maintainers terrifies me -- de facto standards should be respected. Even if something is invalid like `description-file`, if it is present in 12k repos it should raise a warning and not break anything.
In the rationale for this that I can find [1], a maintainer says the following:
> I'm inclined to say we should do it, even though it will cause some disruption.
They also say an alternative is to "accept the status quo", which is exactily what they should be doing. I can't find maintainers giving a compelling reason not to support this status quo of `long-description` as an alias to `long_description` besides "simplifying code." Code simplification should never take precedence over massive breakage of compatibility.
[1] https://github.com/pypa/setuptools/pull/4870#pullrequestrevi...
- From Gandhi's commentary on chapter 1 of the Bhagavad Gita:
> ... evil cannot by itself flourish in this world. It can do so only if it is allied with some good. This was the principle underlying noncooperation—that the evil system which the [British colonial] Government represents, and which has endured only because of the support it receives from good people, cannot survive if that support is withdrawn.
If you are a good person working for the big G...
- The entire photo is the finish line. Look at the color of the ground -- it's cream, the color of the lines on the track, while the track is blue. Each vertical line of the photo is taken in the same position on that finish line.
The first "line photo" is the right-most column of pixels on that photo. The next photo is the second-to-the-right column, etc. This way the winner can be determined as the line first photo that has the contestant's torso in it.
- I really want to sign up and share a creation, but when I do either sign up or sign in, it gives me a firebase url that just redirects me to the app store. I can't find any way to sign up.
I'll click "Sign in to Downpour", it will bring me to a "Open link in App?" page, I press "Open", and then it brings me to a "Downpour -- make a game" page and I click open again which brings me to the app store. The app is installed on my phone.
- I tried your challenge to create pizza. My goal is to get some kind of food, but combining combinations of water, plants, fire, etc are way more likely to produce dragons and universes. I eventually got to chestnut which got to bread, but it was a lot easier to get to "Toast Toast Toast" or "Chestnutzilla" or "Treasure" + "Toast" = "Pirate". I finally got "Tostzilla" which has a pizza emoji, and then "lunch", and "breakfast", and "party"+"toast"="celebration" ?? but it feels random and illogical at some point I just gave up.
So to me it feels like playing against a soulless vector database rather than something engaging and well-crafted. I think what gives me this impression is that things are commonly related to each other using words rather than their meaning -- getting from "pirate" to "captain crunch" to "serial killer" is obviously following lines of language rather than the core concepts that relate objects. This is directly opposed to the actual act of crafting which is 100% rooted in the material world and has no relationship to language.
Maybe I'm losing my imagination, but doing it like you suggest, creating challenges, is makes it more fun. I think I'm just tired of thinking in language.
I'm also seeing a lot of my favorite game creators on twitter enjoying the toy and I'll trust their taste over mine :)
- The request looks like "https://neal.fun/api/infinite-craft/pair?first=Phoenix&secon..." so it's probably typically caching the combination of phoenix+seeds but if there is no cache entry it would use llama to make up something. If there's a lot of attention on the site the llm service might be down or overloaded. And given the exponential/factoral (?) amount of combinations this may be reached surprisingly quickly. Just a guess.
As an aside, the game is technically interesting, being a really simple example of using llm generation for game mechanics. But it is not engaging at all and feels nonsensical to me, especially when compared to little alchemy https://littlealchemy2.com/.
I'm not trying to be negative and this isn't a dig on creativity of the wonderful Neal but more points to the immaturity of llms applied to games, maybe to my overexposure to chatgpt, and maybe a prediction that human touch will always be required to make something entertaining. I'm curious how llms will fit into an engaging game experience in the future.
- I've been thinking about making a cross-platform mobile app but don't want to think about react native, touch javascript, or fiddle with xcode any more than I have to.
Is it accurate to think that I could instead use godot to create a cross-platform app to eliminate complexity from react native while creating something that is performant/native across ios/android?
- 7 points
- I am 25 and from my observations of social media-active people I connect with that were born and are living in the US, it's a split between instagram and snapchat. Many are active on snapchat stories and instagram.
My observation is that that IG is more popular with urban, liberal, artistic (people create and/or sell art), style-oriented, older audience. It feels more professional and public, and it's common to follow accounts like celebs, artists, businesses, or generally people you haven't met in person. Artistic and lifestyle people will use IG chat to communicate and connect. For example a yoga studio or music venue may post events there. It feels like it's taking the role of a more image-oriented facebook. The stories are very popular too.
Snapchat is (in my observation) more popular with midwestern/rural/suburban people, and the network is more friends of friends or maybe people you met at parties. It's much more casual and it's more likely you have met the people you connect with. Trendy urban people I have met have shunned it for a while and think it's childish, but some are coming back. Either way it's the primary way I communicate with certain contacts besides imessage/sms (mainly through the chat). I'll post something to a story and someone will comment on it or vice versa.
Anecdotally snapchat was very popular in high school and early college and then waned, but became more popular again recently for some reason (I'm getting more and more views on my stories than before even though I'm not adding friends that frequently). Also when I talk to foreigners, they see it as a childish thing that was a fad in the 2010s, but people in the US (especially suburban types) are very active on it and have been for a while.
I'm bullish on snapchat and it's my largest "fun"/risk investment in a single company because of the stickiness it has with people my age and younger, specifically in a more midwestern rural/suburban demographic. Also the snapmap feature is phenomenal and will be the next thing other tech companies start imitating.
- If you googled a bit, you could have found the answers to 2 and 3: https://www2.census.gov/programs-surveys/decennial/2020/tech...
- Shanghai is a city with a unique role in the progression of the CCP and its global efforts. Also PLA Unit 61398 is in Pudong, the shanghai district mentioned in the article. Overall there's a lot of CCP/PLA-adjacent tech talent in the area, and of course the local police still ultimately report to the CCP.
Does this handle the case where there are longer-running activities that have low CPU usage? Couldn't these be canceled during scalein?
Temporal would retry them, but it would make some workflow runs take longer, which could be annoying for some user-interactive workflows.
Otherwise I've seen needing to hit the metrics endpoint to query things like `worker_task_slots_available` to scale up, or query pending activities, pending workflows, etc to scale down per worker.