Awesome, I’m looking for frameworks like this, thanks for sharing.
Awesome, I’m looking for frameworks like this, thanks for sharing.
I want to add that, like you, I’ve become a big fan of restricting the numbers of ways to do something.
IMO, It’s more time wasted choosing, more time wasted reviewing, and makes it easier to overlook errors. I want more opinionated languages and frameworks.
I kept seeing so many different ones recommended and I kept getting weird issues I didn’t understand with most of them. I don’t often need to make a bootable Linux USB, but every time, Rufus did the job quick and easy.
Rust, because I’m lazy and I want a compiler that helps me out. Performance is a pretty neat bonus.
I really like the word you used, code smell. I often have a hard time expressing to co-workers in code reviews why something feels off, it just does.
If it was something self-hosted on the web, it may have been Clarity AI.
I think your comment embodies Rust more than any I’ve seen before
I use main
because, although I never heard of anybody actually getting offended by master
, it costs me nothing to use main
instead. Also it looks prettier and seems to be the new convention ¯\_(ツ)_/¯
Disclaimer: I don’t know much about securing the container itself. The considerations I discuss here are mostly networking.
What I’ve personally been doing is using k3s with Cloudflare Tunnel (routed using DNS like in this documentation) as an ingress.
With Cloudflare Tunnel, if you create an application in front of it, you can require authentication and add a list of allowed emails.
I could replace k3s with a different Kubernetes distribution, and/or replace Cloudflare Tunnel with a different ingress (e.g., Tailscale Funnel or more common ingresses like nginx).
Co-pilot can write some small very simple functions for me, sometimes saving me the need to look at documentation. It will still often fail at those, in my experience, and will consistently fail at anything more complex.
It will get better, but currently it’s only a small help.
I’d honestly choose a similar stack for the back-end. I have limited experience with Rust, but my impressions so far is that it’s a language that allows you to make changes with confidence that they’ll work. I feel like starting something in Rust is somewhat difficult, but contributing is relatively simple.
For the front-end, I don’t think the choice is as important, since I think that by virtue of being federated and being able to have multiple front-ends, it would almost be better for the front-end to be managed by other parts of the community. And I say that as a primarily front-end/developer-experience dev.
I would probably default to React since I’m familiar with it and it’s very popular, but would probably be tempted to experiment with something better.
I love both proprietary software and open source software, and personally I kinda like this warning.
How much of a concern it is for software’s code to be proprietary, is probably personal opinion. For this reason, maybe yellow is a bit too much? I think making these errors grayscale might be a good middle ground.
Pulling changes should be trivial after you’ve done it a few times.
Good to know! I’ve been thinking of switching my setup to Kubernetes, especially after dealing with some unstable services that need to be run in the correct order.
I do it sometimes, especially when the bug is hard to reproduce and I know exactly what’s causing it. Sometimes it’s quicker to write the tests than to test manually.
I’ve been using Zoho mail with a namecheap domain and had no significant issues, besides being marked as spam maybe once or twice?