mxstbr

33 ms·

421.
by mxstbr 10y ago
Extremely sorry about that, was totally unrelated to the header. Finally managed to replicate it and fixed it! Really super sorry for the horrible experience.
422.
by mxstbr 10y ago
Tracked it down and fixed it, should work fine again now – sorry about that!
423.
by mxstbr 10y ago
Finally tracked it down and fixed it, should work fine again now! Extremely sorry about that, totally my fault.
424.
by mxstbr 10y ago
I've been trying to replicate this bug for ages now, I have no idea what's going on! :( Massively sorry for the troubles! Which device/browser are you on?
425.
by mxstbr 10y ago
Yeah I can't replicate it either on my OnePlus with Chrome. Really confused what's going on here, as I don't do any JS routing things at all...
426.
by mxstbr 10y ago
Super sorry about that, will get it fixed ASAP! (currently at a Christmas dinner with family...)
427.
by mxstbr 10y ago
Oh no! That's definitely a bug. What device/browser are you on?
428.
by mxstbr 10y ago
Thank you, you cannot imagine how much I appreciate that! The time I spent making that look the way it does... That just made it all worth it.
429.
by mxstbr 10y ago
Hey Fahim, thanks for the kind words! ---- I have a discount coupon for the course... It was originally meant for my friends, so I hope Fahim doesn't mind me sharing it, but if you enter "au-christmas" during checkout you can
430.
by mxstbr 10y ago
I remember first meeting you in the Reactiflux Discord during a lively discussion about Redux or somesuch. It's been amazing to follow your journey and I can't wait to see where you'll be going!
431.
by mxstbr 10y ago
Thank you for the kind words! I absolutely agree, many junior developers are afraid to jump into open source – even though they totally don't have to be! The pain points you have while developing, no matter at which level of experience
432.
My journey from high school to a feature in Forbes (thanks to you)(mxstbr.blog)
220 points by mxstbr 10y ago|64 comments
433.
Rest-your-eyes: Rest your eyes while your terminal commands run(github.com)
5 points by mxstbr 10y ago|0 comments
434.
Tagged Template Literals – The magic behind styled-components revealed(mxstbr.blog)
8 points by mxstbr 10y ago|0 comments
435.
Shipping Flowtype Definitions in NPM Packages(medium.com)
9 points by mxstbr 10y ago|0 comments
436.
by mxstbr 10y ago
You can choose to style styled components any way you want too! You can pass in class names, inline styles, whatever you want just works. No need to be aware of styled-components from the user side at all. Imagine Button being a styled comp
437.
by mxstbr 10y ago
We're currently writing some documentation specifically pertaining to theming third-party component libraries, which you can read the WIP of here: https://github.com/styled-components/styled-components-exper... Th
438.
by mxstbr 10y ago
Would you mind chiming into that issue with what you imagine? I hadn't thought about caching yet, that's a good use-case for a separate CSS file! We also almost have a proper server-side rendering API[0], in case you haven't
439.
by mxstbr 10y ago
This is useful for structuring components internally, but sadly doesn't help solve the theming issue at all :-( What you want from theming is a global skin. You want users of your component library to be able to say "I want all of
440.
by mxstbr 10y ago
Theming is on of the big reasons we saw the need to make styled-components[0] (new lib to style React apps and component libraries) I'm one of the maintainers of ElementalUI, and Glen Maddern, the styled-components co-creator, one of t
441.
by mxstbr 10y ago
If anybody has questions related to the article (or anything else I might be able to answer really) feel free to ping me here!
442.
by mxstbr 10y ago
It's going to be so much fun, I can't wait to see you there!
443.
Hedron: A no-frills flexbox grid system for React(github.com)
3 points by mxstbr 10y ago|0 comments
444.
by mxstbr 10y ago
This looks gorgeous! I really like the API so far, can't wait to see where this goes!
445.
by mxstbr 10y ago
Hey Andrey! :wave: If you reading this are interested in a discussion about this, read this tweet by Andrey and the following replies: https://twitter.com/andreypopp/status/786524437843615744 :)
446.
by mxstbr 10y ago
To elaborate on this just a tiny bit, you can use tachyons-js[0] by the amazing jongold to automate even more of this: import tachyons from 'tachyons-js'; const tachyonsHelperFunc(props) => Object.keys(props).map(pro
447.
by mxstbr 10y ago
I very much realize that, which is why I've been pushing towards people recognizing this because it _does_ make a huge difference! (as seen by the OC that kicked off this discussion)
448.
by mxstbr 10y ago
Sorry, how do you mean "rerender the styles multiple times"? The only time any styles ever change is if one of your interpolations changes, but otherwise we don't do much calculation at all! That being said, there might be a
449.
by mxstbr 10y ago
Hah, small world! (if you want to call HN small) Glad you liked it :)
450.
by mxstbr 10y ago
Exactly, they use inline styles, we use CSS. :) (that's the difference between _inline styles_ (<p style={styles} />) and CSS-in-JS (<p className={styles} />) libs)

More ›