I was referring to how React and Vue have a whole internal virtual implementation of the DOM which prevents many vanilla JS libraries from working with them.
Svelte is built to not require this abstraction (VDOM), which increases the likelihood that it will work with other JS libraries out of the box.
> Component state should only contain volatile data that is not important to save, the opposite of LocalStorage.
Where do you store data that you retrieve from a server for rendering? Storing it in the state is perfectly fine. In this example, data is retrieved from local storage and stored in the state.
Fair point, but server state is tied ti my account, LS is not. You can tie LS to the account, but IMO that would be out of scope for an "everything component" approach, like the article.
It's good to see UX design problems analyzed from a technical perspective. Designers working on the web should be proficient at understanding the medium on which they work, and look beyond generating static images to toss over the wall for implementation.
This is missing a critical web design aspect that I see most developers miss: Space.
Paying attention to how things align, how big they are, how much and how consistent the spacing around elements is will make a huge improvement to the perception of the UI.
I've started seeing more cooking clips that are actually pretty well made and work well on the medium. If more content creators of various interests adopt it as a platform, it might be worthwhile.
Despite the press of the young player-base, Fortnite fills what you describe for me. The building mechanic creates so much opportunity for think-fast, improvise, and outsmart your opponent moments. Plus, playing solo means you don't have to interact with anyone if you don't want to.
Apex Legends is good for improvisational gameplay that doesn't involve memorising building patterns. Also it's free!
The tactical opportunities in a fight that are available to a team with a gibraltar and pathfinder vs a gibraltar and pathfinder.. huge. Where does the shield go? Is claiming the high ground worth exposing yourself to the airstrike?
Hi from Apollo! My team (Developer Experience) is responsible for making sure you can find what you need in the docs. What improvements would you like to see?
A more consistent documentation experience. A lot of code examples import various modules, but those modules have no documentation. For example: Docs > Client > Apollo Link mentions `graphql-tools` and schema stitching, with a link to read more. Clicking that link takes you to a page that says it's deprecated, and then links to a blog post about why.
Another example: Is `apollo-link-state` deprecated? The docs for `apollo-link-state` don't mention that, but the Local state management page in Apollo Client sure says it is.
Similar to the deprecation issue, a number of Links still say "under active development" or similar pre-release "warnings" in their GitHub READMEs but that isn't reflected in the documentation site, making it tough to figure out what is considered stable and what isn't without jumping back and forth between GitHub and the documentation site, and there's still questions of whether or not perhaps the README warnings are stale. It would also maybe be great to have something of a roadmap of when those links might be considered "production ready" especially if the documentation site is already recommending them as project solutions.
The example to mind is last time I was trying to do something (a few months back) `apollo-link-rest` was highly recommended in the documentation as a potential solution, but yet visiting the GitHub for it seemed to be saying the exact opposite that it wasn't ready yet and was filled with massive API shifts and bugs/issues to iron out before "production ready".
This is mostly pervasive because of agency/client relationships. Most clients go to an agency with a budget, and the agency, in good faith, is out there paying location data services to target their ads. Then a report is generated, passed to the client along some sort KPI that increased, and everyone is happy. This fraud exists because the market allows it.
I'm in a similar camp to yours. I've used tonnes of text editors across Windows / Mac / Linux, and Notepad++ was simply the best amongst all of them.
TextMate comes closest on the Mac which is why it's my primary GUI editor, but I still miss being able to do all the stuff that just came "naturally" in Notepad++.
Also, running Notepad++ in Wine just doesn't feel the same.
Centro | Digital Advertising Platform | Senior and Mid engineers, UX Designer, Product Managers | Chicago, IL | Full-time | https://www.centro.net
We build Basis, Centro's answer to the challenging and convoluted digital advertising landscape. Our engineering teams across North America work closely with product managers, designers, and testers, creating well-crafted solutions to the complex problems of our industry. Our sales team is top notch, and is hitting their targets for rapidly growing our client roster. As an engineering organization, we are aggressively optimizing to reach this scale, while at the same time building industry-leading features that will land even larger clients.
Our stack is Ruby on Rails, Node, React, PostgreSQL, Redis, RabbitMQ, AWS
React is the closest to standard JS in my experience.