inshadows

What sort of better algos?

It may be our only refuge when Earth's going to be burning for thousands of years. https://en.wikipedia.org/wiki/Seveneves

Who needs government sponsored science? All hail the Musk!

Written by judgemental asshole.

Since this article is about labeling other people as assholes, I hope it's OK that I did the same.

Who are these millions?

I enjoyed the audiobook until the "rebirth" of CISO where it became too cringe. Then I dropped it for later. But I still recommend it, just for fun.

"Sir Humphrey Appleby : The Queen is inseparable from the Church of England.

Jim Hacker : And what about God?

Sir Humphrey Appleby : I think he is what is called an optional extra."

How can one find LOCATION of such active jammer?

EDIT: How can one find location of a jammer? I'm interested in the process and equipment needed to find location of active jamming device in a geographic area. E.g. what police uses and how can an average person like me do the same.

I know Puppet is a mess. What you say is that you spill lot of exec's into a class? You can avoid that, can't you? If you just declare "resources" and connect them via relationships, then it seems pretty "declarative" to me, i.e. there's no sequence of actions in Puppet DSL and when you run puppet it only does what's necessary. While I find it truly "declarative", I still think Puppet and its ecosystem just suck, for lot of other reasons.

I don't think Ansible even tries to hide the fact that it's just imperative sequence of actions. I wonder where the people saying opposite are coming from. It's just retarded imperative language.

Puppet is declarative, isn't it? You declare states and relationships, and it computes plan of action.

Ansible is not declarative at all though, and it's not even funny how almost every fan says it is. It's just a sequence of actions.

> All of the examples above have one thing in common - they focus on the needs of developers instead of needs of the customers.

Exactly. https://web.dev is prime example of that. Shiny new features for _developers_ all the time, as if any of that will make incompetent web developers write slick and fast applications.

Could you please explain the option thing in the contract? I don't understand what this means

"It had a clause, options would be good for ~7 years. I misread that as time to execute."

OK. So the things under google GitHub organization are personal projects for which googlers didn't bother to get the permission?

What support does this project (and other "Launch HN" ones) get from YCombinator? How much money for the runway?

How is it going to catch new files? ls runs once, doesn't it?

Even better: https://en.wikipedia.org/wiki/Observability

I don't think you understand UB, because clearly, this is not UB.

But I congratulate you. You have enough knowledge to engage in Internet discussions involving fancy names without understanding underlying concepts.

Hint: 1) Read my original post. 2) Contemplate whether the compiler is removing anything in this instance.

Yeah, I know what UB is, and that's why I'm saying that this is not UB. Have you even read what I wrote?

Where is the undefined behavior? AFAU, UB is a compile time concept. As other commenter has asked, how can the compiler infer that has_value() call has any relation to key_data_ non-NULL-ness?

EDIT:

> optional->... is UB if the optional is empty

I understand what you mean: dereferencing optional is undefined if has_value() is not checked for true in the same thread before. But that undefined behavior happens at runtime, i.e. compile time UB is not invoked, the statements are kept without any optimizations. Right? The terminology is confusing.

I guess because it works?

I don't fear Rust Evangelism Strike Force. Bring it.

I agree that handling XML is more complex than handling JSON, but only slightly. Unless you use Java of course, where for some reason, handling XML is always pain in the ass.

The complexity of XML features (namespaces and bunch of other standards) is hidden in libraries. And some of those features might be useful, only to be re-implemented in JSON, with same amount of additional complexity in libraries.

Just recently I used lxml in Python to parse RSS and it gave me collection like if I used json module. Moreover, I used XPath extensively to pick parts of the XML I was interested in. This would have been more complex with manual traversal. Of course there are Python bindings to jq, but in general the jq language isn't as widespread as XPath. Then there's the slight annoyance of accessing attributes via dedicated getter methods as they're "special" as you mention. But in all, I haven't noticed millions of lines of extra code and complexity.

> XML didn't work as a data interchange. JSON and YAML (and TOML etc etc) beat it handily.

Why not? AFAIK it worked well. See SAP and many other products.

You haven't mentioned anything specific about dangerousness of goto. The fact that you heard some conclusion is irrelevant, unless you pass the reasoning behind it. If goto is dangerous, why isn't if statement dangerous.

And about async code: Have fun writing bare metal code with that. Because, you know, your compiler will spit gotos anyway, and unlike gotos you write, you'll have little control over that.

This thread isn't about safety though. It's about readability (spaghetti code). IMHO gotos in C when used for for dealing with errors at the end of the function make the code clearer.

Hopefully, LetsEncrypt is and will always be incorruptible organization. There was never a case of a community project being taken over by greedy capitalists. Oh wait...

1. http://n-gate.com/

2. You sure place a lot of trust into third parties.

With JavaScript disabled, the text disappears in pretty animation on load. Good job unhred.com.

White screen without JS

I second that, but in Europe please. Thanks!

Don't you need to hit the DB anyway to fetch authorization data like user role? Clearly you aren't going to store it in JWT or you face the issue with invalidation. But fine, cache it in Redis. Problem solved.

10 timeout to reply. o_O

Set counter = 0 in DB. Put it into JWT. Increment the counter in DB to revoke the user. Compare counter in JWT < counter in DB. What's the problem?