![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://slrpnk.net/pictrs/image/d9a15e34-516b-4f18-a4c7-171aa9dc1e98.webp)
I ended up figuring out im averaging about 120w on my desktop which isn’t bad at all.
A web browser, a code editor and some docker containers or binaries. Nothing incredibly strenuous. Like I’m not gaming.
I ended up figuring out im averaging about 120w on my desktop which isn’t bad at all.
A web browser, a code editor and some docker containers or binaries. Nothing incredibly strenuous. Like I’m not gaming.
Definitely will look into the MacBooks power consumption. The logic checks out for sure. I have to measure my current laptops too.
Thank you! Appreciate it
🌶️🥵Many people consume Facebook meta company’s tech stack wholesale, don’t know how to actually traditionally program their way out of a paper bag, and web dev and devops caused a massive layoff (250k people) at the end of 2022, start of 2023 because it was all vaporware. They consume the same software in droves if the other guy uses it.
There is an entire subculture around it that is just a bunch of medium.com writers, YouTubers and twitter handles just trying to get the clicks for their ad money. Some of these guys have never written valid software or done anything noteworthy. If you meet them head on you’d find they have enormous egos and can’t find a counter argument when presented with reason.
I’ll even add on that there are many programmers who don’t know how to code outside a web app.
Why is something like [react, graphql, react ssr, devops, tailwind, unit tests, containers] vaporware?
You know the stuff I don’t hear about?
Thanks for weighing in. Yeah! This is basically what I am thinking I’ll have to do. I just tried Github actions and runners with a very small internal app and I liked it. I’ve never worked closely in AWS but I’ve gotten trained in/used Azure a few times and it’s basically the same thing on my end.
Robust tests, larger conditional workflows in github actions, and some sort of staggered rollout I think are the conclusion I’m arriving at.
Godspeed. I hope the transition goes well. If you need to baby step towards it, I felt like docker swarm was easier to approach but kubernetes is far more standard. I recommend budgeting training into the rollout if your shop can afford it. For CI/CD I recently had a great experience with github and github actions but I had a coworker setup on-premise gitlab in the past too.
Somewhat of a tangent - My experience with alembic of over four years is that it is leagues better than manual SQL dealings, and also very easy to understand what you’re looking at. But I have to say that when I used sequelize in NodeJS, it has an autosync and autoupgrade schema that made alembic look silly.
In regards to my own post I think for now what I’m mostly seeing is that for each new deployment - is going to have to have an internal smoke test, then staggered rollout of updates.
Reading what you wrote here - I think this is confirming my looming suspicion. Which is that there is no standard today for upgrading docker containers. Since upgrades happen app to app. For example if I have a docker-compose deployment and service A
is lemmy
, and service B
is postgres
the app in this case service A
will have to have its own logic for handling upgrades or code migrations.
In other words, the upgrade process can depend on how the software developer writes the software; independent of docker/k8s/vm’s or whatever deployment strategy you are running.
I think what I was hoping for was that I’d ask if there was a newer smooth standardized way to do software upgrades besides A/B testing or staggered rollouts but I’m not really seeing that.
I’m not super familiar with Lemmy’s codebase but it looks like they’re using diesel ORM here and have migration handling on a case by case basis for some major changes. https://github.com/LemmyNet/lemmy/blob/main/src/code_migrations.rs**___****___****___**
Maybe try some of these - I found this awesome list in my research https://github.com/VPashkov/awesome-nim#gui
Thank you so much for posting. It’s really nice to hear from someone with experience first hand.
I have a lineage phone I keep on dial and I was using graphene OS for a minute but
The thing is that I live by my phone. Passwords, banking, pretty much the entirety of my actual life daily. I think graphene OS is great! But I also don’t have time or a the ability to have an AI review the codebase to validate that what I’m putting on my phone is safe. The truth is that these are unpaid strangers making a great product who’s work Im not a subject matter expert in. Android is a large codebase. I’m friends with a guy who works on it full time and even he feels lost sometimes. So I reversed my phone back to stock Android for my daily driver.
If I’m doing better financially in a few months I’ll likely buy another pixel phone or try fair phone with graphene. I just can’t justify the purchase right now and my phone works fine.
Just a reminder if you like these projects, donate to them!. I dropped about $1000 on open source stuff over the last year to include joplin, EFF, vueJS, graphene, lineage, and quasarJS. Every one of them does great work.
I have to ask how do you like the pine book pro?
I have one of their phones but the software at the time was really under developed so it mostly sat for a few years