HN user

avisser

641 karma
Posts0
Comments270
View on HN
No posts found.

After 4 years of Russia/Ukraine, does anyone think that a terror group would take down an airliner with anything other than a drone? Why take any operational risk of actually going through security?

Off the top of my head, C# is both the language & the runtime. React only throws things over the fence to browsers.

Probably helps a lot to keep abstractions from leaking.

why bother learning two paradigms

Objection. Your React is ultimately turning into HTML so you DO have to learn HTML + CSS. You just have an abstraction over it.

Work bought me a VisionTek hub. I wanted the 1 cable life - unfortunately, it only does monitors via DisplayLink, aka compressed & streamed to & from my desk. It's noticeably fuzzy.

So now it's 2 cables: 1 from the hub, 1 from the monitor. Both USB-C.

WTF guys?

My Apple monitor from 2009 just worked with 1 cable (no power, but still).

IMO that phrase came about when old tech companies (the IBMs of the world) had

  * waterfall
  * design up-front
  * source control systems that
    * defaulted all files to read-only
    * required you to "check-out" files, potentially locking other devs out from editing them [1]
  * probably didn't have unit tests so "deploying to prod" meant "doing a full QA pass, done by human beings"
  * there was no CI/CD (We had "Build Engineers")
In this context, pushing a change to SVN/git/hg, having tests run automatically, then having CI/CD push new code to production, all as a side-effect of one engineer push a button? That was moving fast, and occasionally, breaking the whole website. But we got better tests, better CI/CD, metrics, green/blue, ... We learned it was unequivocally better than the old way.

[1] Reserved Checkouts: https://www.ibm.com/docs/en/clearcase/11.0.0?topic=ucm-check...