argiopetech
Now, if the random crashing were fixed, that would make a real difference for me...
Most of my like-new rules came from antique malls, though I've also purchased one from Etsy. Estate sales are occasionally fruitful. As long as they were stored properly (e.g., in a desk drawer, like it seems they mostly were after the electronic calculator took over), they don't degrade. Occasionally you see minor yellowing that is cured by some time in the sun. Carrying cases (often leather) are typically more affected by time. I soak new (to me) leather cases in neatsfoot oil and give them at least a week before putting the rule back.
You could make your own with prints from the Slide Rule Museum [0]. 3D printing would make quick work of it, but I'm sure wood or metal units could be accomplished. The cursor benefits from spring loading,
They also have some pretty nice simulators [1], if that's your thing.
[0] https://sliderulemuseum.com/SR_Scales.shtml [1] https://www.sliderulemuseum.com/VirtualSR.shtml
If the widths don't add to 1, there are two possible behaviors (configurable). Either the newly focused pane adheres to the size of the screen (e.g., scroll right from the full screen editor and the half-screen browser is on the right border with half the editor visible), or the newly focused pane centers on the screen. I prefer the first behavior, but I make significant use of the "center pane" keybinding.
The Video Demo section in the README gives a pretty good demonstration of this behavior in the first 10-15 seconds.
Edit: To add to this thought and address some comments elsewhere about losing windows, I use "struts", which show P pixels of the panes to the left and right (when they exist) of the current view as a visual aid/reminder of where I am in the ribbon. These reduce the size of the tiled section of the screen and the calculation of pane size accordingly.
Quote:
We're using xwayland-satellite rather than Xwayland directly because X11 is very cursed. xwayland-satellite takes on the bulk of the work dealing with the X11 peculiarities from us, giving niri normal Wayland windows to manage.
xwayland-satellite works well with most applications: Steam, games, Discord, even more exotic things like Ardour with wine Windows VST plugins. However, X11 apps that want to position windows or bars at specific screen coordinates won't behave correctly and will need a nested compositor to run. See sections below for how to do that.
Noting the release notes, it does have many animations already enabled (but I have some or all of them disabled through config).
I'm not recommending anyone run this in favor of newer versions, but it's working for me.
If you have (having had "Editor" focused, and just opened "TermT"):
Editor | (TermT) | Term | Browser
(FM) | Term | Browser | etc.
The answer (for me) is to think of desktops as topics. The terminal on /tmp is with the things that prompted its creation. If I needed to check some log output, for example, it's with the project that made that log output.
Edit: Note that there's nothing keeping you from stacking those terms if you like, i.e., the appropriate keybinding goes from the previous to
Editor | (TermT), Term | Browser
(FM) | Term | Browser | etc.
Vastly preferable to having to look at the edge of the screen.
Things on other desktops are invisible in every WM.
The only difference with niri is the possibility for things to be left or right of the current window. Overview helps with that, but I know what I expect to be on a specific desktop (it's related to the topic) and seldom need it.
This was on my Bonobo WS (PopOS) w/ 2x NVidia GTX 1080s, multiple screens (2 1080p, 1 4k at 2x scaling), etc. No issues other than app support.
Highly recommend trying it. Very low barrier to entry.
Being able to have an unlimited number of windows on a desktop (without continually switching the tiling structure) makes them collections of topics rather than having multiple desktops bounded by what fits comfortably. What used to be a switch from the "editor and terminals" desktop to the "browser" desktop is now horizontal movement on the current desktop to the related browser window (general browsing is on a different desktop).
Really low barrier to entry, works great out of the box. There were some wayland teething issues (application support, e.g., no Zoom), but nothing that couldn't be overcome (occasionally by falling back to X). Most of those have been resolved with time.
As for why we have government: the alternatives are unstable and devolve into government, or are weak easily brought to the submission of other states (those powers having a natural incentive in land, people [historically: slaves], and other natural resources to invade weak or disorganized neighbors).
Re. your other points, if we can have those discussions we're likely not in the grips of tyranny. Tyranny has a way of making you accept the potholes and the fact you don't have water 5/7 days (beats dying in a labor camp, and you probably don't have fuel for your car anyway).
Since you asked, though: Paving and water/sewage are not inherently tyrannical. Acquiring the right of way may be. Schools are not inherently tyrannical, but may be used subversively to produce a populace willing to be governed under tyranny. Protecting territorial waters it not inherently tyrannical, but military might can certainly be used in a tyrannical manner. Inspection of food and funding of science and medicine are not inherently tyrannical, but the taxation required for that funding may be, as could be e.g., requiring the use of the output of that funded medicinal research.
In summary, I'm saying that every government must be watched carefully by its citizens lest it devolve into tyranny. By assuming this trend (demonstrated time and again through history) to be indicative of future risk, I am prepared for that eventuality. By continued vigilance, I implicitly fight for the opposite. By continued discourse, I demand the same of my peers (and they of me, mitigating my own tyrannical traits).
Personally, I wouldn't trade my government (imperfect though it may be) for a 50% nominal tax rate and sub-arctic climate. That said, it's no surprise to me that the Kingdom of Norway, a parliamentary monarchy with 4% the land area and less than half the population density vs. USA, populated by 80% ethnic Norwegians, would have a very different form of and perspective on government than the third largest country (by land mass), de-facto world hegemon, a federated republic populated by 360 million children of colonists and immigrants. Horses for courses.
The founders of the USA believed the counter to tyranny was to keep government weak, so that when even the slightest hint of restriction on life, liberty, or property crept in it could be stomped out by the people. The Founding Fathers too were fallible and built a form of government which could not long guarantee those desirable characteristics. I argue the USA is a bad actor in many regards, and I trust it not. That said, it's the best of a bad lot, IMO.
Barring mistakes, it balances if we had avoided reducing the planet's vegetation by 20% since 1900. So much for that.
That's obviously not "the" solution, but it seems like reducing fuel burn while increasing forestation would benefit us beyond what is commonly expected.
For example, could we burn oil at 2024's rates with 1900's forests and not have net-positive CO2 levels? Back of the napkin:
- We're producing ~37 gigatons of CO2 (GtCO2) through burning of fossil fuels at the moment [0]
- The current forestation level is ~4 billion hectares [1]
- The net loss of forestation is ~1 billion hectares since 1900, with deforestation rates peaking starting ~100 years ago. [1]
- 1 petagram == 1 Gt
- Current forests consume 157 Gt/yr [article]
Therefore, the billion hectares we cut down in the past century would consume an additional 157 * 0.25 == 39.25 GtCO2/yr if it were still standing, 2 Gt more than our historical maximum global net output.
Obviously, the burning of fossil fuels is ultimate source of the increase in CO2, but without the deforestation it would still (back of the napkin) be sustainable. At least, we'd not be quite so far down this road.
[0] https://www.statista.com/statistics/276629/global-co2-emissi...
This doesn't strike me as odd at all. It's an identifier, not a string. The quoting of the import, on the other hand...
Wind isn't blowing the right direction? Easier to motor than tack. Sailing upwind? Easier to motor than have the guests stumbling into walls due to heel. Variable winds? No wind? Have to be at <place> by <time>? Easier to motor.
Typed holes (but not the defer- option) have been enabled by default for some time now. They're an immediate go-to when scratching my head over types. I prefer them to the type error output, not only because they give better suggestions, but also because they can be named (_a, _conversionFunction, etc).