pax_americana
pax_americana on Hacker News
Chrome just added CSS Anchor Positioning this year. The other browsers also expressed interest in implementing it, with Firefox having announced an Intent to Implement. The feature would likely be available on all major browsers sometime next year.
So here's how your example would work using it:
.outer {
width: 100%;
height: 400px;
background: aliceblue;
anchor-name: --outer;
}
.left {
width: 100px;
height: 100px;
background: white;
position: absolute;
position-anchor: --outer;
left: anchor(left);
align-self: anchor-center;
}
.center {
width: 150px;
height: 200px;
background: pink;
position: absolute;
position-anchor: --outer;
justify-self: anchor-center;
align-self: anchor-center;
}
.right {
width: 160px;
height: 150px;
background: gray;
position: absolute;
position-anchor: --outer;
right: anchor(right);
align-self: anchor-center;
}
Source: https://developer.chrome.com/blog/anchor-positioning-api
If you’re doing animations in JS, better do it with the Web Animations API since it’s also hardware accelerated.
Reddit is actually undergoing a rewrite for their web frontend, which now heavily uses web components using lit. You can try it by accessing sh.reddit.com or using reddit without logging in.
Google libraries are a different story compared to their software products. AngularDart is hardly used outside of Google that it's practically dead and no longer maintained for use externally. However it's alive and well inside Google and still have internal releases within the company. Since Flutter is heavily used outside as well as inside, Google will have to consider the man-hours of rewriting everything Flutter has touched in order to decide dropping it, which means never basically. So even if Flutter is dropped by the community using it, it would still be maintained by Google for their internal use.
Publicly it's dead, but it's alive and well and constantly getting updated inside Google.
Here's a pretty good explanation.
https://stackoverflow.com/a/53234826
There is a library that would allow you to declare functional components, however it relies on code generation which might discourage others from using it. Dart is planning on adding static metaprogramming though, and that might provide a way to introduce functional components to Flutter without codegen.
You seem you have a hate boner for CanvasKit. It's just a Skia project that Flutter uses as one of its render targets. It's main use is to provide a better Canvas painting API than what browsers offer natively.
I believe the Stadia app is the only mainstream Google iOS app that is written in Flutter. The rest are native apps (Swift/Objective C) but specifically implements Material design.
I think you're confusing fuchsia and flutter. Fuchsia is a new OS while flutter is it's native UI. I don't think "uncanny" is applicable here.
All four features of the Web Components Spec (Shadow DOM, Custom Elements, HTML Import and Template Element) are the top most requested features in the MSEdge Developer Uservoice. <template> has already been implemented while the remaining three are on their backlog.
https://wpdev.uservoice.com/forums/257854-microsoft-edge-dev...
Posted by
pax_americana on Thursday August 25, 2016 @10:21PM
from the qmlweb.github.io dept.
The project has been consistently updated this past few months. I don't get why you've said it hasn't changed for two years.
Posted by
pax_americana on Sunday April 10, 2016 @12:08AM
from the github.com dept.
Polymer is not a polyfill for the standards. It's just a library for creating web components in a less boilerplatey manner. The polyfill library is called webcomponents.js.
I find it amusing that those two mirror XML and JSON respectively.
I disagree. I think QML is faster to prototype (you can export an existing PSD file to qml). Also QML's anchor-based layouts >>> flexbox.