prestige VS Sass

I've not used it, but have heard of Prestige (https://github.com/sharat87/prestige). It bills itself as "A text-based HTTP client in the browser. An interface-less Postman." I hope that helps!

9. prestige

Shameless plug: There's also Prestige at https://prestigemad.com, which is very similar but works right in the browser. You can save your files as Gists as well. Templating with variables is also supported with `${}` syntax, like Javascript's template strings.

But gRPC support is not built yet. It's on the roadmap.

There's also https://prestigemad.com, a text based API testing tool, like Postman. I'm the developer behind it and is open source at https://github.com/sharat87/prestige.

Login not required!

Hey! I did the same thing, rewrite httpbin in Go, and put it up on https://httpbun.com. I did it because I needed a fast endpoint like httpbin, with a few extras, and with working redirect endpoints. I needed this for testing Prestige. (Sorry for inserting a shameless plug in here, but httpbun and httphub are just so close to each other I couldn't shut up 🙈).

Still early days at https://prestigemad.com (recently discussed at https://news.ycombinator.com/item?id=27412445)

- Backend is a Django project, database is PostgreSQL.

- Frontend powered by Mithril.js and the editor by CodeMirror.

- Hosted on a $5 box on EC2.

- GoatCounter for analytics.

- CloudFlare for DNS, NameCheap for domain.

Also https://httpbun.com

- Backend is a vanilla Go project.

- Frontend is plain HTML and CSS, I don't recall it having any JS at all.

- Hosted on the same $5 box on EC2.

- No analytics (yet).

- CloudFlare for DNS, NameCheap for domain.

It is refreshing to see how much I can squeeze out of a $5 box. I don't intend to stay with EC2 for long, but when its cheap, I'd rather spend my time improving Prestige.

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.