Nate Cox

Damn fine callout here, it definitely looks like the AMS there is loaded up with the green, orange, and pla support

This just in: intentionally misrepresenting something has a 100% chance of it being misrepresented.

Let’s try again:

• proper tools are important, but not as important as the people using them
• documentation is important, but not as important as the software functioning correctly
• working with the customer to accomplish their needs is more important than adhering to the letter of a contract
• plans are important, but dogmatically applying them above the spirit of their intent is harmful

Ugh I wanted one of these so fucking badly when I was a kid.

The SEO on this name is going to be a major irritation for adoption.

But that aside, doesn’t it strike you as a concerning that this project is born at least in part from the complaints about a “benevolent dictator”, and the very first time—at least that I’ve seen—someone asks you to put something up for community consensus you say no?

That’s some god damn nostalgia for me right there. I think I may need to get mine out and get infuriated with some Pitfall again.

This is the way

Rails is great for starting an app, you can get something to a functional MVP state in a ridiculously small amount of time. We used to do rapid prototyping where we could be shipping it to the client in like 2-4 weeks. I haven’t found anything that comes close to this elsewhere.

But you’re right that the big trade off is jumping off is effectively impossible, because Rails is your app. Most criticism that I see (and feel is valid) is that unless you’re willing to do a whole rewrite you will be on Rails forever. I think this is a more reasonable trade off than I see represented online; “long terms Rails is a nightmare” comes up a lot and I don’t think it’s that bad.

I personally like that we’re seeing options for both strategies here popping up. More options is good for us as devs.

Really taking that saturday morning cartoon super villain act to a new level.

I would argue that the signal to noise ratio here makes this metric effectively worthless. Being unpopular doesn’t necessarily indicate bad faith, and downvotes come for many reasons that are not similar enough to group.

Downvotes also bring a unique kind of bad actor: the troll. I have many times seen accounts that go out of their way to farm for downvotes, and that kind of content brings everyone down with it.

I know it’s an unpopular opinion, but I feel strongly that downvoting itself is a problem.

Social media is powered by little bits of endorphins that come from clicking the response buttons, and a certain type of person seems to get a thrill out of the downvote in particular. That personality type does not seem to be conducive to building a strong community, but we give them quite a bit of engagement anyways to keep them coming back.

I don’t think anything of value would be lost by dropping that action all together.

Paddle or joystick?

I don’t understand the complaint here. It sounds like the complaint is that there is a single source for libraries… but the solution provided is “use apt-get”.

Today, I refuse to use any language that doesn’t ship with a dependency resolver like crates or rubygems. Python taught me that I really want dependencies to be a first class citizen.

I pay for Kagi because it does not have any form of advertising or “sponsored results”, and it consistently gives me the best results of any other browser I’ve tried.

Apple supporting this would not be hard, as with all the other search engines the search is just a query parameter appended to the url, they could just provide a template string for “unsupported” search engines.

Probably explains why I’m not allowed to just make Kagi my default search engine on iOS and Mac.

Honestly the great failing of nix is that the new user experience is utterly terrible. I personally bounced off nix several times before I finally just grit my teeth and embraced the suck.

I think the best you can really do is look at the community. The nix project does have documentation but it is indecipherable, and I say this as someone who mostly likes nix and uses it daily.

https://zero-to-nix.com is a pretty good resource. I think they’re trying a bit hard to “framework” nix that maybe isn’t my preference, but the getting started guide is the best I’ve found so far.

Also, use your search engine of choice to find articles on nix, home-manager, nix-darwin (if you’re using a Mac), and find repos out there of other people’s dotfiles. Then get used to confusion and frustration for a while.

I still think that it has been worth it for me, personally… but there is real pain in the learning.

A software error that was quickly fixed, and that Bambu was transparent about and took accountability for, isn’t exactly “exerting control”.

Nobody is compelling you to like BambuLabs, but the hyperbolic argument here just seems silly.

You can print offline from an SD card, online is only required if you want to start prints from the slicer or monitor the print via the phone app.

I cancelled my mk4 order after a long wait that didn’t seem likely to end soon and got a P1S instead.

I was upgrading from a MK3S that I’d had for a couple of years, and I was all in on Prusa.

After using the P1S for a while now, it’s clear to me that Prusa sat on its hands for too long. The P1S is fantastic, involves virtually no setup, and gives me out-of-the-box prints better than my MK3S ever gave me even after months of fine tuning. I can’t imagine a world where Bambu doesn’t significantly erode Prusa’s market share.

Core-XY is the way to go, and I think to really compete Prusa is going to have to finally retire the i3 bed-slinger design and step into the future.

I want to support Prusa in principle, but they’re going to have to really step it up to get me away from my Bambu.

MUDding taught me programming and Regex in a very real and useful way.

It also contributed to a gaming addiction that took years to break, so food for thought I guess.

EM perspective: your 1:1 meetings are your time to ask questions, express concerns, advocate for yourself (e.g., for career advancement or project placement), and generally have a line to what is happening with the org and upper management.

They aren’t a place for me to micromanage my reports, they’re how I figure out to to best serve the people I lead, especially when my responsibilities keep me out of the day to day work.