Not a good thing
638 karma · joined June 29, 2016
Not a good thing
EDIT: responding to pre-edit of parent
On hand, it provides real benefits
On the other, hard not to see this most benefits the wealthy. I count myself in that benefit
You joke, but that's what the VIM creator/maintainer said in response to the question of the continued future of VIM
> For something like photopea, there aren’t sub-second alternatives out there.
if there is't one now, there will be. Besides, with a little CDN and tweaking you improve your users enjoyment. Why not?
My response may come off as rude, but that's not the intention. From the above quote you've vastly over simplified all but the most simplistic environments. Someone could run all of the above for well under 10k month - those are not the reasons why costs are high
> putting 500kb of JS in every web page they serve
that's not much and CDNs serve that without issue or significant cost
> putting Docker everywhere when a chroot would suffice
Docker does not have much overhead over chroot with a large drop in security/isolation
> microservices
there are good and bad ways to do this - does not need to cost much. saying "microservices" is so broad to have no meaning in this context
> Kubernetes
think about why someone might run kube. Again, not that expensive unless you're really small where having master nodes would have a big impact on costs
> or hell even writing SAPs when we don't need them?
Do you mean SAP? SAP is the largest non-American software company by revenue. I don't think anyone likes working with SAP. You think people use it for without reason? There are reasons. Think about what those might be
But those are just details - when building anything of a decent size, nothing is a simple CRUD. There are always exceptions, limitation, biz logic, migration issues, schema issues. I don't care if you use Postgres, Mongo, Kafka or $SOMETHING_COOL
Then there's data retention. It's very very easy to keep PB of data in s3 or other data stores for biz or compliance needs
Then AWS gives IAM, which is very helpful in teams > 5
Also, I'd create a IAM user and severely limit your usage of the root account, and over time stop using the root completely.
Besides, just use AUTHY if that's your concern
1. BW supports inline Android 11 password fill. I find the UX much better with this feature
2. LP is a bit buggy, particularly on Android
3. LP is slow to add new features
4. I didn't expect this, but I really enjoyed BW's UI
5. On Android, I enjoy the three quick launch buttons they provide
6. LP creates new logins in folders of it's choosing by default. Not a fan
But in general, BW it just "works" better/faster for me
Just about everything in a NixOS is configured in a declarative way, but that only really scratches the surface. It's the first Linux OS I've used that configuration is done at a wholistic level
Say for example you have a RHEL/Debian Linux server and you want to see how it’s configured. This sounds easy, but can be quite time consuming. You can see what packages are installed but then you’d need to examine all the /etc files. Try and see which ones are modified. Look at all services, look for further configuration that may exist in /opt or /usr. When you get to a certain scale tools like Chef, Puppet or Salt tend to help with managing configuration. Over time to meet compliance and monitoring requirements configuration can grow. And that’s not getting into any filesystem permissions you may set.
If you're using `yum install` or `apt-get` to install packages out of the system repos, you'll get the latest package in that repo. Run that command at different times, you can get a different package version
In NixOS the system and packages are versioned together; makes for very reproducible systems. The downside/upside (depending on your needs) is, updating your kernel will update your packages in lockstep
With NixOS, you can configure a complete system with a single file making Chef, Puppet or Salt obsolete. Once you get over that first hurdle of using NixOS and moving your workloads to it, it tends to be easier to maintain
The major downside I run into is that most of the world does not use Nix[OS]. So if you need something not provided by Nix[OS], you’ll need to learn how to make your own package (derivation)
There are many caveats to everything I said above, but its the general idea
Personal bias talking, but I'd expect to see modest uptick in Nix[os] interest
Kubernetes will transition from new and exciting to a mature platform. Expect less new big features and more minor improvements
I had no idea and kinda funny
50 years is quite the time horizon after all
For better or worse, it's what I and my team used to manage a decent size VMware cluster of a hundred hosts and 6k VMs ( I think, it was a very long time ago)
Wouldn't go back, but there are aspects I miss
If not running Java (including agents), it may indicate some other type of compromise. Not something you should really ignore. Look at logs, cpu, disk, port usage just to start
It was pretty funny actually
> you have to reconfigure basic keybinds like the arrow keys "because it could break a system not used since the 1970s!"
Never had to do that on Nixos, Ubuntu, Amazon Linux, RHEL, MacOS or WSL
For my workflow with lots of context switching between code and commands, using only a terminal is more efficient use of my time. VSCode cannot do that in a way that works for me
But ignoring all of that, many use [neo]vim because they simply enjoy it. Enjoyment does not need justification
Who in their right mind would conflate the two
I just deal with iso cert, so not clear on possible requirements
It's funny, I was just about to move to kernel 5.10 for amz Linux 2. Might just wait a bit for AL2022