The Deal-Breaker
vim.pack has no event/filetype/command-based lazy loading. None. You either load at startup or you manually call :packadd in your config yourself.
Oh, so it’s sane and doesn’t try to bullshit it’s way out of plugin authors’ incompetence?
I’m sold!
The two are not mutually exclusive.
Sexual attractiveness also doesn’t mean sexual drive. One doesn’t need to be gay to understand that a man is sexually attractive in the way they find compelling. A desire to look good is all it takes.
For the company, the problem is already solved.
IIRC the goal wasn’t to have a loyal workforce, but to have an army that isn’t dependent on a small number of elites.
Basically “we won’t stop with the death of our officers, our soldiers can step up to the occasion”.
«гр.» is for grams
Senior backend engineering definitely doesn’t see 99% windows adoption rate.
Well, they do it Japanese style - by forcing developers to leave due to burnout.
I’m working with a legacy codebase for the last few months, where a simple PR often ends up crossing a 1000 lines count due to testing and commenting, and I can’t stop apologizing for those.
Yet there are people out there bragging about 10x changesets.
Kids the days… are entirely relatable.
I made my statement as a BDD/TDD practitioner.
The code goal of software engineering is not to deliver said code, but to deliver it in a framework that lets others—and consequently me in a week’s time—to contribute easily. This makes both future improvements and bug fixes easier.
Dumping a ~25000 lines changeset with a git history that’s almost designed to confuse is antithetical to both engineering and open source.
The size of that changeset means that it’s inherently unreviewable.
The commit history is something I’ve seen only in the PRs that even the most dysfunctional companies would demand a rewrite for.
Also, 2-3 weeks review? PostgreSQL support could be added in that time without the need for a damn „vibe check”. Hell, it would probably take less time than that.
Any feature relying on a willing cooperation of every node in the network is impossible to enforce.
Sure, it should be attempted, but don’t expect it to actually matter against actors that just don’t give a fuck.
But how could you possibly know anything about things you and your family personally suffered through? Silly little barbarian…
we age due to our telemere buffer shortening
Telomere shortening is a marker and there is a correlation, but aging is a process that happens on multiple levels and many of those aren’t fixable by DNA restoration.
We experience wear and tear, we accumulate damage, we accumulate waste, we lose body parts, we constantly fuse our bones together, we have body parts that grow surrounded by tissues capable of maintaining them but then operate outside of them, the list goes on.
But most importantly, death is such a beneficial feature, that it outcompeted everything else. Producing new generation of individuals regularly is a simple and terrifyingly effective solution to a vast array of problems. Many aspects of aging can be seen as adaptations to inevitability of procreation and death.
That aside, I like pointing people at professor Michael Levin’s work. Be very skeptical, as it’s a small field in a world that goes through reproducibility crisis, but it does fill me with a cautious hope.
Why the fuck is the very first sentence not a link to the goddamn proposal being discussed? Are they trying to look sketchy to anyone with a habit of informational hygiene?
https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A52025PC0101 - this one matches the date and the general topic. Dunno if it’s exactly the one.
https://en.wikipedia.org/wiki/Sergei_Magnitsky
His death was the moment when Russian state dropped any pretense of being civilized.
It’s also roughly the time when Russia has pivoted from “let’s trade” narrative towards “don’t encroach on our turf” threats. Prior to that there was at least an effort to put on makeup on the Europe facing ass cheek.
You spelled November 16, 2009 wrong.
Well, IIRC it’s not indirectly. Sam Altman negotiated pre-purchase of massive chunk of wafer supply, which OpenAI backs up with its virtual money.
So DRAM manufacturers are facing a wafer shortage in near future. Which translates into prices now.
Using single vim.pack.add() call to load all necessary plugins at once and later configure in a series of require() calls
How about not using require for configuration at all? Although I wouldn’t expect it from this particular author - he shoves require().setup even into plugins that literally have nothing to configure and should just work.
The whole thing is a remnant of an old misinformed plugin template repository made by someone with no knowledge of vim startup sequence.
It doesn’t, it shifts responsibility at best.