#72 Writing your styles in JS ≠ writing inline styles
sponsor
These 4 Tutorials Create a New Language in Less Than 200 Lines of Code
Have you ever wanted to design your own programming language? It seems like such fun, but if you’ve ever tried you probably got stuck right around the time you read “LLR Decent Parsers and Abstract Syntax Trees.” Traditionally designing your own language was hard because it requires a very specialized set of arcane tools, tools that take a long time to learn and use effectively. But it doesn’t have to be this way. Ohm, a new compact parser toolkit from the team at HARC, lets you build your own languages with simple and clean Javascript.
this week's favorite
Writing your styles in JS ≠ writing inline styles
With the emergence and popularity of libraries like Radium, JSS, Aphrodite and styled-components everybody has been talking about writing styles in JavaScript. What many people don’t realise is that there’s a difference between what’s called “inline styles” and what’s called “CSS-in-JS”.
Testing a React-driven website’s SEO using “Fetch as Google”
I recently tested whether client-side rendering would prevent websites from being crawled by search engine robots. As my article showed, React doesn’t seem to hurt search engine indexing at all. Now I’m taking it to the next level. I’ve set up a sandbox React project to see exactly what Google can crawl and index.
We supply a react implementation antd following Ant Design specification, which designed to help developing RIA such as dashboards or other enterprise-like complex UI needs.
Redux is a state management library that lets you connect directly to application state from anywhere in your app. It also allows you manipulate application state from anywhere in your app. But, to work its magic, Redux requires that your app have a single data store.
Rules For Structuring (Redux) Applications
As our applications grow, we often find that file structure and organization to be crucial for the maintainability of application code. What I want to do in this post is to present three organizational rules that I personally follow on my own projects. By following the rules, your application code should be easier to reason about, and you will find yourself wasting less time on file navigation, tedious refactoring, and bug fixes.
newsletters
Would you like to become a sponsor and advertise in one of the issues? Check out our media kit and get in touch.