HN user

Griever

298 karma

[ my public key: https://keybase.io/jpsullivan; my proof: https://keybase.io/jpsullivan/sigs/wodDUXOsqn9NsVwHOGBjmDks7D5WN8xROAbxFgOoHH4 ]

Posts0
Comments133
View on HN
No posts found.

Great question. We rarely rely on shared utility classes these days. Historically we'd end up going the @apply route, but lately we just add a new style to the root-level css file and call it a day. We may prefix it with "@layer" so that it gets tree-shaken, but that's about it.

I've found that in component-driven UI, the need for these kinds of utility classes becomes less and less necessary. The utility CSS may be defined in the component, and the component is ultimately what gets reused.

Could you elaborate more on the reason for your interest? I've used Tailwind to implement several well-defined design languages, and always had great success. In fact, compared to other design systems, Material for example, I found it to be far simpler to manage over time.

Children of Men 4 years ago

Mostly echoing everyone else’s appreciation for the film in the thread. I was sucked in when I saw it the first time, and it’s one of the few movies I regret not seeing in theaters when it was available. If Alamo ever decides to do a special showing of it, I’d be there in a heartbeat.

It’s upsetting how as the years go on, I’m seeing more and more similarities to the world that the film depicts. But in a strange way, that makes the film all the more important to me.

Angular 11 6 years ago

To address your point about the lack of fragments: It's not as clean as React's implementation, but you can set a component to "ViewEncapsulation.None" to help address this.

Within a components template though, I frequently use <ng-container> to execute async pipes, or to perform simple conditional logic without adding unnecessary divs.

I was in a similar situation, and ultimately decided to reimplement the state management using NGXS. Fortunately the app was relatively small at that point, but I found that it held the developers hands a bit more, which lead to significantly more readable code.

Things can still get tangled up once you start using "ofActionDispatched" lifecycle handlers, but overall I found them to be far more manageable over time than NGXS.

AvE - very intelligent and humorous guy who tears down tools and explains how they work. Probably my favorite channel.

Edge Precision - heavy duty CNC machinist https://www.youtube.com/channel/UCCkSr3M8GXbS4txqPY7OMxQ

Essential Craftsman - construction, tools, etc. Has a great new series where he is walking through the entire construction of a home, dubbed the "spec house" https://www.youtube.com/channel/UCzr30osBdTmuFUS8IfXtXmg

Frank Howarth - woodworking https://www.youtube.com/user/urbanTrash

Matthewmatosis - long-form video game analysis https://www.youtube.com/user/Matthewmatosis

NurdRage - incredibly interesting high level chemistry (to me at least). Has a really great series where he finds a new way to make Sodium Metal. https://www.youtube.com/user/NurdRage

RR Buildings - post-frame construction, tool reviews https://www.youtube.com/channel/UCWXEQsK3UiHszjwgGN5HUeQ

This Old Tony - machining, welding. Very funny! https://www.youtube.com/user/featony

Vancouver Carpenter - mostly drywall tips. Offers very clear explanations of how to do various drywall jobs https://www.youtube.com/channel/UCbZdXox6mKHdcT2QdVT-goQ

Anvil Firing 7 years ago

The "Spec House" series is incredibly valuable if you're even remotely interested in building your own home. I'm incredibly excited to see how that series continues!

I consider Essential Craftsman to be one of the best YouTube channels out there. If you're interested in tools, construction or history in heavy industry, definitely give it a look.

Not entirely. I do approach new projects with a bit more scrutiny than before, which I consider to be a good thing.

I do a lot of small projects here and there. I'm currently working on one that I've been chipping away at for the last six months or so, but it's coming along at a much more relaxing pace.

While I do think that it's important to finish what you start, I also believe that knowing when to stop is just as valuable.

I admittedly haven't looked at it since I gave up on my personal project, so I'm not entirely sure of it's state. However, a quick glance at the changelog seems to indicate that it supports .NetCore in some fashion.

https://github.com/apache/lucenenet/blob/master/CHANGES.txt

It'd be a shame if they discontinued it! A lot of incredibly smart and dedicated folks have put their hearts and souls into that project.

I spent about three years working on a webapp for simplifying the RFQ process, specifically for defense projects. Ultimately I decided to finally call it quits on the app when I realized that even if I built this thing, I'd never have the skills/time/patience to sell it. Wish I had realized that sooner!

After work I would typically spend a few hours a night hacking away at whatever feature I thought was a "must have". Suddenly the list of features that were absolutely needed to ship a 1.0 release grew quite long, and was too much to manage on my own.

I called it quits a few years ago at this point, but I wouldn't say I regret my decision to have put so much effort into a project. It gave me an opportunity to contribute to some high-profile libraries like Lucene.NET and Backbone, and I most certainly grew as a developer.

I wouldn't beat yourself up too hard, though. I'm sure you learned a whole lot about browser limitations, animation, and how to manage your time and expectations in the future. If you agree, then I'd say it wasn't a total loss at all.

As a heavy Inbox user this is definitely a bummer, but I do feel a bit relieved to know what is coming to Gmail.

Last month a video showing some future updates to the Material Design components leaked. If you check out https://youtu.be/0mAude0774I?t=1m27s you can (briefly) see that the version of Gmail they're showing has a lot of functionality seen in Inbox, particularly Trip cards and expandable message bodies. Fingers crossed!

Unless I'm misunderstanding something, wouldn't Tree-Shaking remove the unnecessary code paths from each import? Assuming you're using Webpack 3+ that is.

What were your main issues with Angular? I've been using it over the last year or so (coming from a React background) and I must say I'm quite pleased with how well it works for the team and I.

This is really cool! I've been thinking about a similar idea lately and this seems like a great way of doing it. Do you by chance have any material on how you got the honeywell sensor working with the C.H.I.P. board? (This would be my first electronics project)

I use Win10 on my MBP as well, and I'd say I use it 95% of the time at this point. Definitely runs snappier than OSX, and now with the Linux subsystem running, I rarely have a need to go back.

I only wish Apple would open source BootCamp and allow others to try and fix the few issues that it still has, namely around battery consumption. Highly unlikely they would ever do that, but one can dream.