Really want to play this with a controller. Seems to me that a joystick to steer and another to adjust the sail would be really intuitive. Aside from that really fun, looking forward to future updates.
Except it is intentionally unstructured. AT proto is one way to add the structures we obviously care about for "social" internet media on top of the freedom that the web as a whole provides.
Came here to say this, difftastic is great as long as you are working in a language where it understands the language tree (most languages). Getting away from diffs being focused on line changes to diffs that understand the actual language makes so much sense once you start to use it.
Anthropic is actively blocking calls from anything but claude code for it's claude plans. At this point you either need to be taking part in the cat and mouse game to make that plan work with opencode or you need to be paying the much more expensive API prices.
I'm not particularly against AI programming but I don't think these two things are equivilent. A compiler translates code to specifications in a deterministic way, the same compiler produces the same output from the same code, it is all completely controlled. AI is not at all deterministic, temperature is built into LLMs and furthermore the lack of specificity in prompts and our spoken languages. The difference in control is significant enough to me not to put compilers and AI coding agents into the same catagory even though they are both taking some text and producing some other text/machine code.
Existing social platforms are built for profit, which modulates emotion for engagement (something kind of like entertainment, but I wouldn't say I'm entertained exactly by the rage bait I'm often fed by algorithms). Users of an open protocol might select for the same experience, or they might not, I think that's yet to be seen. This also assumes that this fantasy open protocol could also escape the pressures of maximizing profit.
I generally agree, pinning versions and then having some script to automatically update to capture security updates makes sense, except that it also assumes that every package is just using standard symver, which in my experience is something like 99% true.
But it's also missing the value of hashes, even if every package used symver, then you had a script that could easily update to get recent security updates, we would still gain value from a lockfile hashes to protect against source code changing underneath the same version code.
Some other cryptocurrency fixes this, maybe (big maybe). But as long as _Bitcoin_ is seen primarily as an investment opportunity it can't really function as a means of exchange. For the same reason that we expect and need USD to lose value over time, people need to be encouraged to exchange their currency, not sit on it forever.
Not sure what this says about me, but I ran into youtube putting a 3 video limit on me because I was using adblocking and when I hit that limit I just ended up going outside to have a lovely day. Honestly wish video limits was just a feature I could turn on.
Funny enough, awhile back they made it so that if you turned off watch history, they would disable the front page feed. Not sure if that was seen as a punishment to try to encourage people to turn back on watch history but that also ended up being a welcome change.
The engine approach seems like a solid advantage to me given that at least one decent browser has been built around it. Servo can ultimately support end users who just want a browser built off of it, and developers who want to build a browser with it. Ladybird can only support the former.
You got a back trap. When I try to navigate back from the playlist screen it goes to the processing screen, and then repeats the processing request every time I navigate back after that. Maybe a bit gnarly if that is kicking off the spotify fetch each time.
Aside from that, nice, I'm listening to one of the playlists right now.
Why do we need to keep replacing these jobs (or working hours perhaps)? If as a society we produce more for less work why is that bad? Why don’t we spend more time questioning the underlying system that makes efficiency improvements a bad thing?
You probably need the right tool for the job. I'd argue that react, Vue, and company are only best for true web _applications_, that is highly stateful projects that are more akin to standard desktop apps than web pages, ex: google docs.
If you need server side rendering that could be a sign that what you have is a lot of public indexable information and that most often describes a traditional web site instead. In that case your "old school" rails or laravel solutions are almost definitely a better choice.