HN user

fc373745

256 karma
Posts0
Comments54
View on HN
No posts found.

I completely disagree.

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.

    absolute inset-0 bg-gradient-to-r from-cyan-400 to-sky-500 shadow-lg transform -skew-y-6 sm:skew-y-0 sm:-rotate-6 sm:rounded-3xl

    position: absolute;
    top: 0;
    left: 0;
    right: 0;
    bottom: 0;
    linear-gradient(45deg, #fff, #000);
    box-shadow: 1px 1px 1px 0 rgb(0 0 0 / 0.05);
    transform: skewY(60deg);
    border-radius: 4px;
    transform: rotate(60deg);
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.

Agnostic.

There could be a creator out there that never made itself known to us.

Also, my experiences with Sleep Paralysis makes me feel like something is out there.

I went from a devout Christian (7th day adventist) for 20 years of my life -> to atheist -> to agnostic.

Democracy doesn't work.

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.

Almost evil.

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.

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.

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?

to be honest, that's pretty tame as far as dark patterns go.

If a user had already typed their email onto the field, then the user had at least some intent to sign up whatever the user wanted to sign up for.

This makes what ad trackers and ISPs do with how we browse seem like war crimes if you were to call this a 'dark pattern'

Why not make the goal bigger? Bigger to the point where we can see double digit scoring?

One thing that turned me off from watching Soccer one year was the amount of 1-1 games that led to PKs, and after just doing a little bit of research, Hockey has the longest overtime games by far, and occurs more often by far.

The average NHL team has gone to overtime in about 23.1 percent of its games over the past three seasons. The Flyers have done so in about 31.1 percent of their games

It's not enjoyable for the casual viewer. Betting on sports which have O/U of 0.5, 1, 1.5 is ridiculous tbh.

Unfortunately, i don't think anyone is that dim to conclude that the accusations against the Chinese government is out of pure empathy for the Chinese people.

If it was the case that your empathy stretches across the pacific ocean for the Uighurs, then why does it not stretch for the Palestinians? I think the actions taken by Israel is way worse of a human rights violation than China is doing, but because the West supports Israel, it turns a blind eye against the Palestinians?

Moreover, one can formulate and theoretically, yes accusations should not equivocate as hatred for the Chinese.

But in practice, this isn't true at all.

I'm curious why you consider animations to be nuisance. Game UIs are completely riddled with animations that you have to "wait for" and yet I feel like UI design should aim towards that direction.

However, sports can differ in what they are in need of when it comes to traits and skills, and like you pointed out, many would negligently exclude that intelligence can also be a factor.

Take American Football - the running back and wide receiver position will ask for almost exclusively physical traits. Players like DK Metcalf fits his position so well almost solely based on his physical performance and players in these positions are predominately Black. However, the Quarterback asks less of the physical and more on decision making, and players in these positions are predominately White.

I believe it to be a mixture of both, although physicality and athleticism takes a lion share of what factors are needed to be successful in sports, whereas intelligence is required in selected sports.

As you mentioned, Michael Phelps has an physical anomaly where he has the legs of someone with a height of 5'10 and the torso of someone who is 6'7, which is what propelled him to become to greatest - but to your point, swimming does not ask much for the mental. Maybe reaction time for starts, and strategies for 400im and anything longer than 400m freestyle, but doesn't ask for much compared to other sports out there.

to play the devil's advocate -

these differences across racial lines are not an inhibitor for Black Americans to compete at high levels in sports.

Lord knows how much more staggering the difference could be if all Black Americans actually grew up with good nutrition, education, and training. I mean, the NBA is already 75% African American.

What if it is the case, that all of things you mentioned, and more were provided to lessen the disparity, and yet it still came out as predominately one or two races?

also, to add another point.

Most API teams will give you all the resources that you need.

It is most likely the case that the FE team will ask not for more, but rather, for less.

This was the exact problem why GraphQl was created in the first place - to account for Facebook's mobile platform, because they were receiving way too much data that needed to be trimmed because they didn't want to be sending like 500kb of json over mobile networks.

Competent API teams will give you all the resources that you need to be productive as a FE engineer, and if it is the case that your data needs some trimming, then go ahead and ask your decoupled backend team, while you can go ahead and keep working asynchronously while they get that done for you.

Not Fatal as you think it is.

it's just a hit to the db.

Graphql works the same way if i'm not mistaken.

and if its the case that you don't want the comments at all, then in the conditionals write your sql statements

if you want comments

select * from resource where id=some resource id

if you don't

select without comments from resource where id=some resource id

there's no need to get into specifics, the point is graphql is not bringing anything novel. everything it claims to do can be implemented in RESt if you're willing to implement it.

Unfortunately for graphql, the claim that backend teams need to be constantly making endpoints for other decoupled teams is not as drastic and critical as you consider it to be.

Dare i even say switching to graphql and onboarding developers to graphql is a much more resource intensive process than adding another endpoint (or a couple).