Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mohbk
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
mohbk
2y ago
I'd argue this is because social media is ironically enough, manipulated less than traditional mass media. Despite brigading from any side, anyone can get anything trending on social media, including videos of the aftermath of israeli
2.
▲
by
mohbk
2y ago
Yep, people not seeing the usecase have not tried to build a serverless product on AWS and found themselves stuck between cheap, performant but denormalized ddb or whatever the fuck aurora serverless v2 is supposed to be. I do not want to d
3.
▲
by
mohbk
3y ago
and typeof NaN == "number" is also part of the standard, it is valid to pass NaN to functions that accept numbers, and it's expected to propagate or change back to normal numbers (e.g. NaN^0=1)
4.
▲
by
mohbk
3y ago
the website is 90% problems of very stupid implicit type conversion, and 10% valid floating number behavior that exists in other languages too (0.1+0.2, NaN a number) I agree using plain JS anywhere is not a good idea, but Typescript (or js
5.
▲
by
mohbk
5y ago
knowing how many people can't take disagreement well, I don't think this was a poor decision, practically you can't just trust everyone to have a good head on their shoulders, when you just want a job to survive or get your f
6.
▲
by
mohbk
5y ago
I feel the alternative is not better, a light weight bare minimum lib and no ability to install your own is definitely worse.
7.
▲
by
mohbk
5y ago
there's a number of benchmarks you can checkout online. number crunching wise, Go is on par with Java and C#: https://benchmarksgame-team.pages.debian.net/benchmarksgame/... for webdev work, the standard library m
8.
▲
by
mohbk
5y ago
I think service-changing requests should be passed to a higher level in the chain, to the architects or whatever, changing service contracts can end up changing the domain. I'd assume the architects would have a high level view where t
9.
▲
by
mohbk
6y ago
you can solve underfetching and overfetching in a normal restful API, you can have optional entity relationship fetching on query/params, and also user defined queries. This might be hard/tiresome when you're hand writing SQL