you're right I don't...but people that listen to that stuff were probably never going to vote for anyone other than Trump (anymore than listeners to MSNBC were going to stray from Harris). My primary sources are relatively centrist sources like WSJ and Economist as well as a variety of independent podcasts and the NYTimes. With a few exceptions on the podcast front all of these outlets were unabashedly anti-trump.
If this was the case then it seems that Harris would have won the race...the vast majority of the media I saw here in the US was going on and on about how Trump was a grave danger to democracy and in general just a terrible person and candidate. In regards to the media, I think this election shows that a large majority of the population simply does not believe them at all.
Super interesting article, as a native english speaker who lived in Japan for many years and speak Japanese fluently, he pointed out a lot of things I always took for granted in Japanese (and never recognized as unique). One things I was hoping he would point out, and that I always found extremely unique in Japanese, was the giyongo (basically onomatopoeia). Japanese uses these extensively and the sounds can have extremely sensory driven meanings. They use these giyongo to describe physical textures (tsuru-tsuru is something smooth and slippery), hard to describe souns (pera pera is the sound of speaking a foreign language), flutently), actual sounds (tatata is the sound of fast running), a general feeling (bisho bisho is the sound of being soaked), specific actions (gussuri is the sound of being out cold), even specific emotions (zukizuki is the sound of extreme pain). There are hundreds if not thousands of these and I think they also make the language, as the author describes, 'rich and quirky and different'.
This article is dramatically simplifying the state of software markets.
>Single vendor isn’t a reasonable way to do Open Source and resist evil proprietary software. It’s just another way to do proprietary software.
>proprietary software is not evil. It’s just inferior.
Based on these statements the author would have you believe there is no value in commercial/proprietary software and we should just never develop it. All software should be open and collaborative. That is obviously silly. While open source software is great, many incredible software innovations and truly valuable software comes from proprietary companies. In fact, these companies are typically the ones that make the large open source ecosystem possible by making massive donations in developer hours as well as cash to orgs like linux foundation.
The interesting discussion is in whether commercial software should be closed source or source available with restrictions. The days of building propriety, VC backed infrastructure software with a traditional permissible license are over and likely never coming back.
My grandfather was an academic who studied 'socially alienated adolescents' and was the original director of this program when it was developed back in the 60's. This is one of his original lectures on the social dynamics that drove the program: https://www.youtube.com/watch?v=aPwV8miW46I&ab_channel=Natio...
this is definitely not true of SF...its very obvious for anyone walking around when you are in a good or bad part (parts of SOMA/Tenderloin/Civic Center/Western Addition). Most other parts of the, including where this crime happened, feel completely safe (and statistically are very safe).
It really depends on the type of application but a common one is getting a large spike in traffic beyond the norm (front page on HN, flash sale, etc.) I do think #1 and #2 that you mentioned are more common constraints and are ones that also both addressed in Dragonfly (much more efficient memory utilization and ability to scale vertically which negates the need for complex orchestration)
These stations are all along the Northwest Passage which was extremely inaccessible back then, especially for the large commercial shipping that would be needed. It's become much more accessible recently with warming waters but still mostly just by small craft in the summer.
for most engineering teams the cost of building and maintaining a notification system goes well beyond a $5/month server, though of course it depends on use case and complexity. If you want the ability to render messages across multiple channels from a single template, unified logging across multiple channels, and flexible infrastructure that can scale with demand then you are already talking about a pretty expensive and complex system.
Aren't there some cases where they could be valuable? like alert that plane is delayed before you leave for airport or that your uber has arrived outside?
Courier YC S19 | Full Stack Engineer | San Francisco | ONSITE (Post-COVID)
Courier is the fastest way for developers to build notifications for their app. Our APIs take the tedium out of integrating various notification channels, while our visual designer lets anyone design a message template and deliver their notifications to the best channel for each user with a single API call. Email, Push, Slack, SMS, you name it. Think "Stripe, for notifications."