dhuramas
[1]: https://news.ycombinator.com/item?id=34144566 [2]: https://kcl-lang.io/docs/user_docs/getting-started/intro/#vs...
Failure Modes and Continuous Resilience
[1]: https://nextcity.org/daily/entry/10-facts-homelessness-2014
I think people feel strongly about certain issues. That doesn’t imply that what they are doing is inherently wrong if driven by those core sentiments. How about we empathize- We can respect both Google’s and the employees’ action without choosing sides.
But my first thought before clicking was- please don't be ad/marketing/SEO biz.
I am going through this course- and it is fabulous. Covers tests, and even though the topic names might seem easy or trivial(I mean there is only so many ways you can write loops or define arrays), they include a lot of "extras" that make it fun- for example one of the topics might include details about how to write doctests and docs, another one might introduce table driven tests and provide advice on when to use them. Overall it is great.
I'd be very interested in seeing this approach applied to other language courses.
If the underlying views were performant- I'd assume the query optimizer would do the right thing(at least 90% of the time).
EDIT: I guess it depends - Just did more research and found this [1]. As long as the views don't do unnecessary heavy lifting or joining unnecessary tables, it should be fine.
[1] https://dba.stackexchange.com/questions/151169/are-views-har...
> I thought we were trying to stop people writing their passwords down and storing them next to their computer?
Yes- but I guess it's okay to use password managers anyway. And they make it easy to store screenshots and stuff as attachments.
Besides they had a clear communication about the matter- it's not as if the customers had the rug pulled off their feet. They have been informed well in advance.
CockroachDB tried something. It seems to not be working- so they are changing. It's not as if they are doing it retroactively.
Aurora Postgres – Disastrous Experience
Rust[0] Chef [1]
And here is an old HN comment[2] going into why it doesn't really matter.
Besides it's a Show HN- why be negative when we can raise the same issue more constructively as "Please add checksums and digital signatures. Also why not use regular GitHub releases in the installation instructions?"
[0] https://doc.rust-lang.org/book/ch01-01-installation.html [1] https://docs.chef.io/install_omnibus.html [2] https://news.ycombinator.com/item?id=12766049
Hot: A Height Optimized Trie Index for Main-MemoryDatabase Systems[pdf]
Black Ribbon please.
As an end user, if you care about free software- this is good news. Instead of having different "Enterprise" and artificially handicapped "open-source" edition, we get to see everything out in the open. The secret sauce is now limited to the release process. They say openly that if you need to, fork them and create your own releases - yeah go for the "knockoffs" if you can trust them - or else try the branded (Chef) product.
MongoDB got a lot of flak for misappropriating the name "open source". What Chef is doing is IMHO more clear and honest. They need to make money too.
Amazon Aurora ascendant: How we designed a cloud-native relational database
Why Bloom filters work the way they do
Unknown to most, Kubernetes was originally written in Java
All the licenses(Except the Third-Party Driver licenses) look opensource to me.