secoif
If only the government was equally motivated to remedy injustices incurred by those who aren't already filthy rich.
> I wish iOS allowed you to change DNS for celluar networks.
Are you torrenting from your iPhone?
While the rax-redux equivalent seems to be contained in a single file:
https://github.com/alibaba/rax/blob/07e20908e4e17b182873db09...
The simpler implementation might indicate that the rax developers are trimming overcomplicated bloat, or culling features that don't align with specific needs of Alibaba. Or maybe they're just removing code they don't yet understand the necessity for. It's not immediately clear what tradeoffs each are making, but having rax audit what's really necessary could be a good thing for everyone.
I've had some success with simple find & replace preprocessor but this gets complicated if the CSS uses colour manipulation functions e.g. color: color(var(--color-base) tint(50%)), then you're basically going to be re-implementing their whole stylesheet again.
Also, good luck making sure everything still works if and when the components are updated.
Ideally, you alter theme variables in one place, rather than finding and overriding them everywhere they're applied.
There is a standard for CSS variables and a very functional subset of their functionality can be compiled for older browsers at build time: http://cssnext.io, yet as far as I can tell, all of these component frameworks impose some other nonstandard compiles-to-CSS language or one of many possible APIs for writing inline styles.
Inline styles seem to be a trend at the moment but I can only assume the people driving this movement haven't had the experience of working with 3rd party components (which you may or may not have the source for) and needing to alter something the designers didn't expose and simply having no simple options because the damn inline style can't be overridden even by !important. Now you've got to fork whole the f'ing component, possibly multiple, each of which potentially coming with yet another different compiles-to-CSS toolchain all because you wanted to add a single line of CSS.
Admittedly, antd doesn't use inline styles si the above doesn't apply here, but having to maintain a custom builder for antd in order to change some fonts and a few colors was a frustrating experience. Not sure what a good solution is until CSS variables get more browser adoption, but it'd be great if we could collectively start standardizing on standards.
If I take the normal dose of >3mg, I'll experience incredible irritability the following day. I become sensitive to sound and anything that isn't entirely perfect. Things make me feel unreasonably furious. This is bad. These days I always microdose melatonin.
If I don't fall asleep with the first tiredness crash that happens 20-30 minutes after taking melatonin, I find myself restless and unable to sleep for another 4 or 5 hours. The more melatonin I take, the more intense the initial crash will be, but the harder it is to sleep if I miss that crash.
Sadly this is true for all but a handful of companies.
AWS in general is not well documented. Well-written drivel mostly.
My guess is that there's little to no feedback between documentation writers & developers actually trying to use that documentation to achieve real outcomes. Same could be said about many of the AWS UIs.
I would love to pay someone for timely content, but now that Netflix is blocking vpn access there is literally nobody to pay. It's complete madness.
super.propertyOnSuper ~= this.__proto__.propertyOnSuper
super() in constructor ~= ParentConstructor.call(this)
https://github.com/isaacs/inherits/blob/3af5a10c6b51f9e99d9f...
Link should probably go here http://www.taodyne.com/tutorial-2.0.html#/language
Significant & controversial.
The promise of "code reuse" is very alluring but reusing application code rarely happens in reality. However, reuse of patterns and libraries is very common – solve a generic problem once and you don't have to research how to achieve the equivalent in another ecosystem. Just grab the exact same library, browserify the thing and you're done (ideally).
"One language everywhere" grants you lots of flexibility – where your code executes is no longer locked in stone – you can shift responsibilities from the server to client & vice-versa without significant overhead. No need to port to a different language which perhaps lacks similar paradigms or tooling. Doors are opened to optimisations and architectural changes that would not have even been a consideration otherwise.
To get the benefits of "one language everywhere" doesn't necessarily mean "use JavaScript" but it's a safe decision to choose the lowest common denominator; JavaScript is not going out of fashion any time soon, it runs on nearly every platform and has an ecosystem that's competitive in a wide gamut of problems. An investment in vanilla JS will pay out in long term, while any investment in Framework-X or compile-to-js Y or AltJS-Z is high risk and usually only pays out for the 18 months or so while said tool is in vogue.
JS may not be the best choice, but it's a smart choice.