uvdn7

22 ms·

1. 181.▲
   What happens when you throw an exception in C++(blog.the-pans.com)

   1 points by uvdn7 5y ago|0 comments
2. 182.▲
   C++ exceptions are fast most of the time(blog.the-pans.com)

   2 points by uvdn7 5y ago|0 comments
3. 183.▲
   by uvdn7 5y ago

   I agree with you but we should leave frame pointer out of this — as it almost has nothing to do with it? libunwind knows how to read DWARF anyway. It’s more an implementation detail.
4. 184.▲
   by uvdn7 5y ago

   Is that the same as the decode_stacktrace.sh mentioned in the blog post or significantly more sophisticated? I am sure we can always automate more things :)
5. 185.▲
   by uvdn7 5y ago

   I have an HHKB for many years. It’s still my favorite keyboard. It’s very personally and subjective. Most of the reasons for why I like it can be explained as I am used to it though - eg it’s layout.
6. 186.▲
   Application Binary Interface from the Ground Up(lu-pan.com)

   1 points by uvdn7 5y ago|0 comments
7. 187.▲
   by uvdn7 5y ago

   Brilliant!! What's really cool is that Jakub approached the crash systemically. There are hard bugs in life e.g. cache inconsistencies, kernel bugs. What' more important than fixing them with one-off solution is to come up with a
8. 188.▲
   by uvdn7 5y ago

   Thanks! Updated.
9. 189.▲
   ABI from the Ground Up(blog.the-pans.com)

   3 points by uvdn7 5y ago|2 comments
10. 190.▲
    by uvdn7 5y ago

    While we are at it, looks like spotify.com is using a mix of NS1 and GCP for DNS. spotify.com. 172800 IN NS dns1.p07.nsone.net. spotify.com. 172800 IN NS dns2.p07.nsone.net. spotify.com. 172800 IN NS dns3.p07.nsone.net. spotify.com. 172
11. 191.▲
    by uvdn7 5y ago

    Ah you're right! Thanks!
12. 192.▲
    by uvdn7 5y ago

    That only says spotify.com is using GCP's DNS but not necessarily for hosting? EDIT: I was wrong, as pointed out by shizcakes.
13. 193.▲
    by uvdn7 5y ago

    Now I see that getting rid of the DeWitt clause is indeed great. Kudos to both companies.
14. 194.▲
    by uvdn7 5y ago

    I genuinely think DeWitt clause is good for the users (bad for researchers). Without it, especially in the context of cooperate competitions, the company with the most marketing power will win. Users can always compare different products t
15. 195.▲
    by uvdn7 5y ago

    I disagree. It makes sense for Snowflake to response to what-they-think-is an unreasonably bad result published by Databricks. And they focused more on Snowflake’s result and only compared dollar cost against Databricks. It’s consistent wit
16. 196.▲
    by uvdn7 5y ago

    Exactly. That’s why I think public benchmark war is just a waste of time. There will ALWAYS be some subtle differences between the two platforms that results will never be apple to apple.
17. 197.▲
    by uvdn7 5y ago

    Snowflake claims the snowflake result from Databricks was not audited. It’s not that Databricks numbers were artificially good but rather Snowflake’s number was unreasonably bad.
18. 198.▲
    by uvdn7 5y ago

    I don’t think they are saying benchmark is not important but rather public benchmark war being a distraction.
19. 199.▲
    by uvdn7 5y ago

    It’s probably just me but the distinction between datalake and data warehouse seems like splitting hairs. Unstructured data can always be stored on structure databases. What’s the main reason for both to coexist?
20. 200.▲
    by uvdn7 5y ago

    Whose result can be trusted is beside the point - I actually believe both experiments were likely conducted in good faith but with incomplete context. But that’s beside the point. The point is there’s no good reason to start a benchmark war
21. 201.▲
    Snowflake’s response to Databricks’ TPC-DS post(snowflake.com)

    80 points by uvdn7 5y ago|102 comments