With Linux it's very easy as long as you're okay going offline - just make an ad hoc wifi network, have the other device connect to it, then you can do whatever (Localsend, host a local webserver on the linux machine, whatever.)
Tinkering around building https://viberglass.io. It started off as a way to allow my wife to keep her website up to date without any coding skills, but ended up growing arms and legs.
It is a hosted ticketing system/agent harness platform with integrations towards other ticket systems and chat apps. It allows triggering agentic (coding) tasks without the need to context switch and/or know anything about installing the wanted tools, SDKs, IDEs etc. Ephemeral workloads in isolated containers or cloud compute. Trying to help commoditize small scale development tasks and and prevent them from getting lost in the void of the backlog.
Open source with local or AWS self-hosted, full IaC attached.
I've done a bit of research around trying to find the best, simple clients that don't need an engineering degree to set up but haven't really stumbled upon a good one yet. Claude desktop app advertises that they support all features (they don't), all the others with closer to full spec compliance are related to software development (VS Code and Continue etc.).
I find the context forge quite nice from IBM. I used a few approaches they've implemented within my Ctxpack context management solution as well.
I think the agentic use cases aside, the client side of MCPs are still lacking quite a bit and would need to mature to be able to catch up to the spec. I feel a lot of use cases exist outside of fully automated agentic approaches, since we can't really rely on LLMs yet to produce at a human level.
The underserved cases rely a lot on prompt and resource management at the moment. Being able to iterate and share those across teams to provide easy starting points to delegate tasks is something I feel would be workable for the current iteration of AI assisted work, outside of pure software engineering.
Hopefully other clients join VS Code Copilot to allow more varied approaches than just simple tool calls here. I think Copilot's approach on prompt and resource management isn't quite the best approach either though. It is still early days for MCPs in general so i think we'll see a lot of experiments in this space.
Is this fine-tuning with a more hyped naming? Let's say a company produces 100 documents per day that are appended to a knowledge base. What's the cost and delay to be able to ask questions about these docs whenever a single one is added in?
I feel differently about next.js after their latest shenanigans. Their end goal clearly seems to be vendor lock-in to the Vercel/next.js platform, whichever way it ends up happening. The current attempt looks to be to tweak and assert control over the React library, to make it Vercelified.
Had the same issue as well. Dry air in the apartment and flickering screen when interacting with an IKEA chair.
Solved by adding a "tail" to my chair using a piece of old speaker cable. There is a metal part on the bottom of the chair that the tail can be attached to.
Lyon - Lille flight on the other hand for tomorrow is 147 euros (cheap price compared to other days it seems). The flight takes a little bit over an hour, getting to Lyon airport from the city takes about an hour as well (18.20€ with public transport, 50+ with taxi/ride hailing). On the landing end transport to city is luckily cheaper and faster, 45 minutes with public transport, 15 mins and ~20€ with a taxi.
You can use coroutines with Kotlin JS. Your sentence doesn't really make sense to me though since coroutines and React have very little to do with each other.
