You're right that 7 / 7,000,000 are good odds, and most people would likely take them - but it would be unwise to not give people an educated choice between vaccines if there are known risks.
1,047 karma · joined April 1, 2014
Email: funnylookinhat at gmail
Github: github.com/funnylookinhat
Location: Portland, ME, USA
You're right that 7 / 7,000,000 are good odds, and most people would likely take them - but it would be unwise to not give people an educated choice between vaccines if there are known risks.
BUT - I'm really thankful for people who keep posting and sharing these sorts of projects; they're the ones iterating the process for the rest of us who need something a bit more turn-key.
I'm excited to see this eventually result in something like the following:
- Standard / Easy to update containerized setup.
- Out of the box multi-location syncs (e.g. home, VPS, etc.)
- Takes 5 minutes to configure/add new locations
I want this to be as easy as adding a new AP to my mesh wifi system at home: plug it in, open the app, name the AP, and click "Done".
(Edit - formatting)
It certainly isn't that interesting for everyone, but for a subset of users it's great!
Adding the ability to loop the gif back and forth would be great!
That was super helpful - thanks for explaining!
I'm still lost as to what the advantage is other than a faster start-up time. What am I missing?
1: With ES Modules, imports are asynchronous.
Synchronous imports are incredibly powerful. You can ensure that your application doesn't block on first requests, but instead on load. Initializing connection pools, setting up caches, etc.
You'll also find quite a few packages in NPM that explicitly depend on require over import just so that they can perform the bindings they have to before things get going (see https://www.npmjs.com/package/honeycomb-beeline as an example).
2: With ES Modules imports are commonly destructured.
I know it makes your code feel lighter to have const { add } = import("whatever"); - but as your files grow larger, and those imports start to become complicated bits for middleware or other features, you're just making it more difficult for future maintainers to figure out what those functions mean. A bit of context never hurt anybody, and for my money I'll be that this:
app.use(check);
is not nearly as useful as
app.use(Validator.check);
The example may be contrived - but 9/10 times I find this makes code better than the alternative.
All of these arguments go out the door for Frontend work - that's a totally different terrain. I think one of the big arguments is that developers want to use the exact same JavaScript on frontend and Node applications - but that's an argument unwilling to admit the fact that they're two very different tasks. :)
I've found that 2k (2560x) displays at 27" give me great real estate without any need to scale.
Adding byobu made it effectively impervious.
I think the author is doing the best they can considering all of these tools and resources aren't updated to this pattern yet, but I'd hate to see this become the new normal for any developer entering into the field. What a way to scare off new dev friends!
I've been trying to stick to literal shell (as in /bin/sh) lately for portability reasons - but every once in a while there's something in bash that makes my life much easier!
I have HN set to 125% by default and its great.
Thanks for the mirror!
Thanks for sharing! Bookmarked.
But man - Haskell feels really difficult to wrap my mind around. Could anyone here comment on the learning curve and how it affected productivity for team adoption? Seems like it's on the more difficult side of things.
This is possibly one of the most infamous of all Slashdot threads - it was a collection of emails detailing how it was to be an outsider in the days after Columbine.
https://news.slashdot.org/story/99/04/25/1438249/voices-from...
If the stories in this post are interesting to you, a book to consider would be Geeks, by Jon Katz.
I'm already paying AWS a massive amount for compute, storage, and bandwidth - I don't want to pay more just be able to use it efficiently.
Maybe it's the FOSS nerd in me - but I can't stand the walled-gardens we're essentially creating in these IaaS providers.