> The basic algorithm divides points by a power of the time since a story was submitted. Comments in threads are ranked the same way.
> Other factors affecting rank include user flags, anti-abuse software, software which demotes overheated discussions, account or site weighting, and moderator action.
So if a story gets points very quickly, it will appear on the front page. If it don't keep getting points it will disappear.
That disclaimer is shown for exactly 1.5 seconds, or 38 frames, mostly as white text against a white background. Yes, I downloaded and checked as I'm that sad type of person :-) No one can notice the text is there and read it that fast, so for all practical purposes it might as well not be there.
It always disappoints me regulators just let this kind of faux-disclaimer slide. This is just lying with your fingers crossed behind your back.
The fact that drug makers can hawk pills on TV telling you how much you need glockinflexadusal or whatever schizophrenic word-salad name they've come up with for your sporadic knee twinge and show you how you can be young and beautiful and imminently desirable again
(sometimes people who take this pill start pooping and never stop pooping again for the rest of their lives which are thankfully rather short, and on a few occasions people have immediately burst into flames and started screaming in pain but their bodies refuse to die for some reason)
You should ask your doctor if girexamusib is right for you. *images of children wearing white clothing and running through wheat fields and blowing dandelion puff seeds into a beautiful sunset play while the tranquil music of heavens elevator plays softly in the background*
is incredibly terrible for all of the worst reasons.
I don't see any issues with this particular code (although for larger sizes, there may be an accessibility issue related to zooming). In general, I would recommend avoiding the use of vw-only units because the computed value may not change with zoom.
I would only use this kind of thing on the root element, then size all other elements relative to the root element e.g. h1 { font-size: 1.5rem; }. It's more manageable that way IMHO.
I really like CSS, and in my personal projects I don't use Tailwind.
However, I use it in my day job, and here it is useful to us as a team. The variables combined with the tooling ensures we write consistent styles across our site. The color names and text sizes also correspond to what our design team uses in Figma, making implementing and updating designs quick.
That said, I still find it a pain to read, and we could probably have set up something very similar with CSS Custom Properties.
You could import your favourite design framework (say, bootstrap) as SCSS, change its variables to suit your design, and create any custom components using @extend:
Looks great and works great! A reset button would be nice to undo the horrible mess I made.
A minor note, when I load the page I get console warnings about an Audio Context being prevented from starting automatically, but once I click play everything works perfectly fine.
The audio context thing where it won’t start without user interaction is by webaudio API design. OP would need to prevent the errors from coming up though.
If you're willing to go a bit further, i recommend adding a "groove" cursor, that slightly shift each box within the beat, at random (then you can have more complex algorithm to make the randomisation move the beat toward a ternary rythm instead of completely at random). It's called "humanize" in some audio software and can be fun (if you feel like putting one cursor per track, that's even better).
No, I have HTML and CSS in the same component file. I prefer having styling in one place (the CSS inside the component file) rather than two (the HTML of the component and tailwinds’s own postcss files that implement the styles).
Standardised and clean CSS syntax. The benefits in that context are debatable, a component based frontend architecture is where it absolutely shines. If you end up using it in that context you won't need to ask this question, it quickly becomes clear that it's the optimal path.
What can't pure CSS do here and that Tailwind does ? The CSS syntax is already clean and standardized if you use it properly and don't name every little piece of interface. It is a genuine question, by the way...
I imagine you have done extensive research on your own, but in any case I found this article by Josh Comeau on coding with voice commands and eye tracking very interesting: https://www.joshwcomeau.com/blog/hands-free-coding/
> How are stories ranked?
> The basic algorithm divides points by a power of the time since a story was submitted. Comments in threads are ranked the same way.
> Other factors affecting rank include user flags, anti-abuse software, software which demotes overheated discussions, account or site weighting, and moderator action.
So if a story gets points very quickly, it will appear on the front page. If it don't keep getting points it will disappear.