481–490 of 1001 posts
With AI eating graphic designers lunch, I started to pivot and will add features for vectorizing and editing of AI generated images. I think this can become a really exciting product.
I am also working on Plundrio [2], a put.io Download Client for *arr.
My other project Server Radar [3] has been neglected lately, but I wanna move to D1 completely (currently still using DuckDB on the frontend).
The goal is to bring fast random read/writes to Java. Fun project with lots of great challenges around performance while maintaining a nice API.
i.e. instead of them having to download demos, extract them, parse them and then only query data. I want to just have a database available so they get to skip all those steps.
Not gonna make me rich but if I can get it to cover it's own costs I'll be stoked.
Was doing it on the Fuel Network, but now that they let 30% of staff go last week (including me), I’m thinking about starting fresh and doing it on Solana.
I'm working on tooling to turn kids from consumers into creators. I'm focusing on game development initially, but have plans for video production and hands on crafts. For younger kids I've modified Overcooked 2, a traditionally co-op game. I've replaced the second player with a visual scripting platform that allows kids to code their way through levels — worth noting I haven't removed co-op, there's still room for 2…
would the ability to pick up a new language/syntax be also a skill worth learning?
Check it out at https://panino.sh
It’s a TypeScript web framework that’s runtime agnostic, so it can work on serverless and servers (similar to Hono).
What’s different is that the focus is primarily just on TypeScript. There’s a CLI tool that inspects all the project code and generates loads of metadata. This can include:
• services used
• all the HTTP routes, inputs and outputs
• OpenAPI documentation
• schemas to validate against
• typed fetch client
• typed WebSocket client (and more)
The design decision was also to make it follow a function-based approach, which means your product code is just functions (that get given all the services required). And you have controllers that wire them up to different transport protocols.
This allows interesting design concepts, like writing WebSocket code via serverless format, while allowing it to be deployed via a single process or distributed/serverless. Or progressive enhancement, allowing backend functions to work as HTTP, but also work via Server-Sent Events if a stream is provided.
It also allows functions to be called directly from Next.js and full-stack development frameworks without needing to run on a separate server or use their API endpoints (not a huge advocate, but it helps a lot with SSR). Gave a talk about that last week at the Node.js meetup in Berlin.
It’s still not 1.0 and there are breaking changes while I include more use cases.
Upcoming changes:
• use Request and Response objects to make it truly runtime agnostic (currently each adapter has its own thin layer, which tbf is still needed by many that don’t adopt the web spec)
• smarter code splitting (this will reduce bundle size by tree-shaking anything not needed on a per-function basis)
• queues (one more form of transport)
Check it out, would love feedback!