Good riddance to bad spamware

Wonder how many things they shit up

I was surprised to find that an old Plex feature, controlling any one player from any other instance, such as playing on a laptop and controlling with a cell phone, no longer worked. My wife and I used that a lot when traveling, as plugging a laptop into a hotel TV with an HDMI cable is generally far more bullet proof than any streaming stick

Course sometimes we’d stay in an Airbnb, and they’d have a Roku or Apple TV, where we’d just sign into a Plex app and use it there. But that’s beyond the point

MacOS has had caffeinate forever, and it works great

Did they perhaps confuse Tesla solar installs with the cars?

I wish more people would hold Sam Altman’s feet to the fire, hold him to some semblance of accountability. Because the man has made an entire career of failing upwards, from launching a short lived startup that imploded, to suddenly becoming president of ycombinator, to suddenly being worth billions of dollars, and literally paying people in the third world (with monopoly money, of course) for their eyeballs

Oh and there’s the whole thing where he might have molested his kid sister, which is always seemingly glossed over

Even Ed Zitron, who isn’t afraid to go after someone (see his articles about the guy who destroyed Google search) seems to handle Sam with kid gloves

I think they’re talking about self moderation. Maybe augmented “mod services” that you could subscribe to and pick and choose from, as well as override in the “yes I actually want to see this” sense

I still reach for sass for a lot of things, but now you don’t have to, which is really nice

But now who will donate pretend coats for the virtually needy?!

You’re a moron if you use this.

Not only that, but with toolchains like deno, it’s almost enjoyable

I wrote some telegram bots in deno and it’s got one of the cleanest deploy chains around, just compile to an executable for the target architecture, and SCP it over. Exec is statically linked, and so it just works

Recently I had to do an update to the underlying environment a codebase ran on. This was a somewhat involved upgrade and took a longer period of time than most of our work usually does. I did it in a separate worktree, so I didn’t have to constantly rejuggle the installed dependencies in the project, and could work on two features relatively concurrently

It also provides some utility for comparing the two versions. Nothing you couldn’t do other ways, but still useful

And in elixir/erlang we’re spoiled with loads of options, from ETS to mnesia

During my most recent job search, the most annoying thing I saw was “resume consultants”

They’d reach out like an interested recruiter, but very quickly get to the sales pitch

Apple has done this many times before. Over even more frivolous patents (i.e. a glossy black rectangle)

They made their bed, now they have to lie in it

Seriously. I had a friend extolling how good his experience with his chiropractor was, in response to my tale about physical therapy after a skiing accident. I ended the argument pretty quickly by asking “how often do you have to go back”

I’ve only ever worked in one codebase that didn’t need feature flags, and even then we could have used them.

Graphite is ok, but honestly it’s a solution in search of a problem

Maybe if you have a massive pr, splitting it up like this works, but that’s really a planning failure. Stories should be smaller, and if you need to keep them separate for a long time, use feature branches

No. You’d use something like rev.2020 or some other wide gamut color space. Jxr already supports this, and some programs, like the Xbox, take hdr screenshots as jxr

They can both model any color equally well, it’s just oklch works even closer to how we perceive colors changing. LAB and all derivatives are in Cartesian space, with luminance, a, and b being the defining axises. Luminance is self explanatory, but a and b are just axises of how much red/green and blue/yellow there is. It can be difficult to think of a color in how much blue it is, for example, when the color is something like nearly pure red. They both affect the hue output, so varying one can create strange, unintuitive colors

LCH works in polar space, like a color wheel. L is still luminance, c is the “colorfulness” and h is the hue. H and C let you set the same values a and b would, but in a more human way. We’re used to thinking about colors changing independent of how much of a color there is, and that’s what LCH does. Vary only the h and you get very different colors. Vary only the c and you get the same color but in different amounts of saturation, from full color to no color

True, however it occupies the same niche an ORM occupies, without the foot guns. Updating a slew of different db tables from rather clean and straightforward models is relatively simple. It tries to live somewhere between just doing everything as SQL and abstracting everything away like AR does, giving you conveniences from both approaches. You don’t get mired in scoping hell, but you don’t have big ugly messes of nearly-identical SQL statements either.

i’d recommend trying it out https://hexdocs.pm/ecto/Ecto.html