Functional programming gets a bad wrap about being too hard for mere mortals to comprehend. This is nonsense. The concepts are actually quite simple to grasp.
The jargon is the hardest part. A lot of that vocabulary comes from a specialized field of mathematical study called category theory (with a liberal sprinkling of type theory and abstract algebra). This sounds a lot scarier than it is. You can do this!
All examples using ES6 syntax. wrap (foo) => bar means:
function wrap (foo) {
| html { | |
| /* Adjust font size */ | |
| font-size: 100%; | |
| -webkit-text-size-adjust: 100%; | |
| /* Font varient */ | |
| font-variant-ligatures: none; | |
| -webkit-font-variant-ligatures: none; | |
| /* Smoothing */ | |
| text-rendering: optimizeLegibility; | |
| -moz-osx-font-smoothing: grayscale; |
| #!/bin/bash | |
| if [ -f ~/Library/KeyBindings/DefaultkeyBinding.dict ]; then | |
| echo "~/Library/KeyBindings/DefaultkeyBinding.dict already exists" | |
| exit -1 | |
| fi | |
| mkdir -p ~/Library/KeyBindings | |
| cat << EOF > ~/Library/KeyBindings/DefaultkeyBinding.dict | |
| { | |
| "₩" = ("insertText:", "\`"); |
| /* ******************************************************************************************* | |
| * GLOBAL CONFIG | |
| * Vue.config is an object containing Vue’s global configurations. | |
| * You can modify its properties listed below before bootstrapping your application. | |
| * https://vuejs.org/v2/api/#Global-Config | |
| * ******************************************************************************************* */ | |
| // Configure whether to allow vue-devtools inspection | |
| Vue.config.devtools = true |
Note:
When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.
If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:
I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
| const MY_DOMAIN = "agodrich.com" | |
| const START_PAGE = "https://www.notion.so/gatsby-starter-notion-2c5e3d685aa341088d4cd8daca52fcc2" | |
| const DISQUS_SHORTNAME = "agodrich" | |
| addEventListener('fetch', event => { | |
| event.respondWith(fetchAndApply(event.request)) | |
| }) | |
| const corsHeaders = { | |
| "Access-Control-Allow-Origin": "*", |
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d
| // pages/_app.js | |
| import ReactNativeNextJsScrollRestore from '../react-native-next-scroll-restore' | |
| import { useEffect } from 'react' | |
| function MyApp({ Component, pageProps }) { | |
| useEffect(() => { | |
| const unsubscribe = ReactNativeNextJsScrollRestore.initialize() | |
| return () => { |
