To fix the css + jsx in one file, just write your styled components at the bottom of your component.
If you ever seen a react component completely riddled with Tailwind, you'll realize how messy and uncoordinated it looks.
Even I would consider switching between two files just to avoid that style of css.
Furthermore the necessity to utilize horizontal scroll because adding 10+ more rules will inevitably break your prettier printWidth rule is, by far, the most annoying aspect of Tailwind.
Consider these two snippets, after time of not looking at your css code, do you think 10+ rules on one line is maintainable?
Not even close, ask yourself to change a css property - you would have to iteratively go from left to right until you find it, whereas looking from top down you can immediately catch the css rule you want to find.
Succinct doesn't mean maintainable, and sometimes verbosity does.
Even the United States isn't genuinely democratic as most representative hold stock in various companies.
The best way to influence congress in the United States is to lobby, not vote.
And even in the ways that democracy works in the United States, most issues are in a deadlock position.
How long has the United States argued over abortion? the past, what, half century?
And we still go back and forth.
The United States is crumbling right now due to this deadlock with each party looking to overturn the changes that the previous leadership has overturned and so on and so forth.
Democracy is dying.
My ignorance is not as valuable as your knowledge, but this is precisely what democracy implies.
This isn't to say I advocate for Authoritarian governments either, but they do get rid of the levels of bureaucracy and levels of administration to administer changes, whereas in an authoritarian government is way more efficient to deal with changes.
I'd advocate for a benevolent authoritarian, but it doesn't mean that the successor, or the next, won't be a complete asshole, which is why authoritarian is dangerous.
However, the form of government that I would truly advocate for is a meritocratic oligarchy where the few would have absolute rule, but deserve to have that absolute rule in the sense they are benevolent, just, but wise and efficient at the same time.
Democracy is dying. I have absolutely no hope for this deadlock and polarization between the the factions of the United States, especially when most representatives are sellouts to corporations.
as I take a look at some of the comments in the threads about China, I wish you were more consistent with your stance, especially with comments on the opposite side of the spectrum.
Hacker News was supposed to be niche, but your inconsistency to demote threads of China (as they are consisntely upvoted), is now making Hacker News very generic.
You can ban me, I spend much more time reading than I do posting anyways.
But I know where Hacker news stands with their ulterior motives in doing so.
There was a period of time where bitcoin was almost exclusively used for illegal substances / activity - predominately for drugs (the only time I ever used bitcoin was to buy adderall on silkroad), but also for things like hiring hitmen, weapons, and child pornography.
To see cryptocurrency grow to what it is today, especially given the context of what it originally was used for is a bit demoralizing.
if you read the article you would know that the majority of the homeless population in nyc are sheltered as a 1979 class action lawsuit found that it was a constitutional right for the homeless to be sheltered.
personally I found gql to have a steeper learning curve in that it adds an abstract layer to the stack.
I call it an abstract layer, the author calls it a BFF (backend for the frontend).
As far as dev time excluding onboarding time, lets not forget why gql was created - facebook wanted to separate the data responses to their mobile and web platform
first of all, not all organizations are facebook
secondly, especially for smaller to medium sized startups, not all responses need to be separated, and "shaving" off data for an extra endpoint is not difficult in REST.
and I remember graphql's early website where they made the claim saying that you'll need to have some really huge number of endpoints in order to emulate what graphql has to offer, and since then they have taken that down because of how ridiculous that sounded.
In reality and practice, the number of endpoints that you need to "shave", again, especially for small to medium startups, is slim to none.
sure, I can accept that definition of latency.
However, the author, when describing latency, only specified the distance traveled to justify a graphql server without implicating anything else.
Performance isn't just latency - it's also about the requests and responses per second a service can handle.
GQL notoriously performs weaker to REST in this regard.
>When a user navigates to a page on a web app or deep links into a Single Page Application (SPA) or a particular view in a mobile app, the frontend application needs to call the backend service to fetch the data needed to render the view. With RESTful APIs, it is unlikely that a single call will be able to get all the data. Typically, one call is made, then the frontend code iterates through the results of that call and makes more API calls per result item to get all the data needed.
>For example, I don’t want to navigate through multiple screens to review my travel itinerary; I want to see the summary (including flights, car rental, and hotel reservation) all on one screen before I commit to making the purchase.
I disagree.
Sure, sometimes more than one restful call is made for just one page, but the example given, when architectured properly is just a user foreign key relationship to all its children (reservations flights, rentals, etc), which is just a single sql query.
I don't think the author really understand the flexibility of REST and how much it can emulate what GQL has to offer.
If you want specificity in your query fetching, just add query params or put them in the request body
And if it is the case that you really do need resources from different endpoints, what is preventing you to build that single endpoint in REST?
>the leak was intended to “foster more disruption and competition in the online video streaming space” because “their community is a disgusting toxic cesspool”.
To fix the css + jsx in one file, just write your styled components at the bottom of your component.
If you ever seen a react component completely riddled with Tailwind, you'll realize how messy and uncoordinated it looks.
Even I would consider switching between two files just to avoid that style of css.
Furthermore the necessity to utilize horizontal scroll because adding 10+ more rules will inevitably break your prettier printWidth rule is, by far, the most annoying aspect of Tailwind.
Consider these two snippets, after time of not looking at your css code, do you think 10+ rules on one line is maintainable?
Not even close, ask yourself to change a css property - you would have to iteratively go from left to right until you find it, whereas looking from top down you can immediately catch the css rule you want to find.
Succinct doesn't mean maintainable, and sometimes verbosity does.
Tailwindcss isn't even close to being the future.