Reading this is strange to me because it's exactly what I've been working towards for the last 14 years or so... But TBH, it came together piece by piece. I've built a full implementation in Node.js with a set of declarative frontend components. https://github.com/Saasufy/saasufy-components?tab=readme-ov-file#saasufy-components And https://saasufy.com/ It's surprising how much functionality you can assemble with... - Source: Hacker News / 15 days ago

I'm working on the backend your AI doesn't have to build https://saasufy.com/ For vibe coders. With a focus on: - Security - Analytics - Realtime capabilities. - Source: Hacker News / 18 days ago

This is a good article. I've been working on such infrastructure to facilitate safe vibe coding with a focus on simple access control and analytics. https://saasufy.com/ I think this is spot on but the new abstractions are yet to be popularized but I'm seeing some clear patterns arise. This is something I spend a lot of time thinking about because the new abstractions must fit within existing paradigms to provide... - Source: Hacker News / 29 days ago

This is neat. I've been dreaming of something like this to host frontends connected to my backend platform https://saasufy.com - Because it's built with WebSockets, it doesn't have CORS limitations so I can literally make Claude Code create an index.html file on my computer's file system, then open it directly from the file system by double-clicking it (served via file:// protocol) then, when I'm happy, I can grab... - Source: Hacker News / about 2 months ago

When building agent integration for my serverless backend https://saasufy.com/, I decided to use skill markdown files curl commands inside instead of building out MCP tools. The curl command is just so popular, models are really good at using it. Also I like that curl is for bash and my platform requires JSON payloads; it makes the separation clear to the agent. I find it to be very reliable. - Source: Hacker News / about 2 months ago

Agreed -- but one of my original observations was how the syntax checker at https://phpcodechecker.com/ did not flag the "illegal" spaces if PHP 5.6 was selected, but did flag them if 7.4 or 8.1 is selected. This prompted my original question whether something changed from v5 to v7 in terms of white-space interpretation. Source: over 3 years ago

Https://phpcodechecker.com/ // reports errors in your code. Source: over 4 years ago

I used this website: https://phpcodechecker.com/. Source: over 4 years ago