Hacker Newsnew | past | comments | ask | show | jobs | submit | thefilmore's commentslogin

I wrote a guide [1] that collects this information in one place.

[1] https://akr.am/blog/posts/a-guide-to-compiling-programs-on-w...



End-to-end encrypted, open-source, ~250 lines of code, password optional, and not just for links - https://plic.cc


Bell Labs had a simpler alternative in IFFE [0], that consisted of a single shell script [1]. You would specify any required headers, libraries and tests in a simple text file [2].

[0] https://www.cs.tufts.edu/~nr/cs257/archive/glenn-fowler/iffe...

[1] https://github.com/att/ast/blob/master/src/cmd/INIT/iffe.sh

[2] https://github.com/att/ast/blob/master/src/cmd/3d/features/s...


xzploit


It's also a drop-in replacement for grep as it supports the same flags and regular expression syntax.


I tend to reach for TypeORM. It supports every database under the sun.


TypeORM is great and all - but it has its own quirks too and it's not a silver bullet.

In their case they would also maybe run into some issues as TypeORM has some initialization cost (building a model in memory when it first connects to the DB etc), some object mapping costs and other complexities (particularly around efficient query generation).

While there is nothing stopping it from working in a Lambda this would increase initialization time and cost which both matter since this is for a GraphQL API. I think the solution they've selected (Kysely) is probably a better fit.


In my testing I found no difference in response time for a web app running in Node.js vs Bun.


ThePrimeagen did some benchmarks on stream recently - he found Bun to be slightly better in terms of average response time, but the biggest gain was P99 / P99.9 values under heavy load.

NodeJS seems to drop the ball on a handful of requests when it's getting slammed, i.e. upwards of 10s vs average of 100ms. Bun had a much smaller P50/P99 spread.


Your guess would be correct [1]. Some samples [2].

[1] https://www.mdpi.com/2624-599X/4/3/42

[2] http://www.harmjschoonhoven.com/mp3-quality.html


MP3 smearing can be noticed even at 256kbps [1].

[1] https://www.soundonsound.com/techniques/what-data-compressio...


Well, MP3 does have some fundamental limitations that were only fixed with subsequent codec generations, like AAC or Opus.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: