Good attempt. What were the sources for these graphs? Orginals? Valmiki Ramayanam and Vyasa Mahabharata? Looking at Mahabharata's relationship graph on the website - it feels like it is incomplete. There are probably ~400 to 500 active named characters in Mahabharata (among several thousands of named characters overall)
Right now the data isn’t directly modeled from primary sources like the Valmiki Ramayana or the Mahabharata. It’s an MVP built quickly using curated summaries, so the graph is definitely incomplete.
Planning to expand coverage and move towards a more accurate, source-grounded knowledge graph over time.
And where did the stats come from? I find it very amusing & interesting & informative. I'm assuming you had the LLM generate these? That would be so interesting to see the prompts for!!
I am building localgcp - This is localstack / floci equivalent for Google Cloud platform : https://github.com/slokam-ai/localgcp - currently supports 14 services, including Vertex AI and BigQuery.
Part of building this, I decided to build a BigQuery emulator from scratch and learned a lot about GoogleSQL (previously ZetaSQL) along the way: https://github.com/slokam-ai/localbq
I plan to maintain and improve this going forward. The goal is to see how much can emulators actually do.
Ravana is a cross-platform desktop application built with Electron that allows you to use multiple AI assistants like Gemini, ChatGPT, and Claude in a single, organized, tabbed interface. It currently supports Gemini, ChatGPT, Claude, NotebookLM, Meta AI, and Perplexity.
Hey! I just noticed that! You're the first person to write in a different script, so it's not a problem I experienced until now. Will figure out a way to make the URL neater by default, although you can currently edit it as well.
Btw, I'm also Indian (from Goa) so it's amazing to see posts in one of our many regional languages :)
"Leadership is a privilege that can easily be taken away. The talented people who work for me have a plenty of options and can leave at any moment. I therefore treat them like unpaid volunteers"
I don't really understand what he means by this. Just beacuse you're choosing to have a certain job, or because you can leave, it doesn't mean you're not entitled to compensation. If that were true, anyone with any choice of job wouldn't receive a wage in exchange for his labour power.
Of course the people under him get paid (perhaps not by Satya himself), so what does he mean? That the leadership is unpaid? One would expect that leadership means a higher paid position, because leaders are applying a more specialised labour.
Am I looking at this the wrong way round, or being obtuse?
I think it means "treat them as well as you'd treat a volunteer doing the same job". The contrapositive (which I've actually had thrown at me in a past job) is "your employees get paid to do their job, they deserve no thanks beyond that".
Satya Is says that he wants to make his employees jobs fulfilling enough that people would want to do it. He's not really discussing pay at all. Of course he's getting paid and they are getting paid.
So I've worked near corporate people who obviously hated their jobs. Being in a team with such people is not a good thing for you or the project.
Similarly I was part of a volunteer team that formed ad-hoc to save a huge programing contest. Every person was there because they wanted to be there. It was a whole lot of fun and an effective team.
It means Satya has a privilege to be the leader, but that can be denied by his people if they leave, because there are plenty of opportunities, so that's why he treats them with extra respect - un unpaid volunteer is a way of saying the people are doing him a favor.
I have not used Boquet but going through their documentation it looks like they help developers to get rid of SQL by providing some Javascript plugin in order to filter the reporting data from the database.
SQueaLy's approach is a bit different. It is rather focused on writing powerful and dynamic SQL queries. SQueaLy uses JinjaSQL behind the scenes which gives you the power to use JINJA inside the SQL query. For more details, check out JinjaSQL here - https://github.com/hashedin/jinjasql
With JinjaSQL in the scene, you can access real-time variables related to
- A logged-in user
- Web session
- URL query parameters
inside your SQL queries.
You can then use Jinja templating inside the SQL query to handle conditional statements or create macros based on these real time variables
All this is nice, but once the SQL Server database crosses a certain size, there are things one needs to do like separating transaction logs, data files, tempdb files to separate disks for acceptable performance. I am not sure how that will work with SQL Server inside a container.
Yes, why else would you be running SQL in a container for if not for dev....10GB is fuck all, and it's nice having multiple versions of a large test (or sanitized prod) backup available locally, which can easily be greater than 10GB
The purpose of containers is that computers are now large enough that one computer can do the job of many previously smaller computers.
One your workload exceeds that of a normal run of the mill server containers are no longer a good idea. So basically once you start needing to do that which is mostly pointless now anyway with SSDs that would about the time when containers would also be ill suited to your workload.
Also, if you're running docker in prod, have fun :)
If you schedule it on Kubernetes as a pet set you could give each container a consistent virtual disk from your cloud provider. Of course... your cloud provider also has SQL as a service, so that's probably a cheaper option.
reply