They’re always racing to be the first one to write an article about a case.

Attackers can’t push a security update without going through the reporting process (e.g. Github CVE), so they can’t necessarily abuse that easily.

In this age, many smaller companies serve customers across the globe. There is no common “asleep”.

For reference, oven-sh/setup-bun opted to install dependencies from scratch over using GHA caching since the latter was somehow slower.

https://github.com/oven-sh/setup-bun/issues/14#issuecomment-...

Because of OSS, I’ve never actually applied for a job or done a Leetcode interview. I’ve gotten multiple direct offers through Twitter DMs (I don’t post) and multiple referrals through random encounters that I never used.

E.g. Debugging an interesting issue with GitHub customer support eventually led to a referral for Microsoft by an MD. Similar stories with Cloudflare and more.

It’s not limited to OSS, but just having any sort of backing credibility to your name without going through the whole CV/CL process unlocks a whole slew of opportunities since people can “pre-screen” you from the start.

Nor would you want someone who built most of their career as an actual engineer to suddenly drop that term and become a generic someone in “marketing”. They’re more than that for sure.

I quite like the terminology the more I think about it.

https://github.com/aarondfrancis

[1] https://github.com/mitchellh/libxev

Comments URL: https://news.ycombinator.com/item?id=45836184

Points: 3

# Comments: 0

Are people supposed to be obligated to post such a report nowadays?

I enjoyed the article and found it really interesting, but seeing these types of comments always kind of puts a damper on it afterwards.

Comments URL: https://news.ycombinator.com/item?id=45422569

Points: 4

# Comments: 0

You still get performance improvements even if you don’t switch over to the new import!

For example, common ingredients like potassium bromate or ADA are straight up banned in the EU for health concerns.

Reading the ingredient list of American bread is plain shocking at times.

If you’re working with goroutines, you would always pass in a context parameter to handle cancellation. Many library functions also require context, which poisons the rest of your functions.

Technically, you don’t have to use context for a goroutine and could stub every dependency with context.Background, but that’s very discouraged.

Where I used to live in the Middle East, the culture was very tea (more specifically karak) centric for sure. But it wasn’t a hobby you get so deep into that you become very specific for the average person.

You just drive to your regular place. There’s only one choice and that’s karak. You sip it in your car, chat with your buddies, and you drive off.

Definitely do miss the late nights there. No alcohol, just tea and still an extremely social society.

I doubt they’ll ever enshittify DuckDB core. It’s clear they’re only aiming for better integration with their paid service via peripherals like UI to improve the experience, but you also don’t need to use it?

It’s all extensions that you can develop the end.

net/http (even middlewares are just http.HandleFunc)

> database connections

We were using database/sql for the longest of times before switching to pgx since we wanted some convenience functions.

> email sending

net/mail gets you far enough unless you want to scale it.

> logging

log/slog (which is actually production grade compared to log/log)

> view template rendering

text/template, but I also think Laravel is a better choice if that’s your main focus.

Others either need an experimental standard library package (e.g. golang.org/x/crypto/argon2 for stuff like authentication) or finally need third party dependencies. DI is not enforced like other frameworks, but an extremely common pattern in Go.

At this point, do I really want to bring out a whole framework just for the last few requirements?