Interesting. Is Kubernetes ever used as the orchestrator in HPC workloads, or rather are even containers used there? Also what are some good resources to get better at kubernetes? Currently I am mostly playing with managed k8s like digital ocean's and thinking about transitioning to k3s based bare-metal solution. So, I would really like to learn what's the right way of doing this.
Hmm, makes sense. Does same principles also hold while rendering the movie? The 80/20 rule will be harder to maintain because assets can change frequently and unexpectedly during production. But I guess the need for the data to geographically replicated, with fast and easy access, remains (especially during these remote times). During those times, is s3 a still good enough choice or do you want something more robust so your rendering process is not bottlenecked by io.
I am actually curious about the details, especially the cloud storage. What kind of storage makes sense in this kind of infrastructure ? Is it just regular block volumes being mounted as ext4, or is it something more k8s-ish solution like longhorn or openEBS? I recently started learning and maintaining a k8s cluster, so I tend to really enjoy this kind of content. Will be really looking forward for the January talk.
Also, Turkey Leg and Mmm The Peas are both masterpiece.
Really enjoyed that. I think I will also really enjoy a longer version that talks a little bit more concretely about the tech stack being used. Also, not sure if the qr code is just prop or not, scanning it didn't work.
Yep. That's another thing that I really liked about the talk too. Its very approachable and shows how fun programming can be, especially since coding can appear a bit dry and mechanical to others.
For me, it was Art of Code by Dylan Beattie, but mostly because that talk has the best ending[0] I have seen. Also, introduced to me a side of programming that I instinctively knew existed but never sought out.
Because trust has a social aspect to it, along with technical. The tech may exist, but it is going to be quite hard, if not impossible, to explain to an average person how cryptographically verified evidence of the piece of information is better than the person just accessing said information.
That's what I hoped to do with the original comment. I didn't want to send them an email for something this trivial and I was just leaving the comment in case anyone from Anandtech stumbled upon it. The typo is not really an issue and my comment was not a criticism. I was just trying to be helpful but I can see how that can appear to be when my comment is just about the typo and not the content of the post.
Honestly I don't mind. I was not commenting on the quality of the post, neither was the typo that much of an issue. I have seen people from Anandtech active in the hackernews and I just this is a good way of reaching them and letting them know something trivial with their posts.
I am confused about one thing, in multithreaded scenarios, can an application use 8 threads or 4? Also how does the scheduling work, can I pin a task that I know will be demanding on the firestorm cores?
So I am always curious, are there any laws that makes it mandatory to expose a data dump whenever you come across one or it depends on the goodness of their heart to report it? I guess even if there is a law like that, it would be hard to enforce.
Ah didn't mean it in the sense that it was inevitable because he had Covid, more like it was inevitable since his condition has been deteriorating at a slow but steady pace over the past few weeks since he was hospitalized.
A sad but inevitable day. He was one of the last remnant of a by-gone era in Bengali films, when even a budget-constrained industry like ours gave us works that even today are counted among the greats.
So, all of these new Macs have the same SOC across the board? Or will there be slight differences like the Macbook pro will have a higher-binned soc or maybe the Mac mini and Macbook air will have fewer graphics core?
For many users that can be an alien experience. For most non-technical people, browser is still primarily for accessing contents on the web and switching them to a user experience where you have to start a backend server locally and then access it via the web browser can just feel hacky and even a bit off-putting.
Hmm, if I am understanding correctly, it's not just about changing the runtime model of the eventloop for languages like NodeJs but also we need fundamental change in our hardware interacts with software.
If you want to register a company in India, its a convoluted maze of red tapes. While there have been a lot of improvements, the experience still leaves a lot to be desired (anecdotally). And while the govt postal service is exemplary, its hardly the norm. Yeah it is a glorified hosting service with reviews and I am not worried about the technical capability of the government, I am worried that the 'babu' culture of India will make this simple thing needlessly complicated.
I am not sure how I feel about the government being directly involved in creating the app store. On one hand, I believe the government should take measures to nurture the local startups and app, to give them a fair chance at growing. On the other hand, I don't think an app store created and managed by the government will have the right incentive to be competitive against foreign players and may just end up spiraling into a hot bureaucratic mess, with more and more hoops to jump through just to get an app on that platform.
I believe books and libraries are more important than they ever have been in recent times. Whenever you go and read a book from your library, you librarian doesn't keep a profile of who you are and judges your value based on what books you read. Books are still the best way to expose yourselves to new ideas and libraries are still the cheapest ways you could discover those ideas because your library is not earning by showing you an ad for each book you read and hence, its not in their interest to trap you in a bubble that echoes your own bias.
I am still a bit confused. Will this ID be different from the object id of for accessing the Durable Object, essentially in this case we would be using the Durable Object as a key-value storage? Or is it like the Namespace is separate from the Durable Object and each Namespace can have multiple objects of the same class under?
Edit: I think I get it now. Sorry I misunderstood that each Durable Object is like a singleton for the class you define. Its the other way around, you have the definition and namespace and then you can create a new object from those whenever you need it and this one would unique and accessible across all workers.
Right, that's what I got from the Unique explanation in the doc. What I am confused about is this part:
With Durable Objects, you instead design your storage model to match your application's logical data model. For example, a document editor would have an object for each document, while a chat app would have an object for each chat. There is no problem creating millions or billions of objects, as each object has minimal overhead.
What does it mean that a document editor will have an object for each document? Will I have to create a new UDO each time a new document is created?