vitamark
Joined 6 months ago
Joined 6 months ago
(leaving out cases where your genius GPT-12 Galaxy Ultra agent hacks the sandboxing from inside)
From outside of the US, I see "Lake Ontario (Lake America)" in Google Maps, the same way as with the Gulf of Mexico. I see "Persian Gulf (Arabian Gulf)" and "Sea of Japan (East Sea)".
Some names are given from one perspective (like rivers and mountains), like Rio Grande river or Mt Everest.
Very accurate, thanks, looking forward to that.
in 1.17 I get basically a three-level hierarchy: project -> workspace -> session
I could say I rarely use more than one session per workspace (not including subagents), but switching between projects as totally separate contexts works good.
Tabs on the other hand are less organized, I can see them being fine for sessions in one project (although sidebar is more ergonomical on both desktop and mobile)
Keep in mind that this is coming from someone who has a live browser tab counter website: https://tabs.evtn.me/
I updated one of my opencode containers today and had to downgrade it back because:
1. Worktree/workspace support is gone altogether. No way for agent to work in parallel on different things safely except prompting it directly to create a worktree.
2. Seeing multiple sessions properly now requires opening tabs for those?
3. In general, switching between several projects/sessions/whatever stopped working, and command palette is hotkey-only.
Issues about the new design just sit in an endless unsolved pile on GitHub which seems hopeless. And an agressive stale bot is not helping with that.
I came to OpenCode because it seemed hackable and simple, and at this point it seems like a "move fast break a lot" project that you got to live with.
(rant over, sorry if this is addressed to the wrong person, just needed to vent a bit)
I did get relatively good scores in reading speed back in primary/middle school when we took such tests, so maybe there's an explanation. At the same time, writing/speaking is a very resource-intensive task for me so I tend to be silent a lot (and then drop a pile of sentences on the unsuspecting people I'm with)
A person who has something to say often has trouble stopping writing. Outsourcing writing to AI then feels like the opposite, as if the author doesn't care but wants to just spew some content.
that's a bitrate of 1GB per 9-12h, and for cases when it's too much I just have cached music on my device (I'm lucky to have mostly empty storage on my 256gb phone)
we're all very grateful for cool toolchains and tools but I think people wouldn't even poke a stick at it if it doesn't pass a huge test suite (that is not vibe-coded, probably nodejs test suite if they have one?).
I really feel like humans argue too much about how computer programs think and at the same time too little about how humans think. The topic is criminally underresearched and the existing research is all over the place.
Though there are recent experiments showing that unconscious brain retains language processing abilities [1], so the two might be as well independent systems
Is it really? LLMs don't have words inside, for the most part they operate by applying transformations to a vector that does not contain any words at all. Words that come out of an LLM are just what sampler gives us by looking at the vector that is the result of those transformations.
Does this vector contain a world model? Some form of thoughts or reasoning to arrive at the result? That's an open question really.
Sure, rerunning that whole process for each token might not be the best solution, although that's an open question too. But saying that LLMs operate on words first is too big of an oversimplification
What I find with any site is that without a good foundation you're bound to repeat same styles over and over, and with one you don't get any point with Tailwind.
Expression `select(User).where(User.id == user_id)` does look simpler and cleaner than `select(User).where(eq(User.id, user_id)))`.
Maybe there is an actual eq function of sorts that allows that, and it's not a life-or-death difference here, but as far as convenience goes, it works well. And typecheckers are good enough to be able to let you know what's the return type.