skysight-inc/HackerNews huggingface dataset:
The internet has predicted the imminent assassination of every prominent opposition politician, journalist and speaker for as long as I've been online and it's never happened. Glenn Greenwood is fine, Sy Hersh is fine, Bernie Sanders and Ron Paul are fine. Meanwhile Julian Assange was happy to have people believe the DNC leak came from Seth Rich despite knowing he got it from Russia.
>The cables didn't unite Arabs against the US - they exposed the ruthless corruption of their own governments

I'm sensing that you believe that this is something you think that should have been concealed from them for their own good.

>It's shocking that someone could read about Arab governments doing 'very bad things', the US government trying to stop them, and then come away with the notion that the US is the bad actor.

Collateral murder is mostly what people are condemning. Also what this extradition was all about.

It's weird that you seem to believe that the war crimes are not relevant to the discussion about whether the US is "the bad actor".

Well, perhaps not that weird. Your reply suggests that you may have been part of the institution that committed and covered up the war crimes (unless you were in tunisia for a different reason).

>Assange will have to face trial given the fact that he may have explicitly helped Manning break into systems of National Security, which is definitely illegal.

Oh yes. Exposing US war crimes IS definitely illegal - more illegal than committing them, apparently.

Just like Rosa Parks sitting at the back of a bus - that was illegal too.
False dichotomy, if you say so.

I haven't found it too helpful when dealing with AWS and the serverless trend, whose popularity is really just based on price and economics, not technical superiority.

Serverless turns every simple system into a distributed system with the number of failure modes now multiplied by ten.

That sounds like fun.

I do know how to use serverless for the record, I just think it's an overhyped, overpriced waste of time.
maybe we actually have a case for decentralized “web3” networks. At least ones which really need reliability, but can’t can use whatever e.g. airplanes use (telehealth? online exams?)

Of course you need to make sure the network is actually decentralized (see Solana). Or maybe you can just rely on Amazon and GCP and Azure, because surely they won’t all fail at the same time.
Yes, I believe he did. His contributions, in guiding the development of the Amazon marketplace and Amazon Web Services could have easily amounted to e-commerce and cloud computing adding trillions more in value than it otherwise would have.
Yep. The Assange story that he was totally willing to answer to the rape charges but had to flee to a country that wouldn't extradite him to the US for something else isn't really helped by him being extradited by the "safe" country for charges filed years later after a change of government. I'm not convinced of the merits of the DOJ case against Assange either technically or politically, but its notable how many other people publicly known to have been involved in the dissemination of the Collateral Murder video have continued to do investigative journalism without having charges of any sort filed against them, never mind two separate Wikileaks supporters accusing them of sex offences ...
How did OP become so confident in the assertion that it does not cause heart issues? The US media has been claiming the myocarditis risk was some sort of antivax conspiracy theory, that is when they covered it at all.
The only thing that was down was the marketing home page at aws.amazon.com, which is not a “service” and is not on the SHD. All of the actual services are fine, hence the green.
SBT is actually amazing at maintaining a monorepo (or multi-project as they call it)
Or you separately implement this feature that only you need. Instead of asking for it to be supported out-of-the-box by this very popular library where it'll operate unbeknownst to everyone else.
It sounds like after the model is trained, it also pulls from the training database at generation time. Can someone explain how this isn't a kind of "cheating" at generation?

Happy to be wrong.
> That's an hilariously bad advice

Absolutely not! I'm serious, and I stand by it. Rust ecosystem is like a better Python. You have to consider why someone is willing to move away from Python and into a foreign language: Developer supply, performance, safety, ecosystem, political reasons.

I can't cover all cases so I'm going to focus on the one that makes the most sense _from my personal point of view_.

I do AI Software Enginering and Devops when I'm not project managing. So Python is the only and primary choice for all things related to Data Science, dashboards, APIs, pipelines and transformations (on data).

Why and where would I choose Rust ?

In data pipelines, for performances and memory efficiency. This also ensure we have proper boundaries and documentation (APIs, file formats, schemas) between Data Science-related code and pipelines.

In Dashboards and APIs, for improving type safety, and handling more concurrency on background computations than python without resorting to other frameworks (Celery, Airflow, ...).

In data versioning and supporting infrastructure, for additional type safety and mostly making sure that _nobody_ who is not a software engineer won't cross component boundaries by accident. These components are often very delicate and essentials for a working platform. Changing them can have ripples into other parts of the project, and I only want trained engineers on these.

In the opposite, direction, I could pick Python over Rust when it's most appropriate: Restricted developper availability, improving coordination with Data Scientists, single container deployments, existing experience with framework or ecosystem...

The main blocker for not using Rust isn't because the language is new or more complicated, it's because Python offers more advantages to a situation. At the difference from Scala, I can pick _any_ skilled developper and put him from Python to Rust without any side effects (appart from the training part). This is because writing Rust code is much more consistent at all skill level than Scala. There no "flavor" of Rust. There no bickering about "coding style". The Rust tooling is best in class (Scala's SBT is actually worst-in-class, I believe). You can use the same IDE in Rust an Python (VSCode). This leads to a very similar coding experience between writing type-hinted-Python and Rust. This is not the case between Python and Scala.
> Now that because of recent events and we have a chance to be heard

Is there anything about this particular incident that is new that contributes to your position?

Maybe we run in different tech circles, but I feel like the "on-prem vs. cloud" has been litigated fairly extensively here and elsewhere. In fact, as you said yourself:

"Many of us have been taking shots at those 'big boys' since the start of this trend."
Preprints in biology do not carry the same weight as preprints in CS or physics.
Alex Berenson, is this the guy who concluded that Covid vaccines drive "excess mortality" for people under 60?

edit: ""
It looks minimalist and at the same time futuristic.
I'd be amazed if it isn't a configuration error of some kind.
Java Unmarshaller Security – Turning your data into code execution
‘Log4Shell’ vulnerability poses critical threat to applications using
Fortunately you and I do not individually make that decision. Society does and it has deemed, through democratically elected leaders and participation in a social contract that there is a case to be made to state secrets.
I see this as akin to how factory work has changed with modernization. In a modern highly automated factory you need a much smaller number of highly specialized engineers to maintain the robots. In the analogy, these fewer highly specialized engineers are analogous to the ones who need to know understand TCP/IP in depth and now run AWS. The rest of the workers, now replaced by robots, can move on to different productive work.
Lightweight dependency injection and unit testing using async functions
"none of the “crimes” happened on US soil"

This is essentially false as his ostensible crime relates to participating in the hacking of US systems.

By your inference, Russians hacking into US Hosptials would not be committing a crime on 'US Soil' as though that would make a difference.

Let's have the trial and see the evidence.
You don't. There isn't any. The reason why is explained here: https://thebaffler.com/salvos/of-flying-cars-and-the-declini...
JSON has a standardized spec and the API you design has to do a few things: Marshal and unmarshal.

How frequently do these need to change?

The problem with the library landscape is that one library will be promoted by the purists and another by the company with the money. Suddenly you have to learn both to understand Scala codebases.
There are several factors, higher Vitamin D levels because of time spent outdoors, median age of the population, co-morbidities including diabetes, levels and availability of testing and gathering data etc. etc.
I'm not sure I buy this. The main driver of the industrial revolution was intellectual: the emergence of science, classical liberalism, mercantilism, and modern economics. All this was in place before anything really took off.

Industrialization without fossil fuels would scale much more slowly with wood being used at first and then probably crops being grown for energy (biofuel). Once we figured out electricity we'd have large scale hydropower and wind power. Then we'd figure out either photovoltaics or nuclear fission, at which point we'd be off to the races. My guess is we'd be almost 100% nuclear and hydro powered right now with use of photovoltaics growing.

Stable power grids would probably take longer to emerge, but we figured out simple rechargeable batteries (lead-acid) fairly early. People would probably have banks of these in their homes to power minimal lighting and things like radios, TVs, etc. at night and run their appliances at specified times when the grid was at high power. You'd probably see a food system less dependent on refrigeration until stable grids emerged.

On extremely long historical timescales I suppose depletion of other elements is possible, but things like iron are incredibly common in Earth's crust. I'd be concerned more about rare elements.
Infinite, there is a mathematical formula: https://en.wikipedia.org/wiki/Sunrise_equation
When they tap the chestnut at 3:30am for prayer, is that a bedtime event (their time) or a daybreak event (standard timekeeping)?
I've seen deals where a company sells a pack of consultants to a multi-year project with a price tag of over 1M euros. I don't know if this happens when the scale is 10M+, but it does happen at 1M scale.
Generate Images from Texts in Russian
FS-UAE here, hell I was just playing Laser Squad yesterday...
> Lead induces less damage to the firearm

Over here when lead was prohibited for hunting waterfowl, there was lots of heated debating about the issue. People hunting with grandpa's old shotgun had to either get a new gun for use with steel, or use the hideously expensive Bismuth shells. Seems most active hunters switched to newer guns. I haven't heard anything about modern guns wearing out prematurely due to shooting steel.

> To use non-lead alternatives you typically either have increase the size of the projectile( (s) in the case of shotgun shot ) and/or increase the powder charge. This typically means an individual will need to purchase different firearms. For instance, to get close to the ballistic performance of lead shot in a 12 ga shotgun you will need a 3.5 inch shot shells. The vast majority of shotguns accept 2.75 or 3 inch shells.

Or, you know, if your gun can't take those spiffier shells, slightly limit your shot distances?

> Steel shot in shotguns is more likely to wound game by creating bleed tunnels causing the animal/bird to bleed out much later and not be retrievable. Lead creates more catastrophic immediately fatal wounds.

IIRC there was some research from Denmark suggesting the opposite, namely that the significantly harder steel pellets would have a higher probability of punching through bone and hit vital organs rather than deforming and lodging in the bone. ¯\_(ツ)_/¯

> Copper bullets do not expand as quickly and as effectively as lead bullets leading to more wounded game.

I think this is a relatively newer development, and it seems every year manufacturers are introducing newer copper bullets with more ductile alloys, precut grooves and whatnot to make them expand faster. I don't think it will take long, to the extent it hasn't already happened, that copper bullets will be good enough for the vast majority of usage. Sure, if you want to hit a rodent at 800m or some other extreme form of long-range marksmanship, you really want the density of lead, but most rifle hunting is done at significantly shorter ranges.
For example - given the ample (and basically) record of U.S. authorities in regard to their treatment of so-called High Value Detainees -- and even of very low-value detainees at is borders, as we have seen in recent years -- the High Court had no reason whatsoever to lend credence to the so-called "assurances" they cited in their ruling:

The High Court said Friday that it had received appropriate assurances from the U.S. to meet the threshold for extradition, including:

Assange will not be subject to “special administrative measures” or be held in a notorious maximum security prison in Florence, Colorado.

Assange, if convicted, will be permitted to serve out his sentence in his native Australia.

Assange will receive appropriate clinical and psychological treatment in custody.
In the early days of the internet it was a closed network of academic and government properties. Nobody at that time would have guess it would grow into even the 80s style internet, let alone what we have now.
thanks, updated https://scailer.com/news/lifestyle/join-scailers-final-beta-...
Where do people find good discussions about the economy, investing, etc?

Anyone taking a deeper dive into the Fed, global markets, QE, China, etc

Btw, this was an interesting read:

https://www.bridgewater.com/its-mostly-a-demand-shock-not-a-...
The US is actually quite far in the "monist" side of the spectrum when it comes to ratified treaties but it has such a divided and dysfunctional political culture coupled with an executive which has wide latitude in foreign affairs that many agreements are signed up to by the executive without being ratified by the senate. Monism basically means that properly entered into, international treaties have force as domestic law as well.

The UK is one of the world's most dualist countries. No treaty has any domestic legal standing whatsoever. Until 2010, the government of the day could ratify treaties without recourse to parliament although there has been an observed rule since the early 20th century called the Ponsonby rule that parliament have time to debate and vote on important treaties. The government cannot make domestic statute law without a parliamentary vote therefore dualism emerged.

This means that the UK has to pass a "back to back" law to give legal effect to any treaty it signs where that is required. The US only has to do so when there are elements of the treaty that are plainly not "self executing" i.e. if the US signs a treaty creating a personal right for its own citizens then no further legislation is required but if it signs a treaty agreeing to do something that requires new appropriations, a new agency, or whatever then additional legislation is required.

Quite a long-winded way of saying that Assange never had recourse to certain claims his legal team attempted to make about conflicts between his treatment and the extradition treaty - the extradition treaty does not directly drive UK domestic law on extradition.
My experience with Tailwind + ViewComponent has been great as well. I've also had a lot of success with adding Sorbet typing to the view components. I often use Sorbet enums as view component options. The extra type safety in the view layer is very helpful.
While I don't agree with the OP that Infinite took all the fun away, there are certain minor inconsistencies in the sandbox implementation as compared to previous Halo games that keep it from being as great as it could be. That said I've always thought Halo was the best fps implementation, in agreement with the OP.

-No friendly fire changes the dynamics and risk assessment of throwing grenades, one of the primary combat 'tripod' legs. No longer do you have to weigh the option of throwing a grenade to aid a teammate for fear of also killing them. Are they in a capture zone? Throw everything to got to help keep pressure off of them.

-Melee hit detection is wonky, as is the lunge. To be fair the range and stickyness of the lunge seems to change with every iteration and it takes some time to get used to it. But, there is something off with the hit detection. I've gotten, and been victim of, one-hit melee kills to the front, as if it was an assassination from the rear.

-I greatly feel the loss of Reach's 'shield threshold' mechanic. For the unfamiliar, there were few instances (1hko weapons primarily) where damage would 'bleed through' shields and into health. When the shield popped, so did any overkill damage from the attack that took the shields down. What this boiled down to was a very binary point, if shields are up a melee attack will only take down their shields, if their shields are down, it'll finish them off. Coupled with a very clear visual indication when someone's shields went down, it became an instinctive part of the flow of battle, to me.

-No collision with teammates is pretty awkward. Several times already I've had someone walk through me right as I fire a rocket, which explodes on the back of their head, killing me. At least with friendly fire they'd die as well and maybe learn to stay clear of the guy holding a damn rocket launcher.

-The battle rifle feels wrong. I can't expand on that, it just hasn't gelled with me yet.
>> I can give them more freedom (because I know their programs won't compile if they don't line their types up

In what meaningful way can you give them more freedom? When i think about how i spend my time with junior folks, it tends to be on things like:

1. Do they understand enough of our problem domain that i can begin to describe a problem that needs to be solved?

2. Have they understood the problem i described? How confident am i that they're not going to implement a solution to the wrong problem?

We don't spend time on "hey, you passed the parameters in the wrong order here".

To put it another way based on my experience, what's more useful to a junior developer?

Option A: Hey, here's a test case, here's how to run it. I need you to change the behaviour of this component to do X instead.

Or

Option B: Hey, here's a component with well designed types. I need you to change the behaviour of this component to do X instead.

My experience has been that Option A - play with the component hands on, try things, run it, tweak the data supplied to it and observe the results - these encourage engagement. The developer will be excited even.

And for Option B, they'll be quite dejected, not that invested in the project. I can't even compile the stupid thing because of some cryptic compile error.
Probably a caching issue. I too was seeing "15 days ago", so I purged the cache (with &action=purge) and it now says "36 days ago".
Yeah, or:

Post::find_by_id(id).one(db).await.unwrap().unwrap().into();

I assume this project uses idiomatic Rust code. Is `unwrap().unwrap()` really necessary?

Things like this really make Rust unappealing to me.
Your `f(x)` example is similar to one of the harder examples I mention (but don't dive into) at the end of the blog post. You need a way to pass along information about `x` (such as its type) so that whatever you've constructed to model the body of `f` can use that information, should it need to. We have a notion of “scope stacks”, which live along side the symbol stacks, which we use to encode this kind of information. This early design doc goes into more detail about how scope stacks work, including a worked example that uses them: https://github.github.com/stack-graph-docs/

Dynamic modification of `__dict__` is definitely something that would be hard or impossible to track, depending on what kind of modification you're doing. If the keys are all string literals, then you could probably still get something approximate that's still useful. It's when the keys are constructed from arbitrary computation that it gets impossible, at least with the current stack graph framework. You'd have to have some way to lift that computation into the graph structure, so that the path-finding algorithm could simulate its execution. All while maintaining the zero-config and incremental requirements. https://twitter.com/dcreager/status/1467654252516589571
I often yearn for the "unearthly quiet" and structure of a monastic life. I am not religious but I just feel as if I don't belong in society: I don't care about work, jobs, careers, riches, fame. I would like a life of study, contemplation and silence.
HN has really embraced our current techno-pessimistic culture, so all the things that get on trashed here are definitely worth looking into. And no, I'm not joking. In the old days, HN had split brain, so things would both get trashed and celebrated - the famous Dropbox thread (https://news.ycombinator.com/item?id=8863)? The top comment is gently dismissive, but overall the thread is also quite encouraging. Twitter is much better, since you can still get the split-brain effect there, rather than isolating yourself in a negative echo chamber.

So fining headlines isn't hard, I think the real value these days, which didn't exist prior to YouTube becoming huge, is that now you can actually really dive into these things in a way that was incredibly inaccessible before.

Take self-driving cars: You'll see the usual dismissive crap here, but then you can go on YouTube and you can watch Karpathy talk for hours about how they're building their system. Then you can go watch someone like Yannic Kilcher talk about Karpathy's presentation, explain pappers on which the work is based, etc. Then you can go watch AI DRIVR test the latest iteration in the real world. Because there's so much content, you can basically find content at every level, from basic pop-documentary explainers all the way to lectures and paper analysis, allowing you to gradually go deeper and deeper.

Rockets and Space? Scott Manley and EverydayAstronaut will explain missions, engines, everything. SmallStars has amazing visuals. EVs? Sandy Munro will tear down an entire car and show you every single little thing in there. Electric Flight? "Electric Aviation" will explain the engineering tradeoffs between Lillium's small ducted fans and Joby's large propeller design. Biology? iBiology let's you dive into any current reserach (Synthic Bio, Connectome scanning, using DNA as structural material). You can just keep going like that for anything, it's just plain amazing.