uhoh-itsmaciek

The vibe is not the same, but Jonah is likeable, Felicia Day and Patton Oswalt are good as the Mads, and the movie selection is fantastic: Reptilicus? Munchie? The Christmas Dragon? Every film is a magnificent slice of different B-movie territory.

I know why it apologizes, but the fact that it does is offensive. It feels like mockery. Humans apologize because (ideally) they learned that their actions have caused suffering to others, and they feel bad about that and want to avoid causing the same suffering in the future. This simulacrum of an apology is just pattern matching. It feels manipulative.

Be sure to read the disclaimer.

>The curse from the tower of Babel has been lifted.

It wasn't a curse. It was basically divine punishment for hubris. Maybe the reference is a bit on the nose.

The main downside to many mobile web sites is the desperate plea to use the app you have to dismiss every time. I feel sorry for the devs who build a great mobile version only to be forced to put a stupid "$SITE is better in the app" banner on it.

>Long-press on the dash on mobile (in Google keyboard at list) gives you two em-dash options.

One is an em-dash (—); the other is an en-dash (–). See, e.g., https://www.merriam-webster.com/grammar/em-dash-en-dash-how-... for an overview.

I don't believe you want to have a productive conversation about this. It sounds like you just want to be angry.

It does. It bridges a purely server-rendered architecture with a SPA really nicely, and does it mostly with web standards. You don't need to run any client-side JS with a Remix app. It's not perfect, but there are a lot of benefits to its approach.

I won't try to argue there's no front-end treadmill: there absolutely is, and I had to laugh reading the current top comment because I just had to migrate off Apollo CLI at work.

But this "The web was perfect in 1999--stop changing things!" take is tedious and intellectually lazy. (I'm not accusing you of it, but it's certainly a common sentiment.)

We should be working together to solve concrete problems, and avoid both chasing the latest fads and pretending there's no room for improvement.

Maybe as freeze-dried backpacking food? But I expect it's not economical compared to existing options that seem much easier to prepare in bulk.

PSA: "pierogi" is already plural.

    def with_synchronous_commit_off(&block)
      ActiveRecord::Base.connection.exec_query("SET synchronous_commit = off")
      yield
    ensure
      ActiveRecord::Base.connection.exec_query("SET synchronous_commit = on")
    end

I'm not a Rails expert: does this reliably give you the same connection from the pool? If not, you could be setting `synchronous_commit = off` on one "physical" connection, and clearing it on another. This is setting it at the Postgres session level, so it will persist for the lifetime of the connection. If it's not managed reliably, it could lead to some very confusing bugs (only triggered in a very small window when Postgres shuts down unexpectedly while the transaction is still unsynced to durable storage, making it extra fun to debug).

In general, though, this is a very handy feature.

Not sure about a GUI way of doing this, but in the CLI, I use `git log --patch [path]` all the time. It will show you the history of diffs for that one file.

Or thermal receipt tape with a stripe of color near the end.

The thing is, scaling font size does not necessarily mean you want to scale other aspects of the UI. Josh Comeau touches on that in this post: https://www.joshwcomeau.com/css/surprising-truth-about-pixel...

Yeah, +1. I started as a backend dev and for a long time, I knew just enough CSS to be dangerous. After taking that course, I feel pretty confident. Josh is quite good at balancing aesthetics, standards, and pragmatism. He explains the mechanics of CSS in a way that facilitates developing understanding and intuition, giving you an ability to reason about solving design challenges instead of just trying things and crossing your fingers.

>It involves removing a patient's tooth, usually the canine, installing a plastic optical lens inside it, and then implanting the whole thing into the eye.

How fitting that the material usually comes from eyeteeth!

It's just a nice, playful touch.

And no answers, huh? I'm stuck on 38.

Edit: it doesn't mention that `anchor()` can accept an anchor name, which is kind of important for this.

Neat. The museum framing is cute, and well executed with the footsteps sound between levels.

On level 20, if I set `position-try-fallbacks: flip-inline;` and drag the anchor to the top, something weird happens: the label stays on top, but is also mirrored below the anchor, except with no text or background, just a border and a translucent frame. Latest Chrome (on Ubuntu, but I don't think that matters here). Is this a Chrome bug? A bug in Anchoreum? In dev tools, it looks like it's an Anchoreum issue, because there's a separate element in the DOM.

Edit: also happens on level 25 without changing anything if I drag the anchor to the left.

Edit 2: ah, I think that area is where you're _supposed to_ place the anchor. It's not very clear from the text.

Backups don't matter. Restores matter.

There's plenty of dystopian sci-fi out there with all sorts of ideas about that.

I'm also planning to leave. It's offensive that they decided to do podcasts and audiobooks and not allow you to turn that off in the UI. I want an app to listen to music! But someone there apparently thinks they can engage me more if they throw in a bunch of other irrelevant functionality. Ugh.

https://nebula.tv/ is a nice YouTube alternative for that kind of stuff (disclaimer: I'm mostly a subscriber for the music content, so my perception may be skewed).

Did he consider an absence of criticism to be praise of his management technique?

I can't speak for the original commenter, but for me, it serves to remind me that I'm working with some very talented engineers, which feels good. Plus I think it helps to build trust, which is useful when you're not seeing eye-to-eye on some technical or product issues.

Nice analysis. The point about titles is interesting: given how content spreads on the Internet, it's really an invitation to potential readers. If you take that too far, it can devolve into tacky link-bait, but it's worth thinking about how to summarize your post into a handful of compelling words.

Google Drive uses it as an interaction pattern. I find that baffling, but while uncommon, it's not totally absent. And as others have pointed out, many users carry over their expectation of having to double-click from desktop interfaces.

Lake Geneva is the English name commonly used to refer to Lac Léman. I suspect you know that, but I don't follow why you object to that name.

I've started using Navidrome with Symfonium a few months ago. Navidrome is pretty good, but I'm very impressed with Symfonium. It's simple, responsive, and straightforward, but it's got a ton of options so you can fine-tune the client quite a bit.

Pretty sure. Tastes vary, but you're arguing that runaway commercial success is a prerequisite for artistic success?

Not to mention that those superstars need to come from somewhere. If a career in music is basically like spending all your money on lottery tickets, society ends up poorer: many hard-working young musicians are going to see it for the exploitation machine that it is, and go sell advertising instead.

But the system is set up so that, more and more, they're competing for scraps. Shouldn't we incentivize making good art, rather than just becoming a superstar?