davidee

Some films to try if you like films:

- Adaptation

- The Unbearable Weight of Massive Talent

- Dream Scenario

Either way it's a communist conspiracy to sap and impurify all of our precious bodily fluids.

If you're serious - I made the jump to nvim a while ago - I highly recommend using vim keybindings in vscode to get used to them/learn them, without having to worry about setting up a viable vim configuration/learn everything at once.

Can Claude 5.5 also play it?

Meat proxies; proxying the transfer of wealth for the benefit of the few at great cost to the many.

It depends on what you mean by “good alternative”.

We use a self-hosted OSS LanguageTool server that's containerized and runs in a private, on-prem cluster to provide good performance and be HA, but it only works on our corporate network or when using a VPN connection while roaming/remote.

It's incredibly reliable.

It's also devoid of AI/LLM bullshit for writing. Spelling and grammar rules, a few notes about long sentences, that's it.

However, LanguageTool nerfs their other plugins (like mail plugins) to require a subscription service.

I've pleaded with them for years to please allow me to pay a subscription price but use our internal server simply because we don't want/need a spelling/grammar tool to send content to the cloud.

We don't want free. We want private.

The odd thing is that the official LanguageTool browser plugins DO allow use of a self-hosted LanguageTool server; clearly it's doable. There's a poorly maintained obsidian plugin that also works(ish). But that's about it.

We live with these limitations.

There are no certificates to share with Wireguard. Nothing to rotate if you don't want to. Once it works, it works.

I've even got a backup wireguard server running on a Pi 1b. Works fine. We currently run wireguard on our router (and it seems more and more routers are supporting it).

There are keys to configure for each client, but once you have the configuration for one client, the rest come very quickly and easily.

I should add that I don't have any experience with Tailscale, but compared to OpenVPN and other VPN solutions, Wireguard is lightweight, simple, and easy to setup/configure.

We use it on all our mobile devices (phones, laptops, tablets) to tunnel our traffic through our home network with all the filtering it offers (along side access to private services we host).

Alt text: Buzz Lighter sees functional programming paradigms everywhere.

PS - I don't follow JavaScript or use it much, but these are nice tools to have in any language.

I've never seen an incident report or postmortem that didn't include action items to cover the core issue noted in this writing: "can we / how do we prevent this failure mode from recurring?"

I'm not saying these moments of discovery / epiphany aren't valuable, they are and this retelling is enjoyably written.

I am saying that action items borne of incidents should be de rigueur.

I recently had to implement a stripe payment system for a client (having never used it before) and found their documentation to be accurate and excellent (at least for the Java SDK and relatively basic use case).

No love for Stripe but IMO their documentation feels like a first-class product.

It's not just iOS. Final Cut Pro on MacOS now regularly advertises iPadOS Final Cut Pro (which is a paid SaaS tool). Professional applications (arguments about Final Cut Pro X not being all that professional notwithstanding) that advertise like that are almost non-existent in the pro audio and video industry; an Apple pro app advertising, would have been heresy a few years ago.

And yeah, it drives me crazy. It's one more, wildly unnecessary, click.

Logic is one of the last tools keeping me tethered to MacOS. I've got 26 years invested in it, but the moment I open it up to record something and see an ad, it's over. Ardour and Bitwig will suffice, even if it means flushing tens of thousands of dollars of software down the toilet with it (the core suite of plugins I use).

I'm tired of unnecessary speed bumps in the creative process. It's why I no longer use a Roli Seaboard (what wildly awful software).

Apple continues down a course (addicted to ads, even their own) that I've seen few recover from.

There are already consequences.

We (collectively) were unprepared for a machine that presents itself in human forms. We were the frogs that boiled ourselves. We built a world of images and words on a screen. And then we built a machine that can (increasingly) mirror that world; it does so in a way which most of us are incapable of disambiguating.

It feels like there is indeed a ghost in the machine.

And there is, but that ghost is us. And that ghost is fading surprisingly quickly.

I’ve found the downgrade surprisingly minimal on plasma 6 - and it’s far more customizable.

Thanks to marginal gains on MacOs (nee OS X) the Linux desktop gets closer more quickly than Apple can pull away.

Tech has always been breaking social contracts. It’s how we roll. We did the same thing with taxis and travel accommodations to name a few.

We hid our “we know better” hubris under the term “disruption” because the reality (breaking everything) was a little too unsettling for us.

We ignore laws and regulations where we know better of course. Don’t you love having a homey place to stay while travelling that has just a few weird rules, a small to-do list and stays spotless thanks to that cleaning fee?

And look at all the good we did! A whole new world of slaves (oops gig workers - sorry!)

And of course we’re doing it again with information and content. We should be in charge of monetizing all your work because you’re not responsible enough to do it right. It furthers our need for power and control. Oops we meant to help make the world a better place (We keep doing that, sorry.)

Please take this in good faith, as I hope your own post is, but I interpret the thread you're replying to as focusing on the "everyday' part.

Share knowledge? I don't think anyone here is arguing against that in any way (or conversely arguing for hoarding knowledge).

The concern, one I share, is where the sharing has to happen publicly "every day" - so no matter how trivial, useless, niche, overly-specific the tip is (whatever, the list isn't exclusive), someone shares it.

That's the part that's not sharing knowledge for the benefit of others, but rather self-serving. I might even go so far as to say self-serving doesn't even need to be selfish; the person might genuinely believe they're doing good, but even there, self-serving.

TLDR: Share your knowledge, don't make sharing something every day, even when you don't have something valuable to share, your target.

PS - if this note irks anyone (are routine maxxers a thing?), make the goal to learn something every day, then share where appropriate.

This made me chuckle.

Aside: Scala dev here - but I only talk about how wonderful it is with people I trust (mostly Go and Rust developers I used to work with).

Also, Scala Native means I don’t always have to worry about the JVM depending on the use case.

ScalaJS is fun too.

I realise this is a joke, but I have to pile on.

Even weather was/is comically bad. Ask it anything specific and it would fall over, repeating the broadest, least helpful version of weather data, even if all that data is clearly available in the ios weather app. Specifics on wind, precipitation hourly, etc.

So no, you can't really ask a homepod for the weather either - Homepod's weather was more like a shitty version of sticking your head outside and looking up at the sky.

Wouldn't most users considering or using Forgejo also have considered (or used) self-hosted Gitlab which would have the same opex / security costs (and much higher hardware requirements)?

Finder is indeed frustrating. "Recent" seems like an attempt to fix this without the need to use some giant camera roll?

The (hard) problem is that almost every finder alternative/add-on I've tried is someone else's ideal workflow that still doesn't sit well with me. I find KDE's Dolphin similarly frustrating - for very similar reasons.

Both work marginally better (for me) when used in concert with the quick-find tools like Alfred (or Spotlight) and KRunner. None of these are perfect.

Showerthought: maybe the "find files" interfaces aren't the worst offenders; maybe it's the "place files" workflows that are problematic and we're trying to solve the wrong problem?

High quality 500-600w bifacial n panels are between $200-300 in Canada at normal install sizes (12-32). We do lag behind the costs elsewhere, but still nowhere close to $1000 per panel.

If you're building out, say 12kw of PV, that's about 24 panels for a modern install (500w bifacial n panels).

So a $336 premium, or roughly 1.3 additional panels in terms of cost.

While sure, that's not nothing, it's ~$6700 vs ~$7050, or a ~5% premium to the pre-tax cost of the panels.

Citation required.

One monitor for nvim/zellij, one for browser & devtools.

My __third__ monitor is for YouTube, thankyouverymuch.

This should be front page material if it hasn’t been already.

On top of it being thorough and illustrative, it’s surprisingly engaging.

Also: I had no idea.

To further back this up, just because OSM might be a map's data source, it doesn't mean they use the same rendered vectors or images for the tiles.

I make changes to OSM so they can be propagated to a cycling-specific mapping tool I use (it's a commercial tool with their own custom map layers) - it takes about 3-4 weeks from when a change is made on OSM for it to be incorporated into their data set.

So yeah, it's not as simple as "we all use OSM so we'll just share all our rendered mapping values".

Completely agree with you.

That said, Car Play isn't a panacea for keeping me off my phone though, because some manufacturers have the ability to LIMIT what Car Play can show you.

Example - we have two vehicles for our 3 person household.

One is a 7 year old Kia EV, the other a nearly new Ford.

Ford has somehow limited apps like Music and Podcasts to show or give access to only a tiny subset of playlists and songs when the car is moving - exactly when you absolutely shouldn't pick up your phone.

So you pick up your phone because that thing that works in one car, doesn't work in the other - and it's the newer car and car play implementation that's more limiting.

You mean the person who wrote the author request the change right?

Right?

PS - it's knickers

I didn't read it that way (but I can see multiple possible readings).

Here's my interpretation: When someone has a shitty public opionion, we force others to MAKE PUBLIC their opinions.

And because our society is so polarized, we don't talk about opinions or their nuances; we reduce them to binary views (it's possible they are but not always), we pick a side and we light our torches.

Good faith question: would it?

Wouldn't most large codebases with poor abstractions just have engineers engineer around them with their own solutions? In a large enough codebase you'd have both the bad abstractions and all the not-quite-duplicate implementations ignoring the bad abstraction?

I'm using bad here loosely, it could be buggy, incorrect, incomplete, insufficient and more; while being owned by someone or some team that's a challenge to work with for various reasons (overloaded, under-resourced, overbearing, etc., etc.).

Missing the splitting axe getting a little jammed at a knot.

Otherwise excellent.

I had trouble getting through this one, but I think it's worth digging in a bit.

> In just a few short years, Slack has gone on to become an indispensable work tool in our always-on often mobile work life.

For you maybe? For many companies maybe? It feels a lot like the "we have no choice here" when the reality is "this is the easy path". Surprise, the easy path has huge costs!

But I'd argue that what's happened here, in most cases (and whether they believe it or not) companies have relinquished control over their distributed/remote/online/collaborative culture to Slack's definition of "what works". In my opinion Slack's vision of the future is broken because it's not truly designed to help you or your team succeed. It's designed to keep you on Slack as much as possible.

This relates in no small way to the question about corp SWE being performative that was on the front page when I puked up this comment. https://news.ycombinator.com/item?id=48475871)

If you can't tell that I loathe Slack and all its ilk, let me be clear, absolutely I do. It's a terrible way for *most* teams to work. Without a huge (and I do mean huge) about of effort to enforce and reinforce specific behaviours, Slack will push your new hires (who are less connected to the company culture than insert smaller team who came before here) to bend to Slack, and stop trying to bend Slack to the needs of the company.

This gets worse as employees now exist in a place where they can move from company to company and Slack (along with their personal Slack baggage) moves with them. A stint at four tech-companies of significant size and Slack was there, helping destroy whatever positive culture existed before.

It's not Slack's fault per se; this article illustrates one of the pillars that makes Slack at scale hard to live with: it's a noise machine. It slowly increases the noise floor until you're the frog, the water's boiling, and you're dead.

I've had folks attempt to argue about this, but they're often (not always) already boiled and don't realize it. "It just sorta happened."

Slack's perspective: "relax and just let it happen, it'll feel great."

PS - One of my interview loops from a fairly well known OSS company involved an inane question about how one might develop a product to use Slack to improve employee connection in a remote work environment. I should have read it for the very real warning that it was. But I, too, am all too happy to fool myself into believing "this time will be different".