Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Spectre.css – A Lightweight, Responsive and Modern CSS Framework

github.com

Post reply on HN
Print view View original

31–40 of 135 posts

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#31

Post by manigandham »

mmcclure wrote: post #30
manigandham wrote: post #10

I prefer https://tachyons.io/ as a CSS framework that avoids any pre-styled themes and just provides building blocks. Great for SPA/component UIs.

I really do hate to be the guy this guy, but after having to maintain a website a contractor built in Tachyons, I've hated it with a passion of [insert hyperbolic phrase here]. What do you love about it/what am I missing? For me it felt like a tutorial on the most egregious CSS/dom anti-patterns, and I haven't been able to get past it.

The patterns are easy to learn (for me) and makes building components very quick while still being very customizable without having to add a whole bunch of one-off styles. And everything is still standardized.

It also removes the need to constantly reference CSS at all, and can just stick to HTML/JSX instead. It can get very verbose though, but that's a minor trade-off I think.

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#32

Post by ndnxhs »

osdiab wrote: post #23

The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…

From what I understand CSS frameworks used to make web dev more bareable because you could just use a simple class name and the framework would apply a load of hacks to get something sensible that works in all browsers.

Bootstrap always seemed like a polyfil for flexbox.

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#33

Post by mfrye0 »

osdiab wrote: post #23

The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…

I've done frontend for quite awhile. I usually start with some sort of framework for every project and use only the minimal pieces for the foundation.

Generally you need the same stuff for every site:

  - reset/normalize the styling cross browser
  - basic grid system
  - typography, forms, and buttons
  - "componentized" files with variables (sass, less, post css, etc)
Basically I start with a custom build of whatever framework, use that to build the MVP, then customize it according to the designer requirements. Lastly, I'll pull in components as I need them.

Why reinvent the wheel and start from scratch?

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#34

Post by cssss »

tomcam wrote: post #13
matchbok wrote: post #3

I'm just gonna say it. We don't need another "lightweight, responsive, modern" CSS framework. It's a solved problem.

I like fast, small web pages because not everyone has a broadband connection at all times. Can you tell me what other mature, tested, well-supported CSS frameworks have a feature set that large in less than 25% of Bootstrap's size?

There are lots of them:

https://github.com/troxler/awesome-css-frameworks

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#35

Post by evolve2k »

thestepafter wrote: post #24
pixard wrote: post #15

Earlier quoted context omitted.

Anyone interested in this approach may also like Tailwind https://tailwindcss.com/

Tailwind is absolutely fantastic. I can code CSS 2-3 times faster and I no longer hate doing it.

How do we classify the progression that is tachyons/tailwind? Each time I see a new CSS framework I also think, is this yet another framework for devs that can’t desigh or is someone working to move the needle beyond what tachyons/tailwind have set a new place of maintainable CSS.

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#38

Post by dmitriid »

matchbok wrote: post #3

I'm just gonna say it. We don't need another "lightweight, responsive, modern" CSS framework. It's a solved problem.

In which way is it solved?

It takes insanely hard work to pull off a consistent cross-component design in CSS.

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#39

Post by chvid »

osdiab wrote: post #23

The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…

I have come to believe the same.

Plus I have seen really complex and unfruitful css when a project starts customizing and extending ie Bootstrap.

Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework

#40

Post by ryannevius »

mfrye0 wrote: post #33
osdiab wrote: post #23

The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…

I've done frontend for quite awhile. I usually start with some sort of framework for every project and use only the minimal pieces for the foundation. Generally you need the same stuff for every site: - reset/normalize the styling cross browser - basic grid system - typography, forms, and buttons - "componentized" files with variables (sass, less, post css, etc) Basically I start with a custom build of whatever frame…

But is that grid system consistent across different sites? In my experience, I usually need to customize the "grid" to specific breakpoints and widths, as defined by designs/content. I find that it's often faster to just write a few helper classes for layout – specific to the site I'm working on – rather than use 15% of a framework's grid and still do heavy lifting. Of course, this isn't the case if the design team designs with a framework's grid system/breakpoints in mind.
Post reply on HN