While I did like some components from Antd and intend to look into the source, from a basic overview, a lot of the documentation seems to be in Chinese.
Show HN: Antd – A set of high-quality React components
91–100 of 107 posts
Re: Show HN: Antd – A set of high-quality React components
#92The design is good. It look nice! But it is very heavy compared to native HTML and CSS. It's like taking a space ship, to go visit your neighbor.
It's actually super light, i don't know where you got the impression that it's heavy. This is not a monolith but a modular kit - you only load what you use which makes it different from many other UI kits which give you megabytes of CSS on first load. Also, this is native HTML and CSS of course, with proper definition, types and handlers laying out what the component can do: https://github.com/ant-design/ant-design/b…
Hello worldRe: Show HN: Antd – A set of high-quality React components
#93Earlier quoted context omitted.
Hey, can you tell us more? I'm very interested in Weex :) What make it solid ? what are the pros/cons ? Last time I checked I thought I need to know chinese as 95% of issues are in chinese for example. Is it still a prob ?
> Last time I checked I thought I need to know chinese Fascinating. This is probably the first time I've seen a huge open source project where a majority of the contributions are in a language that's not English. I've seen plenty of projects from non-native English speakers, but everything was still done in English. I'm sure there are tons of other big projects in Chinese and other languages, but programming has alwa…
At the end of the day, english has "won" as the language of keywords in programming. And while i'm glad that most newer languages have the ability to code everything but keywords in your native language (i've worked with JS that has variables and function names in other scripts), translating the keywords seems like a pointless process that would do nothing but cause incompatibility.
[0] https://en.wikipedia.org/wiki/Non-English-based_programming_...
Re: Show HN: Antd – A set of high-quality React components
#94This stuff is horrible to use from the keyboard visually, because outlines have been removed without an adequate replacement. Please fix the styles for :focus et al. Make it all obvious, like Microsoft have done in Windows 10 (they have what is pretty much just a 2px solid black outline).
a11y optimization is in progress, but it is not a high priority job.
Re: Show HN: Antd – A set of high-quality React components
#95Earlier quoted context omitted.
Hey, can you tell us more? I'm very interested in Weex :) What make it solid ? what are the pros/cons ? Last time I checked I thought I need to know chinese as 95% of issues are in chinese for example. Is it still a prob ?
Hit the demos for Weex and compare them to Ionic 2. It's still day and night imho, whereas Ionic 2 looks very polished.
I'm looking at the demos now, but my main concern is how these behave on mobile apps. Performance, ease of development, etc. I have little concern for how they behave on my mac, fwiw. (performance on my mac may be related to mobile performance, but due to the very different architecture behind ReactNative style mobile apps, i'm skeptical to compare desktop performance)
Re: Show HN: Antd – A set of high-quality React components
#96This stuff is horrible to use from the keyboard visually, because outlines have been removed without an adequate replacement. Please fix the styles for :focus et al. Make it all obvious, like Microsoft have done in Windows 10 (they have what is pretty much just a 2px solid black outline).
Re: Show HN: Antd – A set of high-quality React components
#97Earlier quoted context omitted.
It's actually super light, i don't know where you got the impression that it's heavy. This is not a monolith but a modular kit - you only load what you use which makes it different from many other UI kits which give you megabytes of CSS on first load. Also, this is native HTML and CSS of course, with proper definition, types and handlers laying out what the component can do: https://github.com/ant-design/ant-design/b…
It's a weak abstraction with maybe hundreds of nested dependencies and many compile steps. A lot of things that can go wrong ... Just to do this: Hello world
To "just" use self contained, configurable, property-defined components that can be shared, re-used, filled with state - that isn't trivial. Which is why they're React components. The components themselves are very lean, there's a bit of code, some markup, a piece of CSS and that's that. The code i have linked compiles down to a couple of bytes.
Re: Show HN: Antd – A set of high-quality React components
#98It appears the team chose to make an oddly generically named babel plugin: `babel-plugin-import` which seems to do some manipulation of CSS/SASS/etc styles (which seems out of scope for babel). I assume the generic name was chosen hoping other libraries would embrace a similar pattern, however, I'm not seeing any spec defining how another library should implement this.
Re: Show HN: Antd – A set of high-quality React components
#99Earlier quoted context omitted.
Hit the demos for Weex and compare them to Ionic 2. It's still day and night imho, whereas Ionic 2 looks very polished.
Can you be more explicit? I just want to make sure i understand you correctly. Do you believe Ionic 2 is better? I'm looking at the demos now, but my main concern is how these behave on mobile apps. Performance, ease of development, etc. I have little concern for how they behave on my mac, fwiw. (performance on my mac may be related to mobile performance, but due to the very different architecture behind ReactNative…