secoif

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.

Comment · 9 years ago

For data that's mostly to do with the the API provided by the particular mongodb driver, than mongodb itself. Mongo stores and transmits BSON, not JSON. Most mongo drivers expose an API that serialises your data to BSON for writes and wraps the BSON data with a JSON-like interface for reads.

Comment · 10 years ago

Doing it this way requires overriding every single built-in rule that uses the property you're trying to override… including states like :hover, :before, :disabled, :disabled and :hover, etc which can be easy to miss.

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.

Comment · 10 years ago

These components look and work great, but unfortunately are a real headache to retheme unless you want to pull in a sass/less toolchain in addition to what you're currently using. This is a pain in the ass if you already have your theme variables set up in one compiles-to-CSS language.

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.

Comment · 10 years ago

Compiled JavaScript?

Comment · 10 years ago

technical debt and not wanting to break people's workflows

Comment · 10 years ago

no, it just installs everything it can into the top level node_modules. npm@2 would do this to a degree as well, it was just less sophisticated about it.

Comment · 10 years ago

what you described is npm@2's behaviour. npm@3 will flatten dependencies as much as possible

Comment · 10 years ago

My experience with melatonin:

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.

Comment · 10 years ago

Did this as a course on Coursera with a group of friends. Highly recommended.

Comment · 10 years ago

> "…they care more about monetizing their users than their users privacy or interest."

Sadly this is true for all but a handful of companies.