As much as I agree there's a risk, we should still appreciate the fact it's being disclosed upfront.

Until the datacenters happen to be in space.

Then the targets become the launch pads. Those space-based datacenters will need constant resupply and maintenance. Destroy launch capability, and their orbits will decay and all that computing capacity will burn up in the atmosphere.

We are so so so far away from self-sustaining machinery in space that it's not even funny.

There is no such thing as a self-sufficient version of any industry in space, and you should expect this to remain the case for approximately the next 10,000 years. Until then, everything that happens in space will have a supply chain rooted on Earth.

Same here for the flash card app! I literally built this for myself after reading about spaced repetition from this amazing web comic: https://ncase.me/remember/

Then… I wanted to apply this to (beginner level) language learning. And yep you have to be disciplined to go through the cards daily, but it works.

My app is 100% free so my trick was to have users write what they need, the app generates a prompt to give to any AI provider, which in turn gives you back a JSON that will be converted into a deck.

Nothing truly ground breaking, but again it works for beginner level concepts :-)

I’ve worked in VR for a long time (including visionPro) and my eyesight definitely got worse. The most ironic thing to me is how iPhone has this screen distance warning telling you to move the screen further from your face while Vision Pro is literally an iPhone strapped to your face.

I was told the issue isn’t the physical distance of the screen to your eyes, but the distance of where your eyes are focusing? So in VR if you focus on an object a meter away it shouldn’t strain your eyes as much as a phone screen 10cm away? No idea if this is scientifically proven.

Your eyes are still looking at an object (roughly?) 10cm away from your face: the screens. Your eyes are not adjusting focus. Any focus (or blur) you see in VR is simulated depth.

So yes, the issue is indeed the distance where your eyes are focussing, caused by the fact that they're constantly focussing on something very close to your face.

My optician told me its like stretching your arm while holding something heavy. At first that's no problem. But eventually your muscles will start burning and you can't hold it and even when you relax your arm it still hurts if you held it for too long.

As far as I'm aware there are no VR headsets yet that adjust the live generated depth vision based on the diaphragm of your eyes. That would be wild.

> Your eyes are still looking at an object (roughly?) 10cm away from your face: the screens. Your eyes are not adjusting focus

Technically you can absolutely have something close to your face but focus your eyes far away. If you wear glasses you do that all the time. Just imagine that your glasses are like screens that reproject what's behind them.

You're not totally wrong because there are two components to focusing, one is rotating eyes according to how far is the object and another adjusting each eye's lens. AR/VR can cause them to mismatch https://en.wikipedia.org/wiki/Vergence%E2%80%93accommodation...

However the screen imitates focal plane a bit in the distance and THAT's where your eyes are focusing. There's still can be a mismatch because it's a fixed distance, but your eyes are NOT focusing like you strapped a phone to your head which is what you are implying.

(Actually I heard AVP dev guidelines recommend to avoid putting objects too far and too close to keep everything near focal plane probably to miminize the mismatch.)

Maybe not photoshop but I’m building in the live VFX (visual effects) space, for example think touch designer or Houdini (but simpler).

My first project was an “old school” node editor done almost entirely with agentic coding. I slapped an MCP on it to see if the agents could make cool stuff and it was mostly hit or miss, but nothing too mind blowing. Blog post about it: https://sxp.studio/blog/subjective-building-a-native-vfx-edi...

My second take on this is to channel coding agents into “prompt nodes” coupled with some agent orchestration. This helps define clear data flows and API contracts for each node + overall graph. This strategy works better since we’re constraining the problem space and overall getting better results when combined (and it also plays nice with context window limitations). The current demo is a bit slow and basic but it’s looking promising! https://sxp.studio/apps/subjectivezero

For the past 2.5~3 months I've been working on a 2D/3D VFX (visual effects) editor dedicated to mac and iPhone/iPad, it was on my never ending list of fun projects to build and a perfect excuse to learn agentic coding on a domain of expertise (written in Swift/SwiftUI and Metal).

I wrote a blog post about my process: https://sxp.studio/blog/subjective-building-a-native-vfx-edi...

...and you can download the app here if you're curious (the app is free!): https://subjectivedesigner.com

Next project is going to be a pivot of that project into something related to creative coding and agentic :-)

Honestly not a bad theory. There’s definitely a huge disparity between actual productivity gained by using agentic coding done somewhat properly… and a non-stop wave of vibe coded work causing outages and churn. Pre-Covid hiring coupled with the high enterprise pricing for AI plans, it would make sense.

This is why I'm building free "spite apps" in homage to Larry David's spite stores [0]. The goal being to push back on enshitification of tech and dark patterns like mandatory subscriptions, ads and user data tracking.

As a solo indie-dev, writing free software (as in you don't need to pay anything) is fine, but I usually do not make the project (entirely) open source due to the added churn & maintenance.

In my experience, setting expectations early in my apps ("I'm a solo indie dev", "this is a free app", "you can reach out to me through email but don't expect super quick responses") helped reduce entitled users and - quite the opposite - people were super happy to get replies from me solving their problems.

[0] Blog post about it: https://sxp.studio/blog/spite-apps-the-latte-larrys-of-apps

That’s funny, I’ve actually used the same algorithm but with taxis in general, for having the same exact issue as the person in this article… but with a real driver. (All of this assuming it’s safe to keep a door open!)

Well, it's safe for me!

I’ve also started publishing a small collection of what I call “spite apps” (a reference to Larry David’s spite store when he makes his own coffee shop to go against mocha joe).

These apps are super simple in terms of privacy policy: - we don’t track you (no telemetry) - we don’t show you ads - no account - free with optional tip

Sure I don’t make much money with them but I feel like I’m pushing back on making humanity worse.