Bootstrap 3.4.0 released
blog.getbootstrap.com
blog.getbootstrap.com
This is a rare moment of empathy in an industry that - judging from other comments here - is ALWAYS on the hunt for the next best thing. Bootstrap has brought me joy and made my life as a developer much easier. Thank you to @mdo & team for keeping it that way.
Unfortunately I ran out of time to be able to continue to maintain it, and now work for one of those big tech companies that requires a lot of approvals to participate in open source anymore unfortunately :( . There are a lot of good fixes pre-2.0 though if you can upgrade to it!
Probably one of the biggest disincentives for continuing to me though were some of the users - some were outright abusive.
https://github.com/thednp/bootstrap.native
It supports most (if not all) of bootstrap’s components, and works well enough that even large-ish projects can do without bootstrap.js (which needs jquery).
React will deal with lifecycle of objects on the screen and state machines to mutate them, but the actual look & feel of the widgetry is defined by whatever ui framework you decide to use (bootstrap, semantic, blueprint, etc).
There are also some Forms like experiences for Web, for example:
https://gist.github.com/primaryobjects/64a4e7e3351c646f51eee...
If you care about people on wireless connections, with less than perfect fiber connections, etc. a 500KB CSS file is going to add seconds to the total page load time and users will see it more often because the size will get it evicted from small caches more frequently. HTTP/2 won't help because the entire CSS file needs to be transferred before the page renders.
Wireless connections have had bad latency, but it's getting better. 15 years ago you could get 200+ ms latency on WiFi. today we are down to around 10-20ms. 15 years ago we only had 100Mbit fiber. If you live in a city today you can get 10Gbe. Meanwhile there are people surfing using satellite up-link, or very poor GSM, so there are strong contrasts. But they probably wont bother loading any CSS (which makes semantic HTML important).
Regular users enjoy only a fraction of those rates, particularly mobile users.
I really hope FE developers in general don't target such unrealistic rates.
Also, it's unclear if the comparison is actually fair- some of these, like Semantic, contain a shit ton of icons.
I was also disappointed to see zero mention of accessibility, which is a deal-breaker for government and large business sites.
Every component has a story, and it’s written in TypeScript (transpiled to JS). I hope to get around to releasing this big update on npm tonight(!) but for now you can use the code straight from GitHub.
Also, the wrapping is complete yet minimal - there are only a couple components with state and you can override those with a `managed` flag.
Also, every component supports ref forwarding (using of course `ref`), and can render as any other component using the `as` prop. For example, if you want to bring your own Form, Link, or Table framework, this will work with that seemlessly.
<Button color=‘primary’ as={Link} to=‘/‘>Go home</Button>
No doubt there would be better solutions more tailored to react out there.
With PostCSS in your pipeline, you can add the tailwind plugin and start composing CSS. This way, you can use your configuration even in places where you are required to write CSS (e.g. for transitions or media queries):
@screen xs {
.item {
@apply border-b border-blue-darker;
transition: background-color 0.2s;
}
}It's a UI library with all imaginable widgets.
element (in vue) is also pretty terrific: https://element.eleme.io/