Yes! There was a great Graphics Gems article on implementing quad trees. The things that change are the sheer number of things you might have in your environment.
End the end I gave up :-) The problem I was trying to solve was a physics based deformable environment. Something like minecraft but without the blockyness. Basically allowing one to dig as deep as one wanted into the planet, build as high as one wanted, and re-arrange as much as one wanted all with physics rules combined with some matter composition rules that would give one an 'authentic' experience. It was a stretch in the 90's and I think I stopped poking at it around 2005 :-). But part of the problem was when you broke things you got multiple sub-objects. Potentially down to the level of "sand" (which in my world was a .001cc chunk.)
If the goal is to make a CPU that is "fast enough to host H100 competitor AI hardware", then why bother with x64? Huawei could have just produced a powerful ARM chip to go with their new AI processor. After all, Nvidia GB200 also uses Arm-based CPUs (the Grace in GB).
It's a very complex system. Implementations cost hospital systems on the order of tens of millions of dollars. They have a near monopoly in the market. 2023 revenue was almost $5B [1]
DuckDB has certain optimizations which allows it to read only parts of a parquet file. It can also read remote file in streaming fashion so it does not have to wait for the entire file to be downloaded or to store a large amount of data in memory.
Relevant documentation: https://duckdb.org/2021/06/25/querying-parquet.html
It is understandable that you need to iterate quickly, but that should not be an excuse to not spend just 5 minutes to think through the potential scenarios.
Also, you can have a function to query an end point to find latest version available as a string, compare that to a const string inside the build, if they are different then invoke the auto-updater. Simple and light weight.
None. But I also have never costed any of the companies I worked for 8k due to 1 line of code. It was a constructive feedback, but hey take it however you will.
There is a fundamental difference between working in a company and shipping products alone as a solo person.
I did have 3 months of savings left and wanted to pursue my dream of creating a start-up.
I did create a fully working desktop app, a high-quality design for it, a landing page, an entire deployment infrastructure for the website, and uploading new version artifacts. While doing that, I was also taking care of all this marketing (30k unique website visitors a month on avg - analytics is public here: https://plausible.io/screen.studio). And a lot of other shit I don't even remember.
At the same time, you were working at a company where very likely at least one person was working on each of those areas independently, and most of the people did not give a damn if there would be a month delay in some area.
And then, you simply explain to me to compare version strings as if you've discovered a circle. WTF. It is a damn obvious thing, and it, of course, happens. The bug was about a whole different thing, but I'll not even try to explain it as I already did and it didn't prevent you from writing this bs. I wonder if you ever think how would you feel if your co-worker wrote a code review pointing out obvious things you did correctly, not related to the context of the PR at all, and ending it with "Simple and light weight." punchline. Maybe it would give your team an amazing opportunity for a long lunch break to discuss things.
this is really annoying, and this triggered me to write my challenging question.
I really doubt you'd be so "mistakes-free" and "I know it all" if you switched roles with your CTO for a week while all devs will take a week-off. If you write comments to solo founders so confidently, maybe you should consider that or if you're not willing to, to fucking think twice before writing comments next time thinking you're a guru because you nail your full time work.
Looking at the confidence you express your opinion (you actually don't express an opinion, you state your opinion as a fact), I believe there is no slightest thought like "maybe I miss something" or "maybe I'd also do exactly the same thing in this person shoes" and other shit like that.
I admire you for being careful and always thinking through all possible scenarios. On the other hand, I enjoy my life as a founder of a startup that has traction (and all its benefits of it). I'll risk betting that this difference is there precisely because you likely never make such mistakes, and you look at people who do from a perspective of "I know it all, and I'll tell you what you should do." ("Simple and light weight.") (note: it is possible you simply don't dream about founding a start-up which is totally fine. But even then, I believe it is a fundamental mistake to look at people who do create start-ups from the perspective of full-time-work and projecting your perspective on theirs)
--------------
I have no idea why the hell I even discuss with your "compare strings" wisdom. I just wasted 1 hour and half the emotional energy I have for this day and it's 9AM.
