@ai__exe@TheBullishEdge_@awsdevelopers@grok This is a single terminal command. The fact that people gravitate towards burning 6 light bulbs worth of energy instead says something.
What Docker tip do you wish you learned sooner?
We asked Docker Captains that question and got 7 practical lessons every engineer should know, from multi-stage builds and Docker Scout to `.dockerignore` and container hardening.
Read them here: https://t.co/ZAwh80opKz
@mbarneyjr I also think iterating between those two is useful. Elaborate on concept > refine > elaborate it further or branch to new sub-concept > refine > ...
Just because anyone can build software now doesn't mean software is dead. Anyone can bake bread in their home right now, yet 99% of us still choose to buy it from someone else. Simple products are complex! I will always be happy to pay someone to handle the nuances.
@SyedUmairCodes@fortelabs The reason is likely they're losing customers to Obsidian and the response is to paint their competitor in a bad light rather than providing better data ownership mechanisms which is what many customers want.
@fortelabs The beauty of file over app is you don't have to move your files at all.
You can open your Obsidian vault in another file-over-app app. Whatever capabilities that app supports will work. The number of apps that have parity with Obsidian grows every day, and that's a good thing.
I want to debunk the claim that I see a lot around here that Obsidian is "just plain text markdown files" which means "you can take them anywhere and open them with any app"
That simply isn't true
Yes, maybe the raw text of the notes is markdown, but many other parts cannot be moved elsewhere and opened by other apps:
1. The .obsidian/ directory contains your JSON config with plugins, settings, hotkeys, workspace state, link format, attachment paths – those can't be moved elsewhere
2. Plugin state files – Readwise's path-to-ID map, Templater's settings, Tasks plugin's database, Excalidraw's drawing data – even if plugins can be recreated, these settings cannot
3. .canvas files – JSON, not markdown. They reference notes by path and won't survive a move
4. .base files – JSON-based database/views over your notes. Same path-fragility
5. .excalidraw.md files – markdown wrapper around an Excalidraw JSON blob. Looks like markdown, isn't really
6. The link graph itself – backlinks, graph view, "linked mentions" – all computed from filenames and link references. They survive because the references are in the markdown, but they require Obsidian (or an Obsidian-aware tool) to materialize
7. Plugin-managed folders – Readwise output, Web Clipper output, Daily Notes location, Templates folder. Each is a folder whose contents are owned by an external system tracked in plugin state
8. Sync state – Obsidian Sync, iCloud, Dropbox, Google Drive each maintain their own state about what's where and what's been resolved. Move operations interfere with this state
9. Embedded query results – Dataview queries, Tasks queries, Bases queries. The query is in the markdown; the result is computed live and never persisted
So technically you CAN move your files elsewhere, but you'd destroy most of what makes them valuable – the graph, the plugin state, the canvases, the embedded queries, the sync state, and any structural intent encoded in folder placement
Which means you're just as locked in to Obsidian as any other "proprietary" app, it's just a hidden lock-in that's obscured by inaccurate marketing
Saying "Obsidian is just markdown files" is like saying "your house is just bricks"
The bricks are real and moveable – but the architecture, plumbing, and wiring aren't bricks, and those are most of what makes the house function
Sandboxes are now fully standalone. No Docker Desktop required. Just install and go.
Now with even faster cold starts, works out of the box with Claude Code, Codex, Copilot, Gemini, and Kiro. Even NanoClaw.
Get full agent autonomy. Keep everything that matters safe.
More → https://t.co/lrfmwXH4HM
With @NVIDIAGTC coming up, everyone is talking agents & autonomy.
If you’re running coding agents, isolation matters. Docker Sandboxes runs them in microVMs so you can experiment without reshaping your machine.
Run agents freely, safely: https://t.co/UNOxDX9tLt
@mbarneyjr Because they’re not trying to be productive. They’re trying to win socially in the moment.
Dropping a full LLM response into a thread serves a few psychological functions:
1. Outsourcing authority
People treat the model like a neutral expert. Posting the whole response...
The Pentagon just accepted from OpenAI the exact SAME terms they banned Anthropic for… this story is insane:
Anthropic: “We won’t let our AI be used for autonomous weapons or mass surveillance.”
Pentagon: “Unacceptable. You’re banned.”
Trump: “Every federal agency must stop using Anthropic immediately.”
OpenAI: “We stand with Anthropic. We share their red lines.”
Also OpenAI: submits bid to replace Anthropic
Pentagon: accepts OpenAI’s deal with the same exact red lines
This actually happened. Today. What an Insane timeline
It's not because anyone *can* vibe code an app that everyone *wants to*.
Anyone can grow their own vegetables, how many do?
Automation made it so a single farmer can make 100x more food.
Agentic coding makes it so a single developer can make 100x more software.