Right, but those capabilities are available to you as well. Granted the remediation effort will take longer but...you're going to do that for any existing issues _anyway_ right?
I understand why this is a tempting thing to do in a "STOP THE PRESSES" manner where you take a breather and fix any existing issues that snuck through. I don't yet understand why when you reach steady-state, you wouldn't rely on the same tooling in a proactive manner to prevent issues from being shipped.
And if you say "yeah, that's obv the plan," well then I don't understand what going closed-source _now_ actually accomplishes with the horses already out of the barn.
The mental model I had of this was actually on the paragraph or page level, rather than words like the post demos. I think it'd be really interesting if you're reading a take on a concept in one book and you can immediately fan-out and either read different ways of presenting the same information/argument, or counters to it.
Listen I'm not a crazy huge fan of a lot of new tech, but this is pretty transformational. When reading the first article [1] I was struck by the fact that it granted so much new freedom to your "social identity" on the internet. The comparison to hosting providers was incredible, because imagine you building a website and posting your thoughts there or starting a business there...and then immediately being shut down and all your data lost because of some arbitrary change of policy at your "host".
Everyone always talks about how your Google account being tied to logins is scary because you can get arbitrarily locked out. This protocol makes something like functionally impossible since /you/ control your data.
US Army veterans do have a higher rate of arthritis but their days are quite different from the "run 3-5 days a week" that most people think of when talking about recreational runners.
And the pacemaker comment stood out so I did a bit of digging and found a study [1] you might be referring to. Again, the effects were strong only in the heavy-duty-exercisers/pro/semi-pro cross-country skiier group. Additionally, this didn't offset the gains to cardiovascular or mortality risk - that group was still "healthier."
You’re right - if you only used it for ‘font-heading-2’, you wouldn’t need it.
But like the person you’re responding to said, the ergonomics improve for the majority of cases that are just
‘flex items-center gap-2’.
And yes, you could write it all yourself but Tailwind is a good set of defaults for those classes and minimizes bike-shedding and improves consistency. These are useful things in lots of teams.
I don’t really use Tailwind on smaller personal projects because I love CSS, but in an org of mixed skill levels, it’s pretty damn useful.
(Also, Tailwind uses CSS variables. It had solid support for them in the last major and first class support for it in the current one.)
Hey, I'm an engineering manager at Join. We build collaboration tools for huge construction projects: think stadiums, hospitals, research facilities, etc. Our customers (GCs) love us and their customers (owners) love us so we're getting cool network effects out of that.
I'm looking for a senior/staff Golang/DB developer who has a bunch of tools in their belt, knows their tradeoffs, and /wants/ to share their knowledge with midlevels and help them avoid some of the scars you've accumulated over the years. :)
This was one of the biggest "oh shit" moments I had when learning Remix: I could reuse the same validators across front and backend and they could even be right there in the same file.
> Actually it would sort of be nice if these frameworks could be coded such that if I have JavaScript shut off, it just runs the code elsewhere and sends me the site.
Remix does!
Actually, most (all?) of the major frameworks will do SSR on pageload and only use client-side rendering for re-renders. But yeah, Remix will do exactly what you're asking for and force you to do full-page refreshes without JS. If that's what you really want.
Reading the code is a joy. I love seeing different approaches to what we all take as givens, such as design.css rather than style.css, or the usage of an `else if (1 == 1)` compared to `else` or even `else if (true)`.
(So I guess, thanks for not teaching her about bundlers and minifiers yet :))
In the article, one of the lawyers quoted states that "enforced compliance is the hallmark feature of any cartel."
Is that part of the legal requirements for a guilty judgement or breaking up a cartel? In the US at least? Would RealPage be fine if they treat their recommended prices as mere suggestions?
> Using this "cross-verified database," we find that music stars have one of the shortest lifespans of any profession, with an expectancy comparable to boxers, military figures, and race car drivers.
Although according to the chart directly below, the life expectancy is more comparable to chess players and poets. Probably isn't as fun a sentence to write though.
IIRC (I read this study a few weeks ago), they compared areas where a Starbucks opened; areas where Starbucks planned an expansion but were prevented by things like city planning snafus; and areas where Starbucks opened in non-traditional (eg low income) areas through their partnership with Magic Johnson.
From your snippet I was wondering whether he was butchering the concept that pessimism is suffering twice (both in anticipation and when your pessimism is confirmed) whereas optimism is only suffering once.
But the context of Elon's tweet actually makes more sense than I was expecting from a tweet from Elon. If everyone's pessimistic about the future and doesn't even try then we'll never accomplish anything.
There's nuance to this topic - we shouldn't strip it out.
I understand why this is a tempting thing to do in a "STOP THE PRESSES" manner where you take a breather and fix any existing issues that snuck through. I don't yet understand why when you reach steady-state, you wouldn't rely on the same tooling in a proactive manner to prevent issues from being shipped.
And if you say "yeah, that's obv the plan," well then I don't understand what going closed-source _now_ actually accomplishes with the horses already out of the barn.