This is exactly why I'm considering using atuin also. My zsh history on my mac will sometimes just completely disappear and then I have to go lookup what I was trying to do again. It is driving me crazy.
They can, with enough money. The problem is that these will need to be sold at an even steeper discount so that throwing enough money at the renovation makes sense. That means whoever currently holds the loan will eat a huge loss, whether there is a conversion to residential or not.
What was i told... the market is always a gamble? Or should we once again bail out smart "investors" on the backs of hard workering Americans tax dollars?
Unity has lost $455 million dollars in the first 6 months of the fiscal year 2023. They lost $919 million in 2022. I don't think they have ever made a profit. Companies are not charities; they exist to make money, and Unity doesn't by a mile.
Everything I'm seeing is that it is Chrome doing this, not Chromium. If the Googs decides to add features on top of Chromium in its Chrome release, that does not mean that other Chromium based browsers will have those changes automatically as well. It totally makes sense to me that Googs would not want these in the base Chromium as it's the secret sauce just for the Googs
I would think Google would want this in Brave and Edge also. Google will want to advertise to the users of these browsers even though they aren't using Chrome.
I worked these out a while ago. I think on some sites, an iframe will still show, but will be empty. My second rule and this one probably do the same thing.
It's more of an abbreviation than a truncation: the link still points to the full URL, but outside of a code context there's not much reason to display excessively long URLs in their entirety as part of a regular comment.
I am an Emacs enjoyer. My biggest issue with Emacs is that development is still done via a mailing list and patches. I wish they would adopt a Git front-end (web UI) workflow.
There's probably also a lot of emacs contributors that use emacs as their mail client that would be disrupted by replacing it with something web based.
The "next generation" of Emacs contributors will be Emacs users and will not have any issues using email for collaboration.
Git was made for email. Needing a separate service for it is mostly cruft, when you have mailing lists. Yes, github has mass appeal, but a lot of software has been written with just email collaboration.
As for attracting low-quality contributions, I don't think they matter. People who use Emacs and depend on it will contribute. Interest in Emacs has increased and so have the available features.
This! I'm happy that Emacs isn't the greatest editor or the most-used/-popular; it needn't compete with say VSCode or vim.
There's a decent, loyal user base, importantly not the free-loading, entitled kind who water it down; they're like-minded, appreciate the philosophy behind it, don't mind tinkering with some LISP here and there, contribute their creations as answers or packages, and above all form a nice community helping each other.
As lazy as it seems, I’ve made a couple contributions to Neovim whereas I probably wouldn’t have bothered if I first had to figure out a mailing list flow.
Personally, I think that it's the copyright assignment that's the biggest barrier. For someone who figured out how to use Emacs, it shouldn't be very hard to figure out how to use a mailing list too.
This. A mailing-list-driven workflow is not as difficult as it appears, and Magit makes everything a breeze. However, I cannot complete the copyright assignment process, and consequently I am unable to contribute to the Emacs proper beyond a few lines of trivial changes.
It is so discouraging that I stopped working on the Emacs core [1] altogether: your contributions won't be acknowledged at all, even if someone volunteers to rewrite your code from scratch.
[1] I've been hacking some GUI-related features, but I'm not motivated enough to complete them. I also tried to write patches for my bug reports, but alas, my "CA-free" quota is already used up.
This is absolutely true and is one of the stronger arguments for the Linux kernel to adopt something like GitLab as well. Being able to take PRs for smaller contributions while still keeping core development on mailing lists (probably with an email bridge between so things aren't missed) seems ideal to me, but that's extra work for maintainers and whatnot
> There's probably also a lot of emacs contributors that use emacs as their mail client that would be disrupted by replacing it with something web based.
The further I get into "emacs for everything" the more I appreciate using email for everything.
As an occasional developer of PostgreSQL which also does development on the mailing list I see pros and cons with it. It is harder to discuss lines of codes in a review on the mailing list but the nature of the mailing list (threading, etc) promotes much more nuanced and constructive discussions about patches on a higher level. Something which I have yet to see in any project on Github.
Gitlab has some threading support but not very good one.
The third-party apps shutting down on July 1st will be the real test. If Reddit notices a significant drop in traffic on that day, they will probably start walking back the change. I agree that this boycott, while the intention is good, won't do much.
Unless a large number of people who don't use 3rd party apps also leave in solidarity, it won't be a "significant drop". 3rd party apps make up quite a small amount of total traffic. And that's also assuming that TPA users _leave_ and don't just switch.
If you have 10,000 users you have 1000 commenters, 100 people posting, and 10 moderators. If you keep 97% of your users but you lost half your mods, 25% of your posters and 7% of your commenters its going to lead to an eventual decline bigger than 3% and it can create a self re-enforcing trend because the people contributing to other networks can drag their connections along with them.
I don't think Reddit is doing anything based on that day's data. I suspect that they will wait for a month before starting to rely on the data for any long-term prospects.
Thanks for this, this changes everything. Namely, I can re-enable most commands that I've globally disabled. Who woulda thought the path to enlightenment would be to simply RTFM.
