HN user

bsuvc

2,218 karma
Posts0
Comments311
View on HN
No posts found.

loading a cross repo issue is a much slower experience

Why not solve the real problem instead of putting in a janky workaround?

At risk of being cliche, it seems like you guys could benefit from the 5 Whys approach here: "Why is loading a cross repo issue slow?" and iterate until you discover the root cause, and fix that.

I suspect fixing the root cause is going to be a lot less glorious career-wise than implementing a UX change that is easier to tout at review time (well maybe not so much after this debacle).

I don't think I have ever used stars in making a decision to use a library and I don't understand why anyone would

I do it all the time, whenever there are competing libraries to choose among.

It's a heuristic that saves me time.

If one library has 1,000 stars and the other has 15, I'm going to default to the 1,000 stars.

I also look at download count and release frequency. Basically I don't want to use some obscure dependency for something critical.

I love how the author thinks developers write commit messages.

All joking aside, it really is a chronic problem in the corporate world. Most codebases I encounter just have "changed stuff" or "hope this works now".

It's a small minority of developers (myself included) who consider the git commit log to be important enough to spend time writing something meaningful.

AI generated commit messages helps this a lot, if developers would actually use it (I hope they will).

The thing is, falling down (ie. failing at things) can take a lot out of you, physically, mentally, financially, spiritually.

For most of us, taking calculated risks is better than simply taking more risks.

And the risk calculation changes based on your personal circumstances: physically falling has a greater impact on an old person than a young person, making a financial mistake has a greater impact on someone who has no savings than someone who is wealthy, etc.

So "let yourself fall down more" isn't really one size fits all advice.

Touched a nerve I guess.

Care to elaborate?

I also knew people who had MUD addictions.

These were very similar to how in later years people became addicted to Second Life or EverQuest and essentially dropped out of society.

I don't know if there is a modern-day equivalent, to be honest.

I am sure IRC was good for some people, but I can say for me personally it was a net negative and real life was so, so much better. I wish I never used IRC.

I also personally witnessed multiple friends who dropped out of college due to IRC addiction in the early 1990s.

I am curious if anyone else has a similar memory of IRC.

I don't see how people use social media apps with notifications turned on.

I just disable all notifications and it doesn't bother me to have LinkedIn because I only open it when I feel like it. Same with Facebook, etc.

Incredibly, the default is always for notifications to be enabled, and I don't know how people live like that.

Telling people they can't unsupport something

Yes.

I have no involvement in this drama (it's the first I've heard of it actually), but signing your name to something matters.

Choose carefully what/who you support.

A repo owner is not obligated to accept contributions.

All of those people are free to create their own repo, post on social media, or write an article recanting their support if they choose to do so.

I stand corrected.

It looks like web workers is the way for JavaScript to do multi-threading.

Async has always been enough for what I need to do in the front end, as most of my long running processes are just calling a back end.

Edit to add: for context, I am a full stack developer and know what threads are... I just never have needed them in the browser.