There is no os inside the container. That's a big part of the reason containerization is so popular as a replacement for heavier alternatives like full virtualization. I get that it's a bit confusing with base image names like "ubuntu" and "fedora", but that doesn't mean that there is a nested copy of ubuntu/fedora running for every container.
So does the one it's in reply to. But you skipped that one to complain about this one.
It's absurd that anyone could pretend to believe that more people having guns is a "deterrent" mild or otherwise to lethal use of force? In every interview about why american cops shoot and kill orders of magnitude more people than most civilized countries, americans always argue it's because their citizenry is armed so the police need to be prepared to make life or death decisions in a split second at every moment on the job.
Nobody suggested that more guns were a solution to anything.
Guns have been more accessible and readily available for the entire history of the United States. School shootings are a relatively new development.
Access to and availability of guns has been more greatly restricted over that time. With virtually no impact.
Perhaps the desperation and miserable mental health of our population are bigger factors?
Every country you would point to likely has better access to healthcare, education, and much better social safety net than the US. As well as law enforcement and prison systems less focused on restitution/justice and more focused on education and rehabilitation. Other countries also see less recidivism and lower violent crime rates in general.
All available evidence indicates we should be spending much less time and energy focusing on guns and far more focusing on the failures and motivations of our government.
> They are, at best, a mild deterrent against indiscriminate use of lethal force.
Is a quote from a sibiling comment to the one I replied to.
It seems that at the very least an extraordinarily loud minority of americans believe that arming the general population should somehow result in fewer gun deaths. On the big social media platforms, the larger news networks, and right here on HN, I am always surprised that such an obviously incorrect idea can be so pervasive.
> All available evidence indicates we should be spending much less time and energy focusing on guns and far more focusing on the failures and motivations of our government.
No, it doesn't. You can't just assert that because it's what you think. Societal issues do play a part, but just as you need oxygen and fuel for a fire, removing either one stops the flames. So if changing the individual minds and morals of seemingly half your country seems easier than enacting legislation restricting access to guns... well I don't think you should hold your breath.
You're misquoting me. That was in the context of a hostile government, not guns in general for civilian-against-civilian "self-defense".
Also, the "at best" and mild" are quite important there. I believe that armed civilians might prevent someone like the National Guard from firing on groups of protestors when it gets hairy, out of fear of being shot in response. They aren't suicidal: you don't escalate when you are in a disadvantaged position!
Going from the Netherlands to Budapest I started my journey with Deutsche Bahn. My train also did the split in half and go different directions trick. Was I supposed to learn Dutch, German, and Hungarian in order to buy my train tickets?
I said "travelling TO", and most of the time you do not need to know anything apart from the name of the city... and then I presume you have a smartphone as well. Come on.
What did you do once you arrived in Budapest? Did you do your research or did you get scammed by the taxi mafia as well?
If you travel to Budapest from Berlin you buy the ticket from DB and the crew changes as follows: German, Czech, Slovak, Hungarian. None of the first three crews would speak Hungarian. Luckily all will be able to communicate in English.
(regular announcements oftentimes won't be in Hungarian until you are in Hungary, that depends on the train origin, but I would only expect local+English)
You will be perfectly fine staying in Budapest with just English; you can learn hello, please, and thank you to be polite. This goes for most bigger European cities, outside of France I guess.
As a quick and kind of oversimplified example of what zero copy means, imagine you read the following json string from a file/the network/whatever:
json = '{"user":"nugget"}' // from somewhere
A simple way to extract json["user"] to a new variable would be to copy the bytes. In pythony/c pseudo code
let user = allocate_string(6 characters)
for i in range(0, 6)
user[i] = json["user"][i]
// user is now the string "nugget"
instead, a zero copy strategy would be to create a string pointer to the address of json offset by 9, and with a length of 6.
{"user":"nugget"}
^ ]end
The reason this can be tricky in C is that when you call free(json), since user is a pointer to the same string that was json, you have effectively done free(user) as well.
So if you use user after calling free(json), You have written a classic _memory safety_ bug called a "use after free" or UAF. Search around a bit for the insane number of use after free bugs there have been in popular software and the havoc they have wreaked.
In rust, when you create a variable referencing the memory of another (user pointing into json) it keeps track of that (as a "borrow", so that's what the borrow checker does if you have read about that) and won't compile if json is freed while you still have access to user. That's the main memory safety issue involved with zero-copy deserialization techniques.
I'm amazed that so many people here completely miss the point. Clippy being annoying/horrible UX or not has absolutely nothing to do with the validity of the reasoning for it being compared to modern software trends.
The point is that microsoft got _nothing_ regardless if you were using or not using clippy. So clippy being bad could only be because they sucked at making something good for their users. It was not because they chose maliciously to make the user experience bad for an ulterior motive like collecting and selling user data or pumping up telemetry numbers for a promotion. They genuinely thought clippy would be a net benefit to their users in some way even though they were clearly wrong.
The point Louis is trying to highlight is the difference in intent, not in execution so that is why clippy is being used as the moral backdrop to compare modern software against. Saying clippy itself is "user hostile UX" is besides the point, and either shows a lack of comprehension or intentional feigned ignorance so that you can complain about a badly thought out feature you didn't like that hasn't existed for over 20 years.
Automatic updates are pretty unrelated. Google can just release an updated version of google play services or a device verification API and everyone's banking/government ID apps will stop working until you manually update anyway. They have a pretty big stick to whack you over the head with if you don't update to the new version "for security"
It's not entitled to not want to try out some new thing if it has major drawbacks over what you are already successfully using.
If someone randomly comes up to you and offers you an apple with a rotten spot and you say "No thanks, there's a big rotten spot" would you expect them to scold you for being entitled and looking a gift horse in the mouth? _They_ came up to _you_ offering an apple!
Nobody came up to them though, they opened a hn article that wasn’t posted _for them_, decided the product isn’t for them, which is fine, but then decided to post about how it’s not for them. The project maintainer didn’t ask if the project suited gp, nobody did.
Nobody asked anyone anything. It's a post with people sharing thoughts. You don't even know if the maintainer is the same person as the author. As far as feedback goes, if the comment gets enough upvotes it shows a significant number of people share the sentiment, and would be something for the maintainer to consider if he wants a broader audience. Nobody expects the maintainer to respond or care though.
actually, it's more like you are selling clothes, and i don't like the style, and i am telling you which style i'd like to buy.
you don't have to produce my style, and i don't have to buy your clothes, but it's good to talk about our preferences so you have a better idea of the potential market.
If you viewed the source and reproduced a software project you don't have a license to redistribute, that's cut and dry copyright violation. If the code looks similar enough you are toast. That's why there's the concept of a "clean room" reimplementation. The same is true if you feed the source into the context of an LLM and asked it to reproduce it. You have done nothing but introduce the possibility of transcription bugs.
reply