markstos @ markstos @lemmy.world

Posts

11

Comments

426

Joined

2 yr. ago

Downside: it requires knowing a new coding language, Nix, to maintain your laptop.

If you don’t understand it, it’s going to be painful to fix anything that doesn’t work.

I have had more problems with two different Frameworks than most Thinkpads. Battery died, boot/power problems on both the 13 and 16, touchpad problem on the 13.

I prefer the concept of the Frameworks but can’t say they have worked better in practice.

Also, all spam messages.

It might be related to earlier attacks on Codeberg because of their open support of diversity, equity and inclusion.

I’m sure Tesla shareholders are happy to hear he’s picked up another side project.

One obstacle all third parties face in the US is party-line voting, which favors the dominant parties.

On possible outcome is that he puts a lot of money into making third party candidates more viable, like efforts to ban party-line voting or supporting ranked choice voting. So, you could vote for the America Party candidate and then if they don’t have a majority ñ, you vote could roll over to the Dem or GOP candidate of your choice, reducing your risk of voting third party.

These changes would help Libertarian, Green and other parties as well. More choice for voters!

I host routing for customers across the US, so yes I need it all. There are ways to solve the problem with less memory but the point is that some problems really do require a huge amount of memory because of data scale and performance requirements.

Nope. Some algorithms are fastest when a whole data set is held into memory. You could design it to page data in from disk as needed, but it would be slower.

OpenTripPlanner as an example will hold the entire road network of the US in memory for example for fast driving directions, and it uses the amount of RAM in that ballpark.

As long you give them a good life before you murder them and eat them, that changes everything.

The same way that pigs are food and dogs are not. Cognitive dissonance.

Thanks for sharing.

It does look like there’s a way to use PiHole personally for those who share the network with those who don’t want it: leave default DNS server setttings alone except for your own devices.

And if you aren’t home or available?

Does PiHole ever break a family member’s browsing, and then they don’t know to fix the issue because it would involve understanding opening up the PiHole web interface?

When I see this I think of the week I worked flat on my back with sciatica. It was literally a pain my neck as I turned my head sideways to look a laptop on the side on the floor.

So I see a guy with bad sciatica, but a more comfortable work setup.

Hunter S. Thompson.

Unsend! Unsend!

Snorting tea, coffee and broccoli would be less popular too.

Years ago there was a voice to text transcription service sold as automated that worked by people listening to your voicemails and typing them out.

It’s grow lamps simulating full sun brightness in a windowless room.

This is interesting, I would be quite impressed if this PR got merged without additional changes.

We'll see. Whether it gets merged in any form, it's still a big win for me because I finally was able to get some changes implemented that I had been wanting for a couple years.

are you able to read and and have a decent understanding of the output code?

Yes. I know other coding languages and CSS. Sometimes Claude generated code that was correct but I thought it was awkward or poor, so I had it revise. For example, I wanted to handle a boolean case and it added three booleans and a function for that. I said no, you can use a single boolean for all that. Another time it duplicated a bunch of code for the single and multi-monitor cases and I had it consolidate it.

In one case, It got stuck debugging and I was able to help isolate where the error was through testing. Once I suggested where to look harder, it was able to find a subtle issue that I couldn't spot myself. The labels were appearing far too small at one point, but I couldn't see that Claude had changed any code that should affect the label size. It turned out two data structures hadn't been merged correctly, so that default values weren't getting overridden correctly. It was the sort of issue I could see a human dev introducing on the first pass.

do you know why it is uncommented?

Yes, that's the fix for supporting floating windows. The author reported that previously there was a problem with the z-index of the labels on these windows, so that's apparently why it was implemented but commented out. But it seems due to other changes, that problem no longer exists. I was able to test that labels on floating windows now work correctly.

Through the process, I also became more familiar with Rust tooling and Rust itself.