286 karma · joined July 4, 2015
Likely more prevalent are the people who don't like corporations, public services, etc. wishing everyone Merry Christmas year after year while ignoring the holidays of other religions.
To avoid all of this, many places are switching to "Happy Holidays", except there are a not-insignificant number of people who are upset by this and feel that companies/governments should be saying "Merry Christmas" because they should be aligned with Christianity.
Edit: Nevermind, I tried again and it did begin to run before the tab closed abruptly. Tried again in an incognito window and it worked, and it also worked in a regular Chrome window with only one tab. Tried to run it in a second tab in that same window and the tab instantly closed again. Anyone know why this might be the case?
Second edit: While it doesn't run in regular Chrome windows with multiple tabs, it does run in Incognito windows with multiple tabs. I don't think I have the expertise to dig further though.
I'm not a designer myself but the things that strike me immediately are that the fonts and colors seem out of fashion and the site looks somewhat awkward on mobile. But that's my whole point. You wouldn't want those things on the homepage of a startup, but this isn't that. It's just a simple blog and it does a good job of being a simple blog.
It seems to me that one of the benefits of the pipe operator is that it very clearly lays out the steps involved, aka
x
|> maybe_function()
|> final_function()
so that the code is dead-simple and clear. It doesn't seem nested in the say way that final_function(maybe_function(X)) is.Granted, I don't have nearly the level of experience of the author so I can't say for sure, but it seems to me like they just haven't had enough experience with the pipe operator to see how it benefits the code "beauty".
This appears to be the personal blog of a lone Erlang developer-- why should they put in effort to make bring it up to current design standards?
It does what it's designed to do. It conveys information in a simple, readable way, same as HN itself. IMO there's nothing worth criticizing here.
edit: typo
From the start, this stood out to me as a very faulty premise. How exactly was Parler, a social media site, a competitor to Amazon, Google, or Apple? It would be different if this were Facebook, but we're talking about ecosystems/infrastructure vs a single app/website.
Also how can the power of three separate companies be a monopoly? The argument seems to be that Silicon Valley is itself a monopoly, except Silicon Valley is only a geographic location.
One would think the fact that cases in the US are rising faster than they ever have would be deterrent enough.
It's just so much better on paper. Faster charging (with separate charger), expandable storage, zoom lens, wider wide-angle lens, 120 Hz refresh, MUCH faster processor. All for the same price as the Pixel 5.
I'd already preordered the Pixel so I figured I'd just let it come and return it after testing both together.
Well, I did test them both together, and I'm returning the Samsung. (Remains to be seen if I'll keep the Pixel 5 or stick with my Pixel 2.)
I really wanted to like the Samsung; I had really high hopes when people said OneUI had gotten better. But it somehow just feels so sluggish. The face unlock doesn't recognize my face a lot of the time, and the on-screen fingerprint sensor (which only lets me register 3 fingers apparently?) doesn't recognize my finger like 60% of the time. So instead of just being able to pick it up and use it instantly like I can with my Pixels, it usually takes 5-10 seconds for me to get into my phone, as I fiddle around to get either the fingerprint sensor or face unlock to recognize me before sometimes having to just swipe my pattern. The refresh rate is 120 Hz yet for some reason it feels like there's a delay whenever I try to swipe through the UI. The camera is good but it bothers me even more than I expected, how much it tries to smooth my face.
Anyway, the point of this comment isn't to be a review of the Samsung phone, but just to highlight how jarring it was to experience all of that after having a Pixel phone that just worked. Even at my P2's 60Hz it feels more snappy than this brand new phone with a 120Hz display and top-of-the-line processor. Granted, I haven't tried many other phones than a Pixel in a while so maybe they're better, but I would just remind everyone that specs aren't everything. The Pixel 5 runs smooth and does everything I want it to well (although it does take longer than I'd like to process photos).
My only problem is that my Pixel 2 also ran smoothly and did everything I wanted it to. The only reason I'm considering the Pixel 5 is the bigger screen and wide-angle camera. So we'll see how I feel in a few days.
After it was stolen, I bought another Pixel 2 used and while the battery life is worse, it still runs perfectly well as far as I can tell.
I have little experience with handiwork but I'm imagining if an amateur developer said this in regards to building a maintainable and scalable application (as I imagine a house to be) from scratch, and scoffing at tedious time-wasters like writing tests and hiring QAs.
As an experienced developer I know the tradeoffs of cutting corners and various quick fixes and so can apply them judiciously, but I know if I ended up working on or taking over that codebase, I'd most likely end up having to tear out a lot of that developer's work and redo it, or else have a headache trying to build and improve around it.
"Previous work using CRISPR in mouse embryos and other kinds of human cell had already demonstrated that editing chromosomes can cause large, unwanted effects. But it was important to demonstrate the work in human embryos as well, says Urnov, because different cell types might respond to genome editing differently."
It says of one study "Of 18 genome-edited embryos, about 22% contained unwanted changes". Such a failure rate probably isn't such a big deal in some applications. In embryos, especially human embryos, it's definitely a big deal.
Also just started trying to learn Svelte today. And I'm about to jump on the breadmaking bandwagon.
Video here: https://www.youtube.com/watch?v=mIhi4BuDSf4
A computer can give me clues as to why I still feel tired after sleeping for 10 hours every night. The right tracker can tell me what my oxygen levels were while sleeping, or how restless I was during the night. It can estimate how much time I spent in each sleep cycle, and identify anomalies in how much REM sleep I seem to be getting, for example.
Many, many people suffer from various sleep abnormalities and insight into their behavior while sleeping can be helpful for helping their conditions, or at least giving them insight into what's going on.
This makes it easier on the researchers trying to conduct a preliminary study. The limitations of the study just mean we can't necessarily generalize the results to both men and women, people of different weights, (nor, I suspect, people of various races,) or even, given the sample size, all men of normal weight.
But first we see if we can detect an effect in "normal weight" males, and then we have doubts about its applicability in other populations we test those populations. This of course isn't the most thorough way of experimentation, but it's the biggest bang for your buck when your resources and/or available subject pool are limited.