2
points
written-beyond
Joined 185 karma
- written-beyondHow very so humble of you to not mention being one of the primary authors behind TRPL book. Steve you're a gem to the world of computing. Always considered you the J. Kenji of the Rust world. Seems like a great project let's see where it goes!
- This is lovely! I'm surprised I had never heard of it before today
- > I like Rust's result-handling system, I don't think it works very well if you try to bring it to the entire ecosystem that already is standardized on error throwing.
I disagree, it's very useful even in languages that have exception throwing conventions. It's good enough for the return type for Promise.allSettled api.
The problem is when I don't have the result type I end up approximating it anyway through other ways. For a quick project I'd stick with exceptions but depending on my codebase I usually use the Go style ok, err tuple (it's usually clunkier in ts though) or a rust style result type ok err enum.
- I think the utility really comes from getting an accessible control plane over your company's data centers/server rack.
Kubernetes clusters doesn't really solve the storage plane issue, or a unified dashboard for users to interact with it easily.
Something like harvester is pretty close IMO to getting a kubernetes alternative to Proxmox/open cloud.
- I don't think it's specifically hard, it's more related to how it probably needed more plumbing in the language that authors thought would add to much baggage and let the community solve it. Like the whole async runtime debates
- You have to chill with rust. Just anyhow macro wrap your errors and just log them out. If you have a specific use case that relies on using that specific error just use that at the parent stack.
- PLEASE DON'T DOWN VOTE ME TO HELL THIS IS A DISCLAIMER I AM JUST SHARING WHAT I'VE READ I AM NOT CLAIMING THEM AS FACTS.
...ahem...
When I was researching about this a few years ago I read some really long in-depth scathing posts about Open stack. One of them explicitly called it a childish set of glued together python scripts that fall apart very quickly when you get off the happy path.
OTH opinions on Proxmox were very measured.
- I'm sorry I probably missed it then, this was like 4 years ago so I could be wrong.
- Congratulations on earning that opportunity!
Thank you for your work. I was in a position where I had to choose between minio and seaweed FS and though seaweed FS was better in every way the lack of an includes dashboard or UI accessibility was a huge factor for me back then. I don't expect or even want you to make any roadmap changes but just wanted to let you know of a possible pain point.
- I'm just as much of an avid llm code generator fan as you may be but I do wonder about the practicality of spending time making projects anymore.
Why build them if other can just generate them too, where is the value of making so many projects?
If the value is in who can sell it the best to people who can't generate it, isn't it just a matter of time before someone else will generate one and they may become better than you at selling it?
- Well at the bare minimum setting up proto files and knowing where they live across many projects.
If they live in their own project, making a single project be buildable with a git clone gets progressively more complex.
You now need sub modules to pull in your protobuf definitions.
You now also need the protobuf tool chain to be available in your environment you just cloned to. If that environment has the wrong version the build fails, it starts to get frustrating pretty fast.
Compare that to json, yes I don't get versioning and a bunch of other fancy features but... I get to finish my work, build and test pretty quickly.
- Idk I built a production system and ensured all data transfers, client to server and server to client were proto buf and it was a pain.
Technically, it sounds really good but the actual act of managing it is hell. That or I need a lot of practice to use them, at that point shouldn't I just use JSON and get on with my life.
- I laughed but also hate the fact that the world needs to worry about "file coin" ruining it for us.
- Man I really feel you, being a solo founder is tough. If it's possible for you to relocate temporarily Antler has a accelerator-esque program. They'll pay you a tiny stipend to move to Austin or NYC depending on which location you get into, for the duration of the program (5-6 weeks). You'll have like minded people around you giving you an opportunity to maybe find a co founder and get some motivation.
At the end you'll get a chance to pitch and get 100+k(varies by location) in seed and then another shot at getting funding.
Tbh their deal is doodoo compared to YC but it's a lot less competitive and you'll be out of the rut you're in right now.
As for the MVP taking time... I think it's perfectly fine, probably better even. The bar to impress it's very high now, specially since llms have made it pretty easy to add polish. I completely understand that feeling where you've already whittled your idea down to it's bone but you still can't get it done. That happens, I've faced that same problem numerous times. Whenever we thought we'd done enough we'd go out to testers and they'd point out the exact rough edges we'd intentionally tried to ignore to ship it out faster. Most of the time those edges put off people completely.
All you need to know is your target audience. If it's enterprise, having that added polish will make or break your deal if they're larger companies, specifically when they're customer 1-2. What won't matter is having 1-2 more metrics in a dashboard or maybe a customizable layout. But let's say you're report generation is a csv file that's generated client side with nothing asynchronous or email based, that would raise some eyebrows about the expected quality of service. This isn't to say you won't have understanding and patient customers, however you'll always have to earn it first.
Get the basics right, make sure it's all functioning together well and hopefully it'll all go well. The hardest part is always bd, that's where you'll truly start to feel like Will Smith walking around with your bone density scanner.
- It was a notoriously rust heavy talk, I genuinely loved it.
- Doesn't matter, they were more exciting and relevant for Devs.
- This mad man had the courage to present BOA a rust project at JS Conf. The project had it's spotlight taken by Bun and Deno. I also think the project was progressing pretty slowly from what people were expecting.
- I was really tired of spinning up docker containers to try out stuff in postgres. Couple that in with launching a database ide and managing the connection URL, makes the whole process tedious and slow.
PgPlayground is meant to be the default place for you to brainstorm, tinker and (eventually) debug in the world of postgres.
Since this is all built on top of PGLite you are restricted to wasm compilable extensions but the current catalogue covers a lot of different use cases.
Looking forward to some feedback!