I think you fundamentally misunderstood any aspect of society, civility and community building if you adhere to such ideas. The issue at hand is bad governance and resource management, not that “immigrants should be kept out”.
Immigration is needed at different parts of a country’s economic timeline, and the levels of immigration needed can vary depending on your needs to balance labor supply and demand. This isn’t about racism, or cultural differences. This is about good governance.
Doctors with proper training will do what they were trained for. Maybe personality traits play a role as well secondary, but stuff like culture is just noise compared to what really matters.
Maybe lol? There is basically no way of knowing cost going into anything or whether or not it will wind up being covered. Also when they get around to demanding money they won't necessarily do it all at once, you can get a bill a year after a visit even though they billed you the first time 4 months ago or some shit. A doctors office can handle this well with significant effort on their part or not.
It’s something I keep meaning to play. My wife got a decent headset for free through work about three or four years ago, and after we both played a collective 15 minutes of Beat Saber it’s been gathering dust on the top shelf of a closet ever since. We used to play tons of DDR and Wii Sports so we like moving-around games but the thing just didn’t interest either of us, at all.
Alyx just hasn’t been quite enough motivation for me to take on the project of figuring out how to get it hooked up and working, though I did at one point do the few minutes of googling to confirm it might work (I think it’s one of those Facebook ones, and as I recall it is supposed to work for Alyx but I’ll need some cable or other). Especially since it’s a fairly short side-story, it’s just not enough juice to be worth the squeeze.
The conclusion of the series (until it’s not the conclusion any more—yeah, I know how franchises work, lol) though? That’d do it.
If I already had it out and used it regularly I’m sure I’d have played Alyx by now, but with that being the only thing I have any interest in doing with it, just not enough to get me to set the thing up for that alone.
There are rumours that they are working on this, but I assume they've chosen to keep the exact software experience of the Frame under wraps for now. It would certainly make the experience of gaming on a giant virtual screen even better!
I described my experience using Claude Code Web to vibe-code a language interpreter here [0], with a link to the closed PRs [1].
As it turns out, you don't really need to "save the state"; with decent-enough code and documentation (both of which the LLM can write), it can figure out what needs to be done and go from there. This is obviously not perfect - and a human developer with a working memory could get to the problem faster - but its reorientation process is fast enough that you generally don't have to worry about it.
I've also had success with this. One of my hobby horses is a second, independent implementation of the Perchance language for creating random generators [0]. Perchance is genuinely very cool, but it was never designed to be embedded into other things, and I've always wanted a solution for that.
Anyway, I have/had an obscene amount of Claude Code Web credits to burn, so I set it to work on implementing a completely standalone Rust implementation of Perchance using documentation and examples alone, and, well, it exists now [1]. And yes, it was done entirely with CCW [2].
It's deterministic, can be embedded anywhere that Rust compiles to (including WASM), has pretty readable code, is largely pure (all I/O is controlled by the user), and features high-quality diagnostics. As proof of it working, I had it build and set up the deploys for a React frontend [3]. This also features an experimental "trace" feature that Perchance-proper does not have, but it's experimental because it doesn't work properly :p
Now, I can't be certain it's 1-for-1-spec-accurate, as the documentation does not constitute a spec, and we're dealing with randomness, but it's close enough that it's satisfactory for my use cases. I genuinely think this is pretty damn cool: with a few days of automated PRs, I have a second, independent mostly-complete interpreter for a language that has never had one (previous attempts, including my own, have fizzled out early).
Thanks for sharing. I hear people make extraordinary claims about LLMs (not saying that is what you are doing) but it's hard to evaluate exactly what they mean without seeing the results. I've been working on a similar project (a static analysis tool) and I've been using sonnet 4.5 to help me build it. On cursory review it produces acceptable results but closer inspection reveals obvious performance or architectural mistakes. In its current state, one-shotted llm code feels like wood filler: very useful in many cases but I would not trust it to be load bearing.
I'd agree with that, yeah. If this was anything more important, I'd give it much more guidance, lay down the core architectural primitives myself, take over the reins more in general, etc - but for what this is, it's perfect.
I'm sure we all assumed that they came from the same codebase, but I don't think any of us were expecting the features to be shipped to both platforms and disabled at runtime as required. I expected a common codebase with the iPadOS features disabled at compiletime for iOS, and vice versa.
But like... why? Why does that matter at all?
reply