fantactuka

"use strict";

import type { LexicalEditor, LexicalNode } from "Lexical";
import type { Binding, Provider } from "LexicalYjs";

import {
  createBinding,
  syncLexicalUpdateToYjs,
  syncYjsChangesToLexical,
} from "LexicalYjs";

Widdershin

In the olden days, HTML was prepared by the server, and JavaScript was little more than a garnish, considered by some to have a soapy taste.

After a fashion, it was decided that sometimes our HTML is best rendered by JavaScript, running in a user's browser. While some would decry this new-found intimacy, the age of interactivity had begun.

But all was not right in the world. Somewhere along the way, we had slipped. Our pages went uncrawled by Bing, time to first meaningful paint grew faster than npm, and it became clear: something must be done.

And so it was decided that the applications first forged for the browser would also run on the server. We would render our HTML using the same logic on the server and the browser, and reap the advantages of both worlds. In a confusing series of events a name for this approach was agreed upon: Server-side rendering. What could go wrong?

In dark rooms, in hushed tones, we speak of colours.

pedronauck

import React from 'react'
import { Link } from 'systems/Core/Link'
import css from 'styled-jsx/css'

export const Header = () => {
  return (
    <header className="Root">
      <img src="/logo.svg" width={100} />
      <div className="MainMenu">
        <ul className="MenuList">

sebmarkbage

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

JoeyBurzynski

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

jdx

package main

import (
	"io"
	"log"
	"net"
	"time"
)

func reader(r io.Reader) {

jeffpamer

ffmpeg -i input.mp4 -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level 3 -an -vf "scale=-1:1440, reverse" -preset veryslow -g 2 output.mp4

// -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level 3
// Encode for web with a good balance of browser compatibility and compression ratio

// -an
// Strip audio tracks

// -vf "scale=-1:1440, reverse"
// Scale video to 1440px wide, maintaining aspect ratio

aquiseb

// Embedded in this article https://medium.com/p/c98e491015b6
package main

import (
	"fmt"
	"log"
	"net/http"
	"time"

	"github.com/graph-gophers/graphql-go"

gricard

If you enjoyed reading this, I'm intending to do more blogging like this over here: https://cdgd.tech

This is not a complaint about Webpack or v4 in any way. This is just a record of my process trying it out so I could provide feedback to the webpack team

Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it. All I need to do is npm i -D webpack@next, right?

+ webpack@4.0.0-beta.2

eeropic

//CC2018
document.addEventListener('paste', function(evt) {
    //Import SVG copied to clipboard from Illustrator
    //remove last hidden character that will otherwise break the import
    if(document.activeElement.nodeName!="TEXTAREA"){
        var str=evt.clipboardData.getData('text/plain').slice(0, -1);
        var svg=project.importSVG(str)
        svg.clipped=false;
        svg.children[0].remove()
        svg.parent.insertChildren(svg.index,svg.removeChildren());