cjg

What happens when the REST server accepts your POST to /api and starts processing it but then, before the response can be sent, the connection drops? This code would see an error from the POST to /api due to a connection failure / timeout, and the transaction rolls back.

Now you've got the /api invoked, but no DB write.

Calling on the official number is a good rule. But my neighbour followed that and was still scammed for tens of thousands.

The critical extra step that they missed was to check that the line was disconnected before calling out. They were using a landline.

The scammers called them, but didn't hang up. Then, when my neighbour called out to their bank, they pretended to be answering that call - going through security, etc.

My neighbour then did whatever the scammers said - because they couldn't possibly be scammers.

And then when two of the nodes die at the same time...?

It's predicated on accelerating technological progress, which can perhaps be seen to be true by looking back at how quickly society has moved through different technological regimes. Once change becomes too fast, it's impossible to predict what is about to happen. It's called "the singularity" with a loose analogy to black holes where a big curvature means that light cannot escape - with fast enough technological progress, the immediate future is highly uncertain.

The most commonly expected way that this might happen is via AGI - perhaps with self-improving AI - where a sudden increase in AI abilities might drive extremely rapid technological change.

That was the video I watched and I just don't get what is different about polylith.

The video spends too long telling me things I already know - e.g. what are functions / objects / layers / etc.

Tell me something I don't know - such as what makes Polylith unique. The video says this is "Components". Well what's so different about those? They sound like microservices or perhaps high-level objects. Or perhaps interfaces.

Show an example!

Try this link from that page: http://www.sleepisdeath.net/slideShow/

Yes.

429 is only applicable if it's the same user sending all the traffic.

503 explicitly mentions server overload.

Most of the answers to this question seem to make the argument that you could not automatically generate safe Rust wrappers for an existing C library because it would be impossible to automatically know the safety requirements for a C API.

That's also true, in general, for C++, but CXX is nevertheless attempting to solve that problem.

CXX requires you to give some extra information when declaring the bridge. Presumably that can allow things to be less automatic.

I'm guessing that the reality is that if your C++ code is relatively idiomatic then CXX will work with it, but stray too far from idiomatic C++ - i.e. towards a C-style interface and CXX won't be able to do such a good job.

But it would be good to hear something more definitive.

I meant generating a safe Rust API for existing C code rather than calling an existing Rust API from C.

Given that C is a subset of C++ (meh), can you use this to generate safe bindings for C?

Most C integration recommendations I've seen suggest using bindgen, but that doesn't give safe bindings.

Iron pans are not the best for those with hemochromatosis (iron overload).

The idea is that it's not a sudden hard failure. Instead only a few things fail which helps in two ways: reducing the load by discarding some work and alerting that the system is beginning to be overloaded.

It's probabilistic.

I just finished implementing a simple backpressure algorithm. Once the queue is more than a certain percentage full, it rejects new items. These rejections get turned into HTTP 503s.

Do you have a link to an article / report about that 138 byte program? I'd be interested how to achieve that.

"8. Source: My Ass" :-)

> While Rust does have a steep learning curve, nearly all the engineers we've worked with have experienced a productivity increase from using it. Freedom from type errors and data races is a huge productivity boost on complex projects.

We can already see how the laws of physics might accommodate energy not being conserved - and from there a small hop to perpetual motion machines.

Energy conservation relies on time translation symmetry. In other words, that the laws of physics do not change over time. Well, perhaps they do change slowly.

A prime example of this is the expansion of spacetime, which can reduce the energy of a photon travelling through empty space - it's redshifted. This has been experimentally observed.

See https://www.preposterousuniverse.com/blog/2010/02/22/energy-... for more details.

More details here: https://blog.rust-lang.org/2021/11/01/cve-2021-42574.html

Location: Cambridge, UK

Remote: Yes - preferred

Willing to relocate: No

Technologies: Rust, Java, Linux & lots more

CV: I will send it to you, if I'm interested in a role

Email: It's in my HN profile

I've got decades of experience as a software engineer. Most recently I've been doing a lot of Rust - picked it up in 2015 - and that's a technology I want to keep in my next role.

What does it mean for a novel to be of high quality? It's not easy to define and it's somewhat subjective, but equally there are definitely things that are not acceptable.

Some things that can help move towards higher quality code: - avoid duplicated code - especially when it's similar but subtly different - variable names that mean something useful - lower code nesting - shorter functions - fewer parameters

Many of these things are focused on improving how understandable / maintainable the code is.

But, as for novels, there aren't just rules you can follow blindly.

Perhaps this helps: https://garywoodfine.com/what-is-clean-code/

Game of Life has the hashlife algorithm that can provide exponential speed-ups but with increased memory usage.

A computer in the Game of Life therefore implies there is an algorithm that can exponentially speed up arbitrary computation - again at the cost of memory overhead.

Does this say anything towards P=NP or other complexity questions?

It also refers to https://chrisparnin.me/pdf/Debugging-Hiring.pdf

Well our product was already something that included the openssl library, so we would have had to release a new version of our product when there's a patched version of openssl anyway.

At least updating it is easy now - we've put a lot of effort into that process recently.

Yes - used rustls on a new project rather than the openssl wrapper which we used before. The experience has been pretty good. The problems of shared library version inconsistency have gone. No noticeable downsides.

I'm on Windows.

For me it's the comms apps (e.g. Teams). These tools are selected at the team or corporate level. Whilst they typically have Linux support, the Linux implementations tend to have many more bugs and fewer features. If I'm in a call and someone's screen is frozen or they drop off unexpectedly, they are usually using something non-Windows.

But I do my day to day development in a Linux-like environment - either docker, WSL or a VM.

I would prefer to be linux native, but not at the cost of being a second-class citizen when interacting with the rest of my team.

Minor nitpick - kamma and karma are the same thing, but different languages. Kamma is Pali and karma is Sanskrit.

To be even more detailed, karma is the action rather than the effect, which is called karma vipaka. The English word karma means something more fluid - depending on context.

I agree with your conclusion of increasing the length of support. But your half-life analysis isn't really the right choice. Hard drives tend to have a bath-tub failure rate: https://en.wikipedia.org/wiki/Bathtub_curve