Google could easily adjust their ranking algorithm to better reward non-AMP pages (which they've obviously already crawled) which they know are 1) below say 75 KB and 2) contain a limited number of resources to fetch. But instead of doing that, they choose to attempt to strongarm everyone into using AMP.
What you're describing is called "replication" in Unreal Engine. It helps tremendously with writing declarative code, and I've found it to be exceptionally powerful and predictable.
I love this architecture so much that I brought it into the world of React and Redux a couple years ago (see https://github.com/loggur/react-redux-provide and https://github.com/loggur/redux-replicate). Dan Abramov and the ReactTraining guys immediately shit on it for some odd reason (I probably did a horrible job of explaining it), saying it wouldn't work in the real world, but I (and my team) have been using it very successfully... in the real world.
With that said, I do need to update the docs and improve some internals (and remove some unnecessary stuff like query handling), but there's only so much time in a day. :)
I'm a full stack expert with years of experience ranging from modern web dev to robotics & embedded systems to gaming engines. Passionate about great tools and great design and I enjoy pushing technology to the next level.
I'm a full stack expert with years of experience ranging from modern web dev to robotics & embedded systems to gaming engines. Passionate about great tools and great design and I enjoy pushing technology to the next level.
These self-driving cars are a good start though. It makes sense - to me at least - that more self-driving cars on the road means fewer accidents. Imagine if nearly every vehicle was autonomous and wirelessly networked with other nearby vehicles. We'd see little to no accidents, assuming everything is secure and working correctly.
This allows you to encapsulate all of your Redux actions/reducers/etc into standalone "providers". It decouples pretty much all of your React components (UI) from your Redux logic (models/controllers), which maximually separates your concerns and makes it trivial to reuse anything anywhere. It also allows you to instantly swap databases and/or websocket implementations.
I believe most of what it's doing under the hood is explained in the article. Sorry if it isn't 100% clear.
Short version:
- A provider has its own store (or it can share a store with other providers if you need it to).
- When you have a `propType` matching a provider's `actions`, those actions are automatically mapped to the store's dispatcher; so when you call `this.props.someAction`, it's essentially calling `provider.store.dispatch(provider.actions.someAction())`.
- And when you have a `propType` matching a provider's `reducers`, that component will always have the latest state of that reducer.
Without the `@provide` decorator, you would just `export default provide(SomeComponent)`. I've opted to use the ES7 decorator because it's cleaner, more concise, and immediately apparent.
There seem to be a lot of similar questions about how to reduce redux's boilerplate and build something real-world with it. I think I found a pretty good solution (among other things) which I wrote about within this article.
TL;DR: You can create redux providers that automatically match themselves to your components based on their propTypes. All you really need is a components directory, a providers directory, and an optional but recommended themes directory. Everything is easily interchangeable, understandable, maintainable, extendable, and reusable. There's a lot more included with all that like hot reloading both client and server, server rendering, etc., etc., etc. I built an app from scratch based on the included boilerplate yesterday and it took about 10 minutes as opposed to the 1 hour it would usually take!
I've been using JSS for everything. It makes the most sense to me. It's minimal in size and function to the point that any extra functionality can be quickly and easily added via `jss.use(plugin)`. And it's maximally modular. Every class is namespaced, and exporting everything to a single sheet for production builds is super simple, as it should be.
My dog can do this. Sadly he was tied to a tree for years before I got him, which is probably how he figured it out. I'll walk him and on extremely rare occasions he will accidentally wrap around a pole or something, and when he realizes he doesn't have any slack, he immediately unwraps himself. I also say "on extremely rare occasions" because somehow he figured out that if there's a tree/pole ahead, he should stay between myself and the tree/pole to avoid ever wrapping around it to begin with. The only times he will go on the wrong side is if he's preoccupied with a smell or something, and even then, he never actually fully wraps around it, as he almost always realizes he should immediately go the other way.
The phrases "political correctness" and "treating people with respect" describe entirely different things. They are not interchangeable without altering the meaning of the sentence, as they refer to two completely different concepts. Whether or not you agree with the intended meaning is irrelevant. The meaning is still there.
Just to be clear, I'm all for treating people with respect, as any decent human being should be. And political correctness is perfectly fine and necessary in most cases, but in most contexts it refers to conforming to certain narratives to avoid scrutiny and being ostracized, which typically only exists to serve some underlying agenda. It's been taken to the extremes lately and conflating "political correctness" with "treating people with respect" is a mistake, because more often than not, political correctness does more harm than good. Imagine there's a serious security flaw in some software but no one will speak up about it because it might result in ostracizing whoever does speak up about it because it offends people. The more freely people are allowed to express themselves, the better off we will all be, regardless of the message. But yes, when speaking freely, one should also be respectful. You can be politically incorrect and treat people with respect at the same time. That is why those phrases are not interchangeable.
It's because it's only text with little to no JavaScript, and I haven't looked at the source behind HN, but presumably, the HTML for every URL is cached upon each change (comment, upvote) and requires very little processing time per user customization.
Most that you've seen are probably using bootstrap (http://getbootstrap.com). Though the only indication of bootstrap I'm seeing within this particular site is font-awesome loaded from the bootstrap cdn.