That's precisely the point of using tabs for indentation: you don't need to fight over it, because it's a local display preference that does not affect the source code at all, so everyone can just configure whatever they prefer locally without affecting other people.
The idea of "skins" is apparently to push that even further by abstracting the concrete syntax.
I don't see why? Your window width will presumably be tailored to accommodate common scenarios in your preferred tab width.
More than that, in the general case for common C like languages things should almost never be nested more than a few levels deep. That's usually a sign of poorly designed and difficult to maintain code.
Lisps are a notable exception here, but due to limitations (arguably poor design) with how the most common editors handle lines that contain a mix of tabs and spaces you're pretty much forced to use only spaces when writing in that family of languages. If anything that language family serves as case in point - code written with an indentation width that isn't to one's preference becomes much more tedious to adapt due to alternating levels of alignment and indentation all being encoded as spaces (ie loss of information which automated tools could otherwise use).
I find it tends to be a structural thing, Tabs for indenting are fine, hell I prefer tabs for indenting. But use tabs for spacing and columnar layout and the format tends to break on tab width changes. Honestly not a huge deal but as such I tend to avoid tabs for layout work.
I love the idea of "tabs for indents, spaces for alignment", but I don't even bring it up anymore because it (the combination of the two) sets so many people off. I also like the idea of elastic tabs, but that requires editor buy-in.
All that being said, I've very much a "as long as everyone working on the code does it the same, I'll be fine" sort of person. We use spaces for everything, with defined indent levels, where I am, and it works just fine.
I completely agree, hence my point about Lisps. In terms of the abstraction a tab communicates a layer of indentation, with blocks at different indentation levels being explicitly decoupled in terms of alignment.
Unfortunately the discussion tends to be somewhat complicated by the occasional (usually automated) code formatting convention that (imo mistakenly) attempts to change the level of indentation in scenarios where you might reasonably want to align an element with the preceding line. For example, IDEs for C like languages that will add an additional tab when splitting function arguments across multiple lines. Fortunately such cases are easily resolved but their mere existence lends itself to objections.
Do you mean that files produced with "wide" tabs might have hard newlines embedded more readily in longer lines? Or that maybe people writing with "narrow" tabs might be comfortable writing 6-deep if/else trees that wrap when somebody with their tabs set to wider opens the same file?
There's a lot of options. If you want to go down the rabbithole try typing `sysctl -a | grep -E "^vm"` and that'll give you a lot of things to google ;)
Probably a safe default as there's extra memory of kernel structures, file buffering, SSH sessions to allow logins to debug why your server suddenly has high load and high IOwait (swapping).
If you know a a system is going to run (e.g.) a Postgres database, then tweaking the vm.* sysctl values is part of the tuning process.
Not sure if I understand your question but nothing "happens to the rest", overcommitting just means processes can allocate memory in excess of RAM + swap. The percentage is arbitrary, could be 50%, 100% or 1000%. Allocating additional memory is not a problem per se, it only becomes a problem when you try to actually write (and subsequently read) more than you have.
Just a guess, but I reckon it doesn't account for things like kernel memory usage, such as caches and buffers. Assigning 100% of physical RAM to applications is probably going to have a Really Bad Outcome.
But the memory being used by the kernel has already been allocated by the kernel. So obviously that RAM isn't available.
I can understand leaving some amount free in case the kernel needs to allocate additional memory in the future, but anything near half seems like a lot!
Neither of your links mention arrests, one specifically says "None of the suspects were detained". They don't seem to back up the original claim about Germany arresting the most people based on social media posts.
That’s an important distinction. Thank you for referring back to the original wording. They were investigated for violating the criminal code, searched, interrogated, and had devices seized in a number of cases, but seemingly not arrested.
> this will never work because governments will never allow for disintermediation of their currency because it’s one of, if not THE, primary sources of control over a population
Isn't this similar to saying "democracy will never work because kings will never allow it"?
I'm not saying it's exactly the same, just the fact that some existing power structures do not like the change does not guarantee they will manage to stop it. Sometimes they do, sometimes they don't.
> The UK arrests 12k people per year for social media posts, using vague laws to undermine free speech.
A spokesperson for Leicestershire police clarified that offences under section 127 and section 1 can include any form of communication and may also be “serious domestic abuse-related crimes”. [1]
It seems misleading to count arrests related to domestic abuse as "anti-free speech".
It seems very politically convenient to be able to hide that one number behind the other. To obfuscate something highly controversial by making it artificially conflated with something everyone would agree on with.
This is what governments do when they want to avoid public scrutiny. This is not the win you are looking for.
It would indeed be better to have the separate counts. It's also wrong to attribute to only one case what is a actually a larger category, unless there is actual evidence that it's the overwhelming majority anyways. Both can be true at the same time.
I'm not trying to win anything, and I do support privacy. I just think any argument, especially those citing specific numbers, should be based on an accurate description of reality.
Generative AI exists, but it is very much dependent on the data it has been trained on. Not saying it would not be interesting, but a huge caveat is required.
The thing is, if it takes say a year to go from a formal spec to a formally proven implementation and then the spec changes because there was a misunderstanding about the requirements, it's a completely broken process. If the same process now takes say a day or even a week instead, that becomes usable as a feedback loop and very much desirable. Sometimes a quantitative improvement leads to a qualitative change.
Do you now use Lean instead of Rocq because your new employer happened to prefer that, or is it superior in your opinion? Which one would you recommend to look at first?
For one, being childless is a choice (mostly, especially since adoption is a possibility). It's indeed OK to have different opinions for what how laws apply differently to people based on their choices. Being gay is not a choice, it is rather similar to race/ethnic background, and it's generally not OK to have laws that treat people differently based on something like that. I'm sure there are more nuances to add, but it seems to me that makes it quite a different situation.
I don't think everyone agrees that being gay is not a choice. There are no outward physical indicators of a person's sexual orientation. It's entirely behavorial and therefore plausibly under the conscious control of the person. Now, I would agree that a person doesn't choose which gender he is attracted to, but it not something than anyone else can see and immediately understand as an inborn characteristic.
Clearly being black, or hispanic, or asian, or white are physical characteristics. Far fewer people would argue that there is any element of choice in that.
The idea of "skins" is apparently to push that even further by abstracting the concrete syntax.