clvx

Spotify's app is bloated. I've been premium since 2014 but I'm reaching my limit of all the garbage the app has. I wish I could deactivate all podcasts and audiobooks. I don't care about it. I don't mind AI music and ghost artists but I wish looking for some sort of music would bring up playlists from actual people instead of the bubble generated AI from Spotify. I feel instead of exploring and expanding my limits when I search for music I'm just self padding myself.

debugging and error messages are still hard to deal with. Also, flakes should become standard at this point. Documentation on how to load modules and explore modules using nix repl is also lacking and/or frustrating. It definitely has rough edges. I do hope it will improve.

I have a hot take on this. I don’t care how you build and deploy as long as it’s reproducible and the whole process can be tracked in their metadata. I’d rather have a process validating CI/CD stages and artifacts metadata in a central db than unifying pipelines that won’t get standardized due communication complexity. This way I can have a conversation on visibility rather than code edge cases.

Exactly. This is how it works in vim/nvim using the copilot.vim plugin. Unless it's refactoring multiple files, I don't see the value. Now that you can choose your own model, I don't see many benefits with Cursor.

I tried doing a dev environment on Kubernetes but the fact you have to be dealing with a set of containers that could change if the base layer changed meant instability in certain cases which threw me off.

I ended up with a mix of nix and it's vm build system which is based on qemu. The issue is too tied to NixOS and all services run in the same place which forces you to manage ports and other things.

How I wish it could work is having a flake that defines certain services, these services could or could not run in different µVMs sharing an isolated linux network layer. Your flake could define your versions, your commands to interact and manage the lifecyle of those µVM's. As the nix store can be cached/shared, it can be provide fast and reproducible builds after the first build.

Get a german shepherd dog. They will wake you up at the same time everyday whether you like it or not.

they ship a flake.nix and a devbox.json configuration. Unless stuff is missing, this should be portable to produce the required binaries for linux/mac you need. This seems to produce typescript and golang.

Impressive Missoula, MT has a median higher than many metropolitan areas like Austin. One of the factors of the house market explosion in western MT.

In a related note, I was checking for tech meetups (at meetup.com) in Missoula and Bozeman and except for Montana programmers, there's no much there. There are a few slack communities but nothing specific for technologies or other groups.

Off topic but some day you could live off grid with your own solar fusion mini reactor powering your own hardware that enables creating your own stories, movies and tales. No more need of streaming services. Internet would be to obtain news, goods and buy greatest and latest (or not) data to update your models. Decentralization could be for once not as painful as it is now; however, I still believe every single hardware vendor would try to hook to the internet and make you install an app. Looking forward to this AI revolution for sure.

Someone somewhere outside of your country's legal entities can still do all the things your country doesn't like and there's little to stop them. Governments might limit legal or commercial usage but it doesn't mean it won't exist.

One thing I don’t trust about this approach is when using coding assistants, the generated code might not be what you need at first and then you keep iterating or use what’s necessary from the output but in ops that approach can make things worse burning more money and trust.

I think this is the ideal spot. I wouldn’t trust an agent doing remediation but I would gladly take input from them regarding services that are acting up or have a trend to disaster. This would improve using my time in what matters instead of cleaning data to determine what matters. In a perfect world I’d like to provide my threshold or what success mean to the agent and expect information without me tweaking dashboards, configuring alerts, etc.

On top of this, having ipv6 configured makes things harder to discover but not impossible (As long as you don't use ${ipv6_subnet}::xxxx for your hosts). You can avoid NAT and just expose the nodes you need. Most ISP assign /56 or /64 which is a humongous amount of ips. It's nice if you are just using a flat virtual network in your home lab. The amount of scanners I see for my subnet are non existent at the moment.

I like this but one of the issues with this approach is if no Docker images like traditional configuration management tool, you are going for a world of pain. Docker and Docker images have tons of best practices already defined for plenty of use cases. If it's already containerized; then, jumping to any orchestrator that supports OCI images is more about adjusting the business to a new set of operations.

Better description of him: https://es.wikipedia.org/wiki/Corrupci%C3%B3n_en_el_gobierno...

Not gonna lie. I designed a system that looks exactly like this. However, the plugin system was an operator instead of annotating a service which is kinda cleaner but it still felt dirty. A better approach is having a service registry to track the versions, values and clusters where this has been pushed but that means you needed a different API or extend the k8s API and deal with the whole auth/authz system.

I think the biggest hurdle to implement a solution like this is your application MUST be a 12 factor app which sadly is not the case from what I've seen. Many devs hardcode values when shipping their code and containers which make it really difficult to add nodes to a DAG. Had this change, SDLC testing would be waaay easier.

In the same space, labeling of all services is a thing. As you are annotating it can be tracked but if you had different gateways or destination routes or other things that need to be tweaked at the mesh level, it could be daunting to track it. In my case, I ensure the whole mesh representation of a version could be tracked by a label so if you had a app=vote1,version=release-4,feature=shiny you could track the shiny components across the whole cluster.

Another hurdle is you are tied to a service mesh implementation. Istio is ok but it can be a beast. It also constraints your org to implement other networking alternatives which is something we wanted to explore.

I do like the project uses Nix =).

Great work.

I recall the bug/cheat to duplicate spell books. Those fireballs and lightning chains at max level could wipe everything in seconds.

As someone who has been in both industries (defense and gambling), be honest with the product. Tech can be nice and it has interesting challenges but if your growth is outside the tech, then you are going to struggle.

One item the DevOps mindset missed was reproducibility. Fast feedback loops in spirit tell to have a way to know what’s wrong but it doesn’t tell how to reproduce it as you have layers and layers where your code is run. So, you are in a spot of I kinda know what’s going on but I have no way to reproduce it because:

- the application has hardcoded paths.

- the service discovery isn’t dynamic

- the branching strategy doesn’t account for edge cases.

- the build process doesn’t account for edge cases.

- and many other things that are related to bad practices.

I recall an old boss saying he wanted stable dev environments which sounded an oximoron. I’ve always aimed to have an environment where I can reproduce a desired behavior wether is a faulty or not.

Use a throwaway disk or device, get rid of that and leave the official one alone.

I discourage this behavior but there could be many cases when this could be useful.

Whoever decided to put the data in a different cloud provider needs a raise and all the praise.

Which is included in the as is part of the license.

A ton of projects have stopped working which forced to fork or replace completely due maintainers not caring anymore, getting sick or just switching priorities. Why is this different. For all the licenses change cases, contributors who disagreed forked and stablished a new route. This is 100% the spirit of the license.

There you go: https://elpais.com/america-futura/2023-09-03/la-fuerza-del-c...

Pretty much Chaccu. Free festival. It's usually in June. You can make a trip of it going to Paracas, Ica's dunes, Nazca Lines and finish in Pampas Galeras. Keep in mind in Galeras there's nothing. Just a post of the National reserve and that's it. It's also at 4K meters of altitude so walking for hours could be a whole experience.

I've seen people who use testcontainers and run their CI workloads in containers abusing the docker.sock mounting so they can spin up the tests. The anti-pattern of using docker.sock has been always a threat because when docker got popularity in CI/CD systems it was the easiest way to have a platform independent way to spin up isolated environments. In my perception, this was a very common pattern in Jenkins a few years ago.

Another one, when you upgrade your cluster and there's an API that is candidate for removal, helm doesn't have a way to update the Kind reference in their metadata which causes the inability to delete and update the release.

I personally like cuelang's philosophy but it could become a little messy when you have to iterate and handle user inputs in large codebases.

Stephane is a great guy. I never met him but we had several discussions in the LXC mailing list before the LXD project became a thing. His knowledge helped me to enter to the linux container world and made a career of it.

If you are in k8s, I freaking love FluxCD for this reason. It points where your sources are.

I’ve been preaching the same. I don’t care where I connect to as long as I have the information. It reminds me a lot to pidgin. As long as there’s a good incentive between the content servers and the UI’s, this could work.

I hope Apollo is talking to several reddit competitors with a sustainable business model and working on integrations. At the end of the month, when they get shut down, they just rebrand the app with the new backend and everyone is happy. All users migrated to a new platform with new communities.

At the beginning, just for the development experience I would just put an instance in some cloud provider and use microk8s or k3s to serve the app. It's very straightforward and then you can move to a managed service if needed. You will probably be using the same tooling and integrations at different steps. Context switching is low and you can reproduce locally. I'm down for serverless options when needed but I have a strong preference for local development.