Public

664 bookmarks
Custom sorting
How I cut GTA Online loading times by 70%
How I cut GTA Online loading times by 70%

That thing where you obviously release something that works, just doesn't work well enough, and you never go back and improve it 'cos it works and, well... it's working yeah?

That.

·nee.lv·
How I cut GTA Online loading times by 70%
Advice to Regretful pwBPD
Advice to Regretful pwBPD
Quote: "The number-one complaint among loved ones isn’t manipulation, splitting, mood swings, rage, jealousy, devaluation, triangulation, the victim Olympics, or really any of the well-known drama/trauma/abuse. It’s the pervasive lack of accountability."
·reddit.com·
Advice to Regretful pwBPD
Reactive abuse
Reactive abuse
Interesting explanation of the idea of "reactive abuse", where an abuser keeps abusing someone until they get to the point that they react and then the reaction is called abuse.
·breakthesilencedv.org·
Reactive abuse
Deleting Git Branches with Magit
Deleting Git Branches with Magit
As this article says, I've always tended to drop down to the CLI to delete a branch, and ensure it's cleaned from the remote, etc. Somehow I'd never picked up on the fact that Magit just handles this. And of course, it does, Magit does so much!
·emacsredux.com·
Deleting Git Branches with Magit
The Insensitive Ruins It All: Compositional and Compilational Influences of Social Sensitivity on Collective Intelligence in Groups
The Insensitive Ruins It All: Compositional and Compilational Influences of Social Sensitivity on Collective Intelligence in Groups
A group's collective intelligence reflects its capacity to perform well across a variety of cognitive tasks and it transcends the individual intelligence of its members. Previous research shows that group members' social sensitivity is a potential antecedent of collective intelligence, yet it is still unclear whether individual or group-level indices are responsible for the positive association between social sensitivity and collective intelligence. In a comprehensive manner, we test the extent to which both compositional (lowest and highest individual score) and compilational aspects (emergent group level) of social sensitivity are associated with collective intelligence. This study has implications for research that explores groups as information processors, and for group design as it indicates how a group should be composed with respect to social sensitivity if the group is to reach high levels of collective intelligence. Our empirical results indicate that collectively intelligent groups are those in which the least socially sensitive group member has a rather high score on social sensitivity. Differently stated, (socially sensitive) group members cannot compensate for the lack of social sensitivity of the other group members.
·frontiersin.org·
The Insensitive Ruins It All: Compositional and Compilational Influences of Social Sensitivity on Collective Intelligence in Groups
Problems | Project Lovelace
Problems | Project Lovelace
A pretty neat list of programming problems, that are intented to be solved in a number of languages and the solutions tested. Good for people getting to grips with a new language, or with programming in general.
·projectlovelace.net·
Problems | Project Lovelace
On Basecamp (AKA Cringe-camp)
On Basecamp (AKA Cringe-camp)
A rather well-done critical review of DHH's explanation of the anti-staff policy changes at Basecamp.
·breen.tech·
On Basecamp (AKA Cringe-camp)
Evolution of Emacs Lisp | Proceedings of the ACM on Programming Languages
Evolution of Emacs Lisp | Proceedings of the ACM on Programming Languages

While Emacs proponents largely agree that it is the world’s greatest text editor, it is almost as much a Lisp machine disguised as an editor. Indeed, one of its chief appeals is that it is programmable via its own programming language. Emacs Lisp is a Lisp in the classic tradition. In this article, we present the history of this language over its more than 30 years of evolution. Its core has remained remarkably stable since its inception in 1985, in large part to preserve compatibility with the many third-party packages providing a multitude of extensions. Still, Emacs Lisp has evolved and continues to do so.

Important aspects of Emacs Lisp have been shaped by concrete requirements of the editor it supports as well as implementation constraints. These requirements led to the choice of a Lisp dialect as Emacs’s language in the first place, specifically its simplicity and dynamic nature: Loading additional Emacs packages or changing the ones in place occurs frequently, and having to restart the editor in order to re-compile or re-link the code would be unacceptable. Fulfilling this requirement in a more static language would have been difficult at best.

One of Lisp’s chief characteristics is its malleability through its uniform syntax and the use of macros. This has allowed the language to evolve much more rapidly and substantively than the evolution of its core would suggest, by letting Emacs packages provide new surface syntax alongside new functions. In particular, Emacs Lisp can be customized to look much like Common Lisp, and additional packages provide multiple-dispatch object systems, legible regular expressions, programmable pattern-matching constructs, generalized variables, and more. Still, the core has also evolved, albeit slowly. Most notably, it acquired support for lexical scoping.

The timeline of Emacs Lisp development is closely tied to the projects and people who have shaped it over the years: We document Emacs Lisp history through its predecessors, Mocklisp and MacLisp, its early development up to the “Emacs schism” and the fork of Lucid Emacs, the development of XEmacs, and the subsequent rennaissance of Emacs development.

·dl.acm.org·
Evolution of Emacs Lisp | Proceedings of the ACM on Programming Languages
The Apperta Data Breach Fiasco
The Apperta Data Breach Fiasco

If you found a leak of data from the NHS and let them know, you'd think they'd be properly happy about being told, right?

About that...

·secjuice.com·
The Apperta Data Breach Fiasco