6,395 karma · joined April 19, 2017
Also, non-backwards-compatible language changes fragmented the Scala ecosystem. Combined with the general trend of functional programming hype somewhat dying down in recent years.
I think it's fitting that a story that was originally an ancient poem, should sound ancient and poetic.
But an LLM has to interpret your words and make judgment calls about the logical details, which is a very different thing. An LLM sufficiently intelligent to make acceptable judgment calls in all situations (acceptable enough to ship to production without human review of those details) would likely be indistinguishable from AGI.
Hard for me to see this as anything other than fly.io committing suicide. AI sandboxes are a crowded product space, basically a complete commodity at this point, and the new CEO will likely focus on profit to the detriment of creative vision.
Happy to be proven wrong though.
Another explanation could be the content itself. Does your game have anything at all to do with computer hacking or sexual content? Is there graphic violent language? People commonly report being unable to use AI to work on such things due to guardrails.
I'm also trying to figure out why OpenAI put out a press release about this. In what way is this not admitting to a federal crime?
So then ask yourself: why did they take it off? Pondering the implications of that question is the entire point of this short story.
In a meta-sense, I don't think G.B. Shaw intended this quote to be taken as an absolute truth by the audience.
And, even taking the quote itself at face value (pretending the fictional character who wrote it was a real person), I think it's referring mostly to political progress. Indeed, most times that political institutions have been upended, it was by people who were not happy with the status quo. But I think that's a different sort of unhappiness from the unhappiness of not being satisfied with your life.
> hands off to two of its own IRs before writing WASM-GC by hand
So it's not "one pass" lol. Do you know what a pass is?
Not that it matters - this AI is claiming "one pass" as though that's a good thing, but it's usually not. One-pass compilers can't typecheck forward references.
> Mozilla uncovered numerous privacy problems across various apps, but Stardust was the only one found sharing detailed reproductive health data with another company.
> The report found that Stardust sends users' health information to a data management company called RudderStack, which isn't named in its privacy policy. That data includes pregnancy status, birth control, moods, alcohol consumption and specific symptoms like tender breasts and stomach cramps.
> Companies often share data with outside services to process information and analyse user behaviour. There's nothing unlawful going on, and there's no reason to think RudderStack (or any company mentioned in this story) is doing something nefarious.
> However, experts say it's inherently risky when your data spreads to more places. It creates another opportunity for security breaches or legal requests for information. Besides, you may just be uncomfortable with another company seeing your health data.
> A Stardust spokesperson says the company only uses RudderStack as a "technical pipeline" to route data into its own analytics systems, and the app doesn't share anything that could allow RudderStack to identify your name or contact information. "Additionally, RudderStack is contractually prohibited from selling or using it for its own purposes," and RudderStack doesn't store the data long-term, the spokesperson says.
> "People deserve better," says Shoshana Wodinsky, a privacy research analyst who conducted Mozilla's tests. At the very least, she says, you should know what's happening.
I usually use the pointy end of a plastic flosser.
So, like, the JVM with its "initial heap size" setting? After reserving that space from the OS on startup, pieces of the space are then handed out by the JVM's internal allocator, where and when needed.
If initial heap size and max heap size are the same, that initial one is the only malloc() call that ever happens. Not as common for desktop software, but a common best practice when deploying JVM applications to servers.
(I think we're perhaps tripping over two different meanings of "allocate" - you can "allocate" in the sense of calling malloc(), and you can "allocate" a piece of that reserved memory to a particular scope/function/object without actually calling malloc.)
> Allocating memory as needed isn’t a Rust-specific idiom.
I never said that.
> only works for very specific use cases.
It's not clear to me what you mean by this.
But, if you could wave a wand and eliminate all legal and liability hurdles to self-driving, automobile deaths would plummet. They're way safer than the average human driver. The technology is definitely capable, our society just isn't ready for it.
Case in point: https://github.com/postgres/postgres/blob/master/src/common/...