jcmfernandes

8 ms·

1. 61.▲
   by jcmfernandes 2y ago

   Isn't the answer always "bugfixes and increased stability"? :)
2. 62.▲
   by jcmfernandes 2y ago

   That is correct :)
3. 63.▲
   by jcmfernandes 2y ago

   > Fun fact: you don't need CSRF protection at all if your API is strictly JSON-based, or uses any content type that isn't one of the built-in form enclosure types. The Powers That Be are talking about adding a json enclosure ty
4. 64.▲
   by jcmfernandes 2y ago

   Correct, they are a part of WASI. Indeed, different things, but well, tightly related. Made sense to talk about them given the chat on bridging gaps in bazel using WASM.
5. 65.▲
   by jcmfernandes 2y ago

   Yes, the concept is old. I may be wrong, but to me, this really seems like it, the one that will succeed. With that said, I'm sure many said the same about the technologies you enumerated... so let's see!
6. 66.▲
   by jcmfernandes 2y ago

   This is great. The future is made of libraries packaged as WASM Components.
7. 67.▲
   by jcmfernandes 2y ago

   Yes, but WASM gives you more, especially WASM Components. E.g., FFI doesn't offer sandboxing, and unloading symbols is tricky. The WIT (WebAssembly Interface Types) IDL (+ bindings codegen) makes objects' exports explicit, but mor
8. 68.▲
   by jcmfernandes 2y ago

   Thanks for your feedback. Components and WIT seem powerful to me, though. I'm building an execution environment on top of a niche programming language, and components allow me to easily extend it with libraries written in other program
9. 69.▲
   by jcmfernandes 2y ago

   I see, thank you. I'm trying to get up to speed with the whole ecosystem as I have a use case for it. I would like to interact with WASM components from a go binary, but it seems like wazero doesn't and won't support the comp
10. 70.▲
    by jcmfernandes 2y ago

    I thought that WASI and the component model were separate specs. Am I wrong?
11. 71.▲
    by jcmfernandes 2y ago

    Gary was a visionary: https://www.destroyallsoftware.com/talks/the-birth-and-death...
12. 72.▲
    by jcmfernandes 2y ago

    You use k8s to manage the machines where wasmCloud runs, and wasmCloud to manage the WASM apps that run on top of it. That's at least my understanding.
13. 73.▲
    by jcmfernandes 2y ago

    I got to know more at your stand during last year's FOSDEM. Very cool project!
14. 74.▲
    by jcmfernandes 2y ago

    Shameless plug: I work to make this easier at https://www.slashid.dev/products/identity-protection/ And yes, you're absolutely right. Attempting to manage NHIs across multiple cloud/service providers wit
15. 75.▲
    by jcmfernandes 2y ago

    Give it a try and try to come back with your sanity intact. I dare you :) It's mess.
16. 76.▲
    by jcmfernandes 2y ago

    I built a simple tool to generate binstubs and work around this problem: https://github.com/jcmfernandes/go-tools-binstubs However, having multiple tools share a single mod file still proves problematic occasionally, d
17. 77.▲
    by jcmfernandes 2y ago

    I can strongly agree with you while understanding how the OP feels (and I certainly don't condone all his advice). IMO, culture plays a role in it; as an EU citizen, layoffs are effectively rare here. I was laid off once, when I was be
18. 78.▲
    by jcmfernandes 2y ago

    I gave up on mine. It's more than obvious to me that it doesn't care if there's ink in the cartridge after some time and just starts malfunctioning.
19. 79.▲
    by jcmfernandes 2y ago

    I understand that, but even nixos refers to configuration.nix as a "configuration file" in its documentation. IMO, it's totally OK that people have different opinions on what are best practices. However, I would still like to
20. 80.▲
    by jcmfernandes 2y ago

    On how to assemble your config. Every config I open does things a little bit different, from the get-go, when using flakes. Add package sets as overlays to nixpkgs or pass inputs downstream? How to parametrize "system"? What'
21. 81.▲
    by jcmfernandes 2y ago

    I'm relatively new to nix, and this cut close: > At this point NixOS has been around for 2 decades, but it still feels like it has not settled on good recommended workflows for incoming users. Yes. This was a major pain point when I
22. 82.▲
    by jcmfernandes 2y ago

    In the long-term, how different do you want to be from Apache Pulsar? At the moment, many differences are obvious, e.g., Pulsar offers transactions, queues and durable timers.
23. 83.▲
    by jcmfernandes 2y ago

    These things are expensive... I ended up going with a DAS, a Terramaster D6-320. It was less than half the price (270€), suits my context (network-access isn't a must; the DAS is small enough to fit behind my TV), it doesn't &quot
24. 84.▲
    by jcmfernandes 2y ago

    I'm using connectrpc, and I'm a happy customer. I can even easily generate an OpenAPI schema for the "JSON API" using https://github.com/sudorandom/protoc-gen-connect-openapi
25. 85.▲
    by jcmfernandes 2y ago

    To those pointing out that it's dynamically typed, meta's rust implementation - that they use in buck2 - supports type annotations.
26. 86.▲
    by jcmfernandes 2y ago

    This is also one of my major complaints at this point. I'm building a developer tool with starklark resting at its core and I had already came across your work. I wish the starklark team had addressed it at this point.
27. 87.▲
    by jcmfernandes 2y ago

    > No foreign key constraints Wat?
28. 88.▲
    by jcmfernandes 2y ago

    There are LOTS of them. Anything that allows you to link your Google/Facebook/etc. account to another system, so that system can perform actions on your Google/Facebook/etc. account on your behalf. Examples: Slack (e.g.,
29. 89.▲
    by jcmfernandes 2y ago

    Since OIDC is a layer on top of OAuth 2, it inherits its complexity. OAuth 2.1 (currently draft) will help bring some sanity. GNAP - https://oauth.net/gnap/ - will, one day, tie everything.
30. 90.▲
    by jcmfernandes 2y ago

    Correct. OAuth is for delegated authorization. OpenID Connect for authentication.