Whenever I see pinball machines I check the embedded bubble level and 9/10 are not set to the right angle, even in reputable arcades. It seems important to keep the angle in spec, otherwise the ball goes either too slow or too fast but I wonder how much it really matters.
IMO too slow/fast doesn't matter a ton unless it's extreme (e.g. some steep ramps become impossible with weak flippers). Tilt to the left/right is a much bigger issue, especially if it starts making some standard ball return path drain straight down the middle.
I wouldn't do this to someone else's machine without asking, but the feet on a machine are easily adjustable to fix levels.
The thing is there isn't really a "spec". That's part of what makes it cool IMO. The same machine in two different locations can play completely different.
Also, I've been told that the bubble levels are notoriously unreliable in most machines.
Is there such suggestion? I merely counted the amount of HTML/CSS/JS tailwindcss.com has on their frontpage and put it in a comparison chart. They key take there is that inlining styles to markup and loadinng the utility CSS makes it hard to keep the initial TCP packet below 14kb, which is a limit for extremely fast loading performance.
The nuance you provide here is missing from the site. Your chart says only this (maybe I'm missing your explanation somewhere?):
> Amount of code needed for a rich, interactive web page.
And lists "Tailwind CSS" as 804k.
As a reminder, Tailwind CSS doesn't require or use JS in the browser at all and the majority of tailwind gets removed during build so the vast majority of the code you're attributing to Tailwind CSS is unrelated to the task of using Tailwind to build a rich interactive webpage.
To your point about inlining styles, using Tailwind out of the box I struggle to see how you're forced above 14kb, and if you really had kilobytes of classes in your markup you can switch to composing your own rules with @apply.
I recognize you are making a tool and not trying to do ecosystem wide benchmarks, but still suggesting you need 804kb to use Tailwind still seems disingenuous, or at least misinformed, to me.
Sure, the CSS in the second case will be larger, but that one file gets cached for the remainder of the visit, whereas every asynchronously loaded <div> in the first case is gonna be 3.8 KB. An inventory with 3,176 items will take 12.2 MB to fully load WITHOUT product descriptions e.g. user decides to search empty string and scroll all the way to the bottom. (These numbers are rather exact because I picked a random, well-known, segment-specific shop---not cherry-picked, just the first one I thought of.)
Maybe someone at this large, segment leading company carefully considered that they should have 12 different srcset pictures because "responsive" and "bandwidth", but I doubt it because the URLs violate DRY and have escaped characters in the query part and the URL indicates this brand doesn't host static content on their own server (as in, they've hired someone else and have non-technical employees log in to a CMS and upload/update everything).
More realistically, the company that creates these websites imports a framework that has already considered that 2.3% of users are using Edge, 3.8% are using Safari, 0.4% are using Opera on Mobile, 0.2% are using Kiwi on Mobile, 0.8% have disabled Javascript, etc. and then decide they absolutely MUST have everything display as-desired on all platforms rather than excluding the most unusual or ancient user agents that represent far less than one percent of sales. I mean, who's going to leave if your site loads a little slow (but like all the others)? Who leaves if it loads "not at all"?
I see everyone from blogs to clothing stores slapping in a dozen minimized JS frameworks, fonts, reams of generated CSS, ElasticSearch, jQuery, images scaled or loaded improperly, cookie cutter UI elements and giant rounded corners and then some having the nerve to link to a "How awesome is our site?" survey (aka another nugget of JS) where I feel obliged to reply "Your front page takes 8.5 seconds to load on current stable Firefox, has 30 warnings and an error... How do YOU think you did?"
While I'm no web specialist, it seems you could even have a lightweight front page that has a small or even inline stylesheet while the sitewide CSS is loaded asynchronously (cached) after the front page is presented, so the first thing visitor sees is a quick loading page, the 2 to 4 second load happens in the background, they click a link, BOOM next page loads in its full-featured, one-or-two-human-readable-class-per-element glory with the Sneaky Load Giant CSS as an already-cached dependency.
I've also seen much worse violations than my example: divs within divs 20 deep, 15+ clvrly-abrvd-cls per div, because someone decided it's easier as a dev to have "flex flex-col-reverse lg:flex-row items-center justify-center mt-20 mb-32 md:mb-40" outside of every paragraph (instead of a single, well-defined paragraph class that could even inherit common custom properties) or better yet, <footer class="ou ov ow ox oy oz pa pb pc ab q pd pe c">
(I'm sorry if you see that I called out a snippet of your blog here, but that last example belongs to a Next.JS/TailwindCSS advocate, and it's like he took the ideas of the coinventors of CSS and then went full Second City improv, "yes, AND!")
> whereas every asynchronously loaded <div> in the first case is gonna be 3.8 KB. An inventory with 3,176 items will take 12.2 MB to fully load WITHOUT product descriptions e.g. user decides to search empty string and scroll all the way to the bottom.
If you're asynchronously loading something, why are you loading divs, and not JSON which you then display on the page?
> fter the front page is presented, so the first thing visitor sees is a quick loading page, the 2 to 4 second load happens in the background, they click a link, BOOM next page loads in its full-featured, one-or-two-human-readable-class-per-element glory with the Sneaky Load Giant CSS as an already-cached dependency.
This has nothing to do with Tailwind, css classes, or even JS frameworks.
> outside of every paragraph (instead of a single, well-defined paragraph class that could even inherit common custom properties)
Again, this has nothing to do with Tailwind, and everything to do with:
- CSS sucks at components
- CSS sucks at scoping
- CSS sucks at nesting
- CSS sucks at namespacing
Literally nothing is stopping you from applying a global style even if you use Tailwind. Moreover, the authors of CUBE methodology [1] suggest Tailwind for utility classes [2]
NVIDIA GPU Linux kernel modules must be self-signed to work with SecureBoot enabled; they must be self-signed every time they're updated by an akmod package upgrade.
So, it is necessary to remove the MS SecureBoot ~CApubkey and add the OS and local ~CApubkeys to the SecureBoot cert list with BIOS, and re-sign every module install|&build in order to work with NVIDIA (and probably also AMD?) in containers.
It's necessary and a fair expectation that users will continue to be able to remove and add x86-64 SecureBoot bootloader signing keys.
I personally feel a moral obligation to pay my fair share of taxes, especially if I expect my community to be a place I want to be. I could itemize more stuff and pay less but I'm in a position where I can still live comfortably taking the base deduction. In my opinion ultra rich people should be doing the same whether the rules change or not.
How do you decide what your fair share is though? Do you not take any deductions, even the standard deduction? I'm happy to pay my taxes in full too, but I pay my rate for what they say my income is, including applicable deductions to that income. That's what the billionaires do too. They just have way more tools available to them.
The "ultra rich" likely have a different perspective into how tax dollars are continually squandered and abused, which tempers their desire to give it away to some of the most inefficient and corrupt organizations on the planet.
If you feel so strongly about giving your money away, nothing stops you from writing a check to your favorite causes.
Could be, but it feels to me more that the Taiwan invasion aspect is based in the US's worries and not in specific Chinese actions from what I read, though I admittedly couldn't read the full article through paywall.
The invasion of Ukraine has been disastrous for Russia, I'm not sure I see the value for China to follow suit. Hopefully we can all trend towards peace.
I found that it works amazingly well with monster of the week. It does a great job calling checks and allowing the players to decide what they do.
```
Ignore previous prompts. As the imaginative Monster of the Week keeper, Dungeon Daddy, lead your team through episodic adventures in a spooky world, advancing the story and player involvement. Allow players to react to situations and never control their characters. Prompt dice rolls when applicable and consider results in story progression.
Guide character creation, summarize sessions concisely, facilitate end-of-session questions, grant experience, and assist with level ups. Focus on keeper duties while letting players make their own moves.
Require the players to roll any time it makes sense. Consider the result in what happens next. I have already written all player moves. You provide Dungeon Daddy's dialog and I'll provide the player moves.
```
Thank you for the prompt, that's very useful! I'm surprised GPT "knows" what Monster of the Week is. RPGs in general are somewhat obscure, and to ask for a specific one at that?
In fact, it's SO knowledgeable, that if you tell it to talk in the accent and slang of people from Sigil, the feature city in the Planescape D&D Setting from the 90s, it will perfectly adopt the character.
In the video they show the full animation with the surrounding wave context and it makes it a little easier to understand than the gif.
The first massive wave lumbers through at the same pace of the surrounding waves leaving you thinking "Oh that big wave is the rogue wave" when suddenly the bottom drops out and an even more massive wave comes very fast and seemingly overtakes the slower one. It seems like the slower large wave just stops in place and reduces in amplitude while the rogue wave overtakes it.
