LGUG2Z

joined 1 year ago
MODERATOR OF
 

This (Windows employing different methods to prevent users from writing programs that programmatically change application focus) has been an ongoing struggle for me for the better part of 3 years.

I finally made what feels like some significant progress this past week.

If you've ever obsessively gone deep down into a hole trying to understand and wrangle weird OS-level behaviors before, you might enjoy this video and feel a vicarious sense of victory :)

 

I got laid off this month and have a lot of time on my hands while I'm looking for new jobs ๐Ÿ˜…

I tried making a LinkTree but the website UI for editing is so janky and frustrating, and on top of that you have to go Premium for advanced theming, again in the janky UI...

I found this great Hugo theme called Lynx and built out my own links webpage like we did back in 90s on Geocities with Dreamweaver

Some folks on Mastodon and Twitter messaged me asking for a walkthrough because there are a few rough edges that are mostly related to changes between Hugo versions and the docs on the theme, so I made this end-to-end video going from project init to deployment on Cloudflare pages with analytics enabled

It's a pretty fun project and I think it can also be useful as a "portfolio links" page for people that are looking for jobs right now

 

cross-posted from: https://lemmy.world/post/8269080

Someone on another website asked me whether it makes sense to use agenix or sops-nix to encrypt secrets for NixOS configurations.

I realized that I hadn't seen a good overview article of the different approaches to secret handling in NixOS and when each one is appropriate to use, so I put down all of my knowledge and opinions in this post ๐Ÿคž

 

Someone on another website asked me whether it makes sense to use agenix or sops-nix to encrypt secrets for NixOS configurations.

I realized that I hadn't seen a good overview article of the different approaches to secret handling in NixOS and when each one is appropriate to use, so I put down all of my knowledge and opinions in this post ๐Ÿคž

 

It currently requires some extra steps to get Nitter up and running on NixOS as I found out yesterday. I documented the process for anyone else who might be looking to run their own Nitter instance between now and the trunk branch of Nitter being functional again.

 

Found some time this past weekend to work on a little "passion feature" that I've been wanting to implement for a while now; sharing the technical write-up for anyone else who is interested in automating headless screenshots with these tools or with others (the knowledge is pretty transferable!)

 

These days I reach for chumsky pretty much any time I need to write a DSL parser.

I thought it would be an interesting exercise to take a DSL parser that I've written using chumsky and reimplement it the "old fashioned" way.

[โ€“] LGUG2Z 3 points 1 year ago* (last edited 1 year ago)

We all use Linux on our workstations and laptops. That might make it easier.

You are living my dream!

I think this is the key piece; the experience of Docker on Linux (including WSL if it's not hooking into Docker Desktop on Windows) and on macOS is just so wildly difference when it comes to performance, reliability and stability.

[โ€“] LGUG2Z 1 points 1 year ago

Thanks for sharing this! Added to my weekend inspiration/reading pile. ๐Ÿ™

[โ€“] LGUG2Z 4 points 1 year ago (1 children)

Highly recommended viewing if you'd like to learn more about the limits of reproducibility in the Docker ecosystem.

[โ€“] LGUG2Z 3 points 1 year ago

Tutorial != advocation. As I said, no attempt to engage in good faith.

[โ€“] LGUG2Z 5 points 1 year ago (3 children)

I understood your point, and while there are situations where it can be optional, in a context and scale of hundreds of developers, who mostly don't have any real docker knowledge, and who work almost exclusively on macOS, let alone enough to set up and maintain alternatives to Docker Desktop, the only practical option becomes to pay the licensing fees to enable the path of least resistance.

[โ€“] LGUG2Z 5 points 1 year ago (3 children)

Lot's of (incorrect) assumptions here and generally a very poorly worded post that doesn't make any attempt to engage in good faith. These are the reasons for what I believe is my very first down-vote of a comment on Lemmy.

[โ€“] LGUG2Z 5 points 1 year ago (2 children)

NixOS on WSL2 is actually my development environment of choice these days! (With my tiling window manager komorebi, of course! ๐Ÿ˜€)

[โ€“] LGUG2Z 6 points 1 year ago (5 children)

I believe this is the Docker Desktop license pricing.

On an individual scale and even some smaller startup scales, things are a little bit different (you qualify for the free tier, everyone you work with is able to debug off-the-beaten-path Docker errors, knowledge about fixes is quick and easy to disseminate, etc.), but the context of this article and the thread on Mastodon that spawned it was a "unicorn" company with an engineering org comprised of hundreds of developers.

[โ€“] LGUG2Z 15 points 1 year ago (27 children)

Hi!

First I'd like to clarify that I'm not "anti-container/Docker". ๐Ÿ˜…

There is a lot of discussion on this article (with my comments!) going on over at Tildes. I don't wanna copy-paste everything from there, but I'll share the first main response I gave to someone who had very similar feedback to kick-start some discussion on those points here as well:

Some high level points on the "why":

  • Reproducibility: Docker builds are not reproducible, and especially in a company with more than a handful of developers, it's nice not to have to worry about a docker build command in the on-boarding docs failing inexplicably (from the POV of the regular joe developer) from one day to the next

  • Cost: Docker licenses for most companies now cost $9/user/month (minimum of 5 seats required) - this is very steep for something that doesn't guarantee reproducibility and has poor performance to boot (see below)

  • Performance: Docker performance on macOS (and Windows), especially storage mount performance remains poor; this is even more acutely felt when working with languages like Node where the dependencies are file-count heavy. Sure, you could just issue everyone Linux laptops, but these days hiring is hard enough without shooting yourself in the foot by not providing a recent MBP to new devs by default

I think it's also worth drawing a line between containers as a local development tool and containers as a deployment artifact, as the above points don't really apply to the latter.

[โ€“] LGUG2Z 2 points 1 year ago

I initially tried it when I first switched to Windows, but as I mentioned in another comment, it lacks the ability to automatically (re)arrange the windows on the screen in response to events like new windows opening, windows minimizing or being closed, etc.

[โ€“] LGUG2Z 2 points 1 year ago* (last edited 1 year ago) (1 children)

The biggest difference vs. the built-in snapping is that when you move one window, all of the other windows move in relation to that window based on the layout algorithm you choose, and when you add a new window to the workspace, all of the other windows rearrange in relation to that new window, etc.

In this way, it's very similar to Linux tiling window managers like bspwm and i3, which allow you to arrange your desktop on-the-fly using only keyboard shortcuts.

[โ€“] LGUG2Z 1 points 1 year ago (5 children)

If you've ever seen some of the cool window managers on communities like [email protected], you should know that you can achieve a similar workflow on Windows too!

view more: โ€น prev next โ€บ