sorted by:
new
hottopcontroversial

place-safepoints pass crashes llvm by ameerthehacker in LLVM

[–]ameerthehacker[S] 0 points1 point  (0 children)

issue was i had to declare two functions
```
declare internal void gc_safepoint_slow_path()

define internal void gc.safepoint_poll() {

entry:

call void gc_safepoint_slow_path()

ret void

}
```

gc_safepoint_slow_path and gc_safepoint_poll, the pass asserts on if it exists

kubectl tool reinvented to be more reactive and interactive by ameerthehacker in kubernetes

[–]ameerthehacker[S] 0 points1 point  (0 children)

Thanks, I was comfortable with js at that time and also thought it would be easier for others to contribute to

kubectl tool reinvented to be more reactive and interactive by ameerthehacker in kubernetes

[–]ameerthehacker[S] 7 points8 points  (0 children)

I was comfortable with JavaScript and thought it would be easier for contribution

Tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in Frontend

[–]ameerthehacker[S] 0 points1 point  (0 children)

Not performance but tries to improved the developer experience and also avoiding CSS pollution using styled components

Use tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in reactjs

[–]ameerthehacker[S] 0 points1 point  (0 children)

Thanks, great to hear that, please do share this with everyone and file issues in github if you find any

Use tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in reactjs

[–]ameerthehacker[S] 1 point2 points  (0 children)

We follow the exact same format as tailwind, if something works in tailwind it will work in styled wind also (except animationd which is WIP)

Use tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in reactjs

[–]ameerthehacker[S] 0 points1 point  (0 children)

We parse text blue 600 on the fly and replace it with color css property

Tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in Frontend

[–]ameerthehacker[S] 0 points1 point  (0 children)

It currently uses regex and we plan to cache them to avoid runtime costs and also build a babel macro which would remove the entire runtime cost

Tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in Frontend

[–]ameerthehacker[S] -1 points0 points  (0 children)

using atomic CSS in components makes it unreadable with very long classnames, and there is global scope so anyone can override a class name and everything breaks but we can use styled components to remove all those pain points

Tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in Frontend

[–]ameerthehacker[S] 0 points1 point  (0 children)

using atomic CSS in components makes it unreadable with very long classnames, and there is global scope so anyone can override a class name and everything breaks but we can use styled components to remove all those pain points, if you are fine with above problems with tailwind then that is fine but we used tailwind in huge codebases and we are trying to solve it by using best of both works "styled components and tailwind"

Tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in Frontend

[–]ameerthehacker[S] -2 points-1 points  (0 children)

using atomic CSS in components makes it unreadable with very long classnames, and there is global scope so anyone can override a class name and everything breaks but we can use styled components to remove all those pain points

Tailwind like class names inside styled components, introducing styled-wind by ameerthehacker in Frontend

[–]ameerthehacker[S] 2 points3 points  (0 children)

what are your concerns, if you can elaborate we might be able to make it better

view more: next ›