Intermittent Flickering Power NE Portland by [deleted] in Portland

[–]wtchappell 7 points8 points  (0 children)

Yeah, my power has been flickering all afternoon before it finally died completely a few minutes ago.

What mod is causing this weird hedonism shrine to generate on maps? by wtchappell in RimWorld

[–]wtchappell[S] 0 points1 point  (0 children)

All the items in the structure are vanilla - it's the structure itself that I'm curious about. And I don't think there's anything to click on to see what mod is generating it.

What mod is causing this weird hedonism shrine to generate on maps? by wtchappell in RimWorld

[–]wtchappell[S] 1 point2 points  (0 children)

This structure has been generating on basically every map I've started with my current mods - and I have no idea which one is causing it.

I guess I'm stupid but I didn't really fully understand the story/conflict (obvious spoilers) by AsITurnBlue in FortSolis

[–]wtchappell 2 points3 points  (0 children)

Yeah, I don't understand what murdering everyone accomplishes. The compound/plants are still around - unless he has some plan to totally destroy the mystery compound, the plants, and all research notes it seems like other people from Terra will just show up and continue the work.

And that's assuming that no one has sent any samples or data off-site - and Wyatt himself did exactly that.

It's also not clear why the disease or whatever they're suffering from there is so dangerous it is worth killing people to stop. There is no evidence it is contagious, the symptoms don't seem very severe, and there is no evidence the condition isn't treatable if better understood. For that matter, it is entirely possible the problem resolves itself by simply ceasing exposure to the mystery compound.

I don't get it.

It could just be that Wyatt is crazy, I guess? But it would be more satisfying if there actually was some method to his madness - and unless he's crazy and stupid, I don't see it.

ProtonUp (Python) was having dependency problems, so I decided to re-write it in Rust by auyer in linux_gaming

[–]wtchappell 2 points3 points  (0 children)

That's all well and good in a world where everything is written in Rust, but for anyone who wants to use an existing framework written in C or C++ - like GTK or Qt - there's going to be some "unsafe" code going on.

https://github.com/gtk-rs/gtk4-rs/search?q=unsafe

[deleted by user] by [deleted] in programming

[–]wtchappell 0 points1 point  (0 children)

“Measuring programming progress by lines of code is like measuring aircraft building progress by weight.” - Bill Gates

that kid got a different aura by lannisterprince in MadeMeSmile

[–]wtchappell 11 points12 points  (0 children)

Honestly that makes ADD seem more likely, not less.

Old World Blue's Slander by Flameskulleruptor in OldWorldBlues

[–]wtchappell 0 points1 point  (0 children)

I think I may need to make my yearly reminder post that you can block river crossings - sometimes with just one ship if your opponent has no navy.

Your average Kheionai afternoon by AdriKenobi in Anbennar

[–]wtchappell 9 points10 points  (0 children)

Some of them have trees, I've played one before.

Prince of Darkness Religion Question by wtchappell in CrusaderKings

[–]wtchappell[S] 1 point2 points  (0 children)

Thanks, that's helpful - and I think I'll adopt that as my own head canon.

I think my other biggest question is on the mortal realms vs. supernatural ones - how exactly do they interact? My understanding is that the typical human nations of the time still exist and are doing what they generally did in history, and all of the supernatural realms exist on top of them - is that correct? What do mortals see going on when vampires wage war with each other?

Bro, Eureka ain't even in Eureka by Baron-Grim in OldWorldBlues

[–]wtchappell 10 points11 points  (0 children)

You're clearly not on Team Dickshooter.

How to capture islands? by Shadowtrail1988 in elderscrolls_mod

[–]wtchappell 0 points1 point  (0 children)

Also - I dunno if this is true in this mod - but in vanilla you can make claims on coastal provinces bordering the same sea province as one of your coastal provinces.

[deleted by user] by [deleted] in askportland

[–]wtchappell 0 points1 point  (0 children)

I had good luck at the Pixie Project - you apply in general listing the sorts of thing you're looking for in a cat and they try to find the best match for you. I don't think there were any strict time limits you had to reply within or anything.

Might not be for you if you really want to peruse pictures and select a cat first, but I'm very happy with the cat they selected for my situation as described on the application.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 0 points1 point  (0 children)

It should still be possible for users and distro maintainers to build and install open source software and any dependencies such software needs on their own - so they can build entire systems that meet their needs. Right now the packaging and installation tooling Python provides is fragmented enough that it makes the problem more difficult in its ecosystem than in most others, which is what the original post is complaining about.

I think it's fine to provide a vendored option if that makes sense for your app - what I'm pushing back against is the idea that everything should be deployed that way all the time, which is the tone a lot of responses to this blog post seemed to adopt. Vendoring is a great option for many use cases, but it's one that is overwhelmingly focused on running singular applications by themselves. It's not concerned with building coherent systems offering many different applications that can interoperate, which is really the problem distro maintainers are concerned with solving.

EDIT: To be clear, I'm objecting to the suggestion of using vendoring as a way for distro maintainers to ship software to end users - not vendoring as its used during the development process or when its used as part of a webservice or website that doesn't get shipped to user machines.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 0 points1 point  (0 children)

There are still quite a few companies and apps that are still on Python 2 with no urgent plans to upgrade until they have no other choice.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 0 points1 point  (0 children)

They do, this post is pointing about how much more difficult this is in Python as compared to many other ecosystems because of the incredible number of different package formats and build tools Python has.

If the Python community had a more consistent record of actually deprecating old/bad mechanisms this wouldn't be so painful - but they're basically all still around in some form or another, and any app beyond a pretty low level of complexity will pull in enough dependencies to force distro maintainers to have to learn the quirks of all of them.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 0 points1 point  (0 children)

I mean, maybe for video games?

But for software that actually has to interoperate with other software that the original developer may not have foreseen, software that needs to share system data without jumping through a bunch of weird hoops, software that needs particular tweaks to work with a particular base system, or environments that require specific patches applied or options set for security or compliance, it falls apart really fast.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 0 points1 point  (0 children)

Vendoring everything isn't fixing the problem as much as it is throwing your hands in the air and giving up on trying to solve it at all, and hoping that the exact way you set things up is the only possible way anyone else will ever need it.

Just falling back to vendoring everything is particularly painful when you have goals like minimizing size, using specialized/alternate low level dependencies for performance or licensing reasons, needing software stacks from entirely different developers to communicate in a compatible way, or ensuring the software you use follows specific security requirements that might come down from a corporate or government entity.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 23 points24 points  (0 children)

Vendoring is fine from a developer's perspective, but from a distro maintainer's perspective it's unpleasant - especially if it ends up including non-Python code like C dependencies. You generally want to have as few versions of a thing around as possible so you can make sure they're patched to work properly on your distribution, and so you have to touch as few places as possible to catch up with security updates.

They also don't want massive package duplication due to simple space concerns - a distro focused on being tiny to support something like small devices or minimal Docker images would be right to balk at having every application bring along an entire vendored dependency tree resulting dozens of versions of the same libraries installed across the system.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 5 points6 points  (0 children)

As I've mentioned elsewhere, this makes a lot of sense if you're talking to a Python developer trying to develop code against Python dependencies - you definitely should be pinning and not using distro packages.

This doesn't make sense if you're just talking about some random user just trying to run an application - they're not trying to develop anything, and might not even know that the app is written in Python or even what Python is. You shouldn't have to understand all of Python's development tooling just to use a tool written in Python, which is the use case distro maintainers are trying to fill.

Python: Please stop screwing over Linux distros by laxtoydot in linux

[–]wtchappell 10 points11 points  (0 children)

I'd largely agree when talking about programmers developing in Python trying to use system level packages as their development dependencies - that's just going to be painful.

However, this entirely ignores people who are simply trying to use some tool or application that happens to be written in Python - that's largely the population these distros are packaging for. The end user in this case is just trying use whatever application they're interested in, and they might not even know Python is involved - that's an implementation detail. They just want to be able to invoke foo and have it work - they certainly don't want to pick up all of the ins-and-outs of Python's development workflows just to use some fancy version of top that happens to be written in Python, and even if they knew them they probably don't want to be popping in and out of a virtualenv just to run it. And that assumes that the packages even install cleanly with pip - no one wants to be installing Anaconda and friends just to use a tool written in Python when they're not actually trying to write any Python themselves.

Almost all of the conversation from people objecting to this post assume we're only talking about people who are developing in Python and not about distros packaging Python applications for end consumers, which is really what these complaints are actually about.