You've moved the goal posts. Nobody said an input levels indicator isn't useful. We're talking about this specific graphic not being a useful graphic for visualizing live data. You've wandered away from the pack here
The heart of the issue isn't that animating height is expensive, it's the downstream effect of that animation repeatedly changing the page's layout and forcing redraws.
Been using Tailwind since starting my job 5 years ago where we have a ton of webapps standardized on Angular+Tailwind, and you may have to hop into a webapp you've never heard of before to fix a bug. Couldn't be happier with how much easier it is to build and maintain compared to traditional CSS.
Many many words I've read trying to convince me why I shouldn't be having a good time using it, yet here I am more productive than ever thanks to it. Less experienced devs are by default funnelled into writing code that's easy to understand, only looking at one file, as opposed to people trying to do cute tricks where styles could be coming from anywhere in the project. It's SO much easier when the styles are on the component I'm looking at and I don't have to cross-reference between files. Plus people sticking to increments of 0.25rem instead of everyone using their own preferred units is huge.
When you work at a big company you can't expect everyone will write nice CSS. But Tailwind plays a huge part in making sure everyone writes something that's much more easier for the next person who has to read it.
You'd also be more productive and have less unknowns and potentially less decision paralysis if, say, everyone started using excel hooked up to a database instead of writing their own bespoke CRUD app, but alas, those aren't the reasons one asks programmers to program.
I echo this. For all the supposedly bad things it is, Tailwind provides a level of common denominator in a big team still making sure the CSS at the basic level is nice.
It doesn't even require a big team to be useful—I won't remember how I organized a set of styles a few months from now, and having Tailwind require a minimal set of constraints, and keeping the styles easily editable in the place you use them makes things more maintainable over time.
i appreciate the OP's take and insight but couldn't agree more with this comment.
> yet here I am more productive than ever thanks to it.
i have first hand experience with most of the css frameworks. heck, even wrote a custom scss one at one point, but eventually there's a simplicity (admittedly to a fault at times) to tailwind that just makes you more productive.
> Plus people sticking to increments of 0.25rem ins
this is another really good point that doesn't come through as much. Tailwind also does a fantastic job of picking the right defaults which 90% of the internet won't do.
from the OP's original piece
>> it demands the developer who installs it set up a config file that lays out all codebase-wide style constants: colors, margin sizes, fonts, border radii, etc.
... or importantly, it sets up a solid set of defaults.
On my list of concerns for big tech abusing power, the ad company with the browser monopoly leveraging their position to essentially end ad blocking on the web by disabling it on the browser people are using in practice is very high on the list, and I would have been fine waiting on forcing Apple to let you uninstall the camera app, or switching the iPhone to USB-C if it could have prevented this. This didn't come out of nowhere, we've known about manifest v3 for years now.
In fact Google's browser monopoly only looks like it's gonna get further cemented as Apple is forced to allow other browser engines, which is the only thing keeping any sort of competition against Chrome.
I feel like the anti-Apple snark that's been so popular since around the late 2000s (and I took part in in my angsty teen years) has been affecting the priority of what's being dealt with from regulators and it annoys me.
As an iOS and web user, it is my desire that Apple doesn't allow other browser engines because immediately Google and other web devs will start pushing webapps that only work with mobile Chrome and we'll all be forced to install a Chromium browser to use certain websites, it becomes default and users will think "Safari sucks now, a bunch of websites don't work with it," finally ending Google's last bit of real competition in the browser space: Safari with its terrifying 17% marketshare.
That's not even getting into the resources/battery life aspect.
As a web dev, I happen to love some of the tech advancements in Chromium, and as a nerd, I'd be thrilled to see it on iOS, just for the fun technical novelty of it all. But allowing it on iOS will downright kill WebKit, as web devs will just code for Chrome (as they already do). The floodgates will be opened.
As a user, I value battery life, smooth performance, and system integration (technically and visually). It's great to use an Apple browser on an Apple OS, just as it is nice to use Chrome on Android—everything fits together.
Gosh, I miss the pre-Blink days when WebKit was able to benefit from Chromium, but alas…
So to protect an artificially inflated browser engine you're willing to remove user choice and freedom to prevent a competitor from doing well? Microsoft was learned this was illegal many years ago. When the US government went after monopolies and didn't cosign them.
A lot of serious engineers would love to work in an environment that isn't the HR-reigning office politics bullshit standard of the past decade or two.
I don't even really like Elon but I bet the engineers at X are having a better time in their day-to-day than the ones at Meta or Google where all their work is constantly roadblocked by red tape, in-fighting, and PMs whose only goal is to make it look like they headed something important to get themselves promoted. Elon's at least got a vision and keeps it a top priority to be competitive in the AI space.
> Its absolutely bllsht these companies can effect us in this way.
I'd be one of the last people to defend Instagram/Meta/Zuck, but is that really your takeaway from this? Execution videos are absolutely against Instagram's TOS and I'm sure they want it on their platform even less than you.
If anything, Instagram's issue is they're too heavy on the robo-censorship. My friend posted a photo of him standing on one leg with a chair in his hands, making a goofy face, with the caption "I'm gonna hit you with this chair!" directed at no one in particular, and it was taken down for, quote: "encouraging violence and leading to risk of physical harm, or a direct threat to public safety." Appeal was rejected too, and the post had to be deleted.
This happens because they're trying to moderate against people posting execution videos. One slipped through the cracks seemingly, but it's not like they don't put a lot of effort into preventing that. It's pretty hard to do at Meta's scale where most of the earth's population is using their platforms.
Moderation has basically gone away... Don't you think there's a extra bit of ML that goes into the first reel I'm seeing after not opening the app for 10 hours also? I'm making assumptions here, but this was the first reel. These videos have thousands of likes.
Yep. Just see YouTube comment sections with clear pornographic images in certain users' profiles–accounts which have existed for enough time for the dumbest of moderation campaigns to have identified as inappropriate.
The take-away is that not that they are poorly moderated (which is true).
The point is that these short-form videos deliver no actual value to those consuming them but come with plenty of mental health downsides. (Literal PTSD, for starters.)
The ML moderation false positives/negatives do not annoy me as much as the slot machine design of reels/tiktoks/shorts. I do think the constraints of the medium's design (very short, random, visual, crowd-controlled) create perverse incentives.
That is not at all representative of how the original code would have looked like. At all.
I am tired of people assigning pseudo-magical properties to "decompilations" while at the same doublethinking them as a way to launder copyrighted works.
Yeah looking at that is what prompted this question. Are the events in order? If so: the index for an event in the bitmap is constant, so if you realize you need to save an event that wasn't previously being saved, how do you insert it to keep order? Do you break all previously saved data by changing all the following indexes? Or are the events not in order, which could make it harder to find if an event is already in it (and just generally be confusing)? Managing a long list of events like this given that it is used for persistent state seems like an interesting process challenge.
