braindevices

#btrfs benchmark for daily used desktop OS

smakosh

import Error from "next/error";
import Script from "next/script";
import * as gtag from "utils/ga";
import { useEffect } from "react";
import { AppProps } from "next/app";
import { useRouter } from "next/router";

const App = ({ Component, pageProps, err }: AppProps & { err: Error }) => {
  const router = useRouter();

JonDotsoy

Conventional Commits to Terminal (zsh, sh)

Git alias conventional-commit and m to create conventional commits so fast. And prepare the scope with the alias git scope <scope-name>.

How to install

Run the next line in your shell terminal

shakna-israel

Let's Destroy C

I have a pet project I work on, every now and then. CNoEvil.

The concept is simple enough.

What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?

---

DimosthenisK

import { SetMetadata } from '@nestjs/common';

export interface SelfDecoratorParams {
    userIDParam: string;
    allowAdmins?: boolean;
}

export const Self = (params: SelfDecoratorParams | string) =>
    SetMetadata(
        'selfParams',

Tomcc

Client Blob Cache

What's the Client Blob Cache

The Client Blob Cache is a new Bedrock optimization - it allows blocks and biomes to be cached on Clients to avoid resending identical chunks over and over. Chunks and biomes make up the vast majority of network traffic in a lot of common cases (eg. login, teleport or dimension switches) but at the same time, they rarely change. Allowing the Client to reuse chunks it has seen in the past can save a ton of traffic and latency!

The Client Cache is a Content Addressed Storage (a bit like git) that stores Blobs and retrieves them based on their full hashes (BlobIds). This means that the cache doesn't actually know about Chunks - in the future, we might start using it for more types of data, like skins or data driven entities.

A nice thing we get from the CAS approach is that the cache is persistent: returning players will be able to reuse content that was sent them in previous sessions or even previous sessions in different servers as long as tha

Ciantic

import { createConnection, getConnection, Entity, getRepository } from "typeorm";
import { PrimaryGeneratedColumn, Column } from "typeorm";

@Entity()
export class MyEntity {
    @PrimaryGeneratedColumn()
    id?: number;

    @Column()
    name?: string;

SOF3

<?php
namespace SOFe\YieldTask;
use pocketmine\plugin\Plugin;
use pocketmine\scheduler\PluginTask;
class YieldTask extends PluginTask{
  const UNIT_TICKS = 1;
  const UNIT_SECONDS = 20;
  const UNIT_MINUTES = 1200;
  private $generator;
  private $factor;

Pulimet

adb help // List all comands

== Adb Server
adb kill-server
adb start-server 

== Adb Reboot
adb reboot
adb reboot recovery 
adb reboot-bootloader

jocopa3

For advanced users, a syntax highlighter for sublime text and
textmate which makes reading the list easier can be found here: 
https://gist.github.com/jocopa3/e4a35921e4f978572e7f45360d231f37

============ Blocks ============

All blocks as found in the 1.1.0.0 Block::initBlocks function. 
Block names are the same names used in the /give command.

Name                            Id          Data