131 karma · joined December 21, 2011
Be the first hire, working with me, combining LLMs, geometry, and manufacturing in a high-agency, high-trust environment. You’ll have significant ownership over your work, freedom to experiment, and direct influence on the direction of the product.
A wide range of technologies to work with: vllm / React / Postgres / CGAL / OpenCASCADE / Eigen / express
team@camypro.com https://www.camypro.com/
I think my system is sort of both. I want to put some events in a queue for a finite set of time, process them as a single consolidated set, and then drop them all from the queue.
I need a durable queue but not indefinitely. Max a couple of hours.
What I want is Google PubSub but open source so I can self host.
I'm checking out the list.
Performance isn't a big deal for me. I had assumed that Kafka would give me things like decoupling, retry, dead-lettering, logging, schema validation, schema versioning, exactly once processing.
I like Postgres, and obviously I can write a queue ontop of it, but it seems like quite a lot of effort?
Clearly the pressure on government to write these laws is coming from somewhere. You should engage with the arguments the other side makes.
When I told them I (as a 5 person business) obviously don't have time to go through 1000s of old emails they reacted with surprise to the amount of emails. I guess they don't send many. They didn't offer any other solution.
As others have mentioned this org is a tax on all UK business.
I am reflecting on Deepmind. This company saw the AI revolution before anyone else. London based. They did an amazing job. Sold to Google. The problem is that long term the growth and money now goes back to the US. Maybe the UK is just too small to produce world leading companies.
www.roadcount.com
Memory size is an interesting example. A typical Kubernetes deployment has much more control over this than a typical non-container setup. It is costing you to figure out the right setting but in the long term you are rewarded with a more robust and more re-deployable application.
I've only used it managed. There is a bit of a learning curve but it's not so bad. I can't see how it can take 4 months to figure it out.
2. Put it in a Ethereum transaction.
More seriously, I have no idea.
https://support.apple.com/en-gb/guide/deployment/dep28afbde6...
To do TOR you would need to look at the IP protocol and signing at the packet level. Definitely more difficult.
1. Give my name and address to activate a device 2. "The internet" requires authentication via the HSM.
How is it different from now when you can record a conversation you have? or forward an email to the police?
However I have an unpopular opinion, interested to hear what others might think:
We should eliminate anonymity online. If you go on the internet everything you do should be tied back to your name. This can be done using device attestation. Everyone gets a private key tied to their name/address.
This is compatible with free speech. In fact it promotes free speech because being a "troll" becomes a lot more personal.
I think this way of living would be closer to our nature as tribal primates. It would improve behaviour and overall quality of life. Our brains are designed to have checks and balances from wider society which you don't get anonymously online.
This would also reduce the need for govt monitoring because any chat online could be "turned in" by an informer and then any criminals identified.
The thing is that the original post never said they wouldn't do this. The post asked for resources and industry best practice. For all we know they would use this information with discression and practically.
You touched a nerve because I get deeply frustrated by the attitude in manufacturing where process knowledge is not readily shared like in software. The reality is that many business are not best practice.
Any subject worth learning has depth to it. Nothing worth knowing can be fully understood in a short period of time. That doesnt mean you cant start today.
This response is negative gatekeeping.
This kind of change is difficult to make without mistakes because it silently changes the assumptions made when code calling dict_put() was originally written. ALL call sites would need to be audited to ensure they are not overflowing the dictionary size.
The diff I am referring to is here:
https://git.tukaani.org/?p=xz.git;a=commitdiff;h=de5c5e41764...