Also interested in the custom styles. Although I like the redesign, it's all over the place typographically – 300 only for h1, 400 for h2 with a slight increase in letter spacing (?!) – but can't be bothered to apply a fix myself.
If anything it's the least harmful way of generating a profit. Better than restricting parts of the site. Besides, a subscription service like this is something employers will most likely be paying for, not developers – unless you're a freelancer, in which case it still would count as a business expense.
Love the update. The color-coded pages are also very useful. Though I wish they had an option to hide deprecated methods and properties, or at least put them in a different group.
It seems caddyserver makes certificates a lot easier to work with. Certbot is pretty much on par with NGINX in terms of challenging documentation and foot guns.
My only pet peeve with these "laws" is the endless amount of people eager to come up with their own in hopes to be quoted in articles like these. Most of them don’t even make sense and read more like a meme, like “Atwood’s Law”: "Any application that can be written in JavaScript, will eventually be written in JavaScript.”
It is. However it's unbearably slow when generating previews for prototypes. XD and Sketch are great for quick prototyping and Figma for actually implementing a large scale design system.
Glad to see Tiptap getting more attention. I've used 1.0 and 2.0 and they've both been great to work with. However one GIANT roadblock in the project I was working on was the inability to create custom inline components, like say a link with inline buttons for removing/changing the url. I believe there still isn't support for this type of functionality.
Funnily enough the quote on textmate grammars in the article feels quite relevant:
>The fact that we now have these complex grammars that end up producing beautiful tokens is more of a testament to the amazing computing power available to us than to the design of the [TextMate] grammar semantics.
It’s disappointing to see that the consensus among frontend devs is to just sit and wait for a new API from react to do all the work. Every framework out there has simple methods for rendering a component to string which can be returned to the client.
Font licensing is annoying even for people in the industry itself – sadly a lot of it has to do with piracy and others who purposefully buy cheaper licences. Though my advice is to just look further, you won't see Monotype change their licensing model any time soon, but foundries like ABC Dinamo have made significant changes (like only taking company size into account, not users or pageviews) that others have started to adopt.
PWA still sounds to me like a 2015 buzzword from Google that never quite took off as everyone hoped it would. Perhaps the lack of support on Firefox could have something to do with it.
Fantastic. Thanks for including the link. It's pretty clear he's making a point of quoting the dialogue in and out of context. His tone makes the lecture pretty engaging to be honest.