Preferences

rivetfasten
Joined 19 karma

  1. > Of course, we've been told to never accept a counter offer at your job.

    Do you have a example article? I haven't encountered the advice, but I'm curious if the reasoning matches my guess.

  2. Who reaches for a tool they forgot about?

    Few organizations invest in solutions only understood by one or two individuals on their team. This is actually what prevents undergraduate cs knowledge from having an impact. It makes me sad.

    Undergraduate CS isn't about the things you do most of the time. It's about enabling the occasions where the alternative is to give up and shrug, or perhaps speculate instead of evaluate.

    Undergrads, read this before taking a theory of computation class: https://swtch.com/~rsc/regexp/regexp1.html

  3. I was about to mention this too.

    Compare: "import a specific lightweight library and wire together as needed" vs "write the whole app in terms of a bloated framework".

    I've been out of the frontend game for a while, but what does react give you that knockout and maybe some url management logic do not?

    I guess components are supposed to standardize modularity, so you can easily import some random widget?

  4. It's always a matter of chasing the bottleneck. It's fair to say that network isn't the bottleneck for most applications. Heuristically, if you're willing to take on the performance impacts of a GC'd language you're probably already not the target audience.

    Zero copy is the important part for applications that need to saturate the NIC. For example Netflix integrated encryption into the FreeBSD kernel so they could use sendfile for zero-copy transfers from SSD (in the case of very popular titles) to a TLS stream. Otherwise they would have had two extra copies of every block of video just to encrypt it.

    Note however that their actual streaming stack is very different from the application stack. The constraint isn't strictly technical: ISP colocation space is expensive, so they need to have the most juiced machines they can possibly fit in the rack to control costs.

    There's an obvious appeal to accomplishing zero-copy by pushing network functionality into user space instead of application functionality into kernel space, so the DPDK evolution is natural.

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal