branko_d

7 ms·

1.
by branko_d 21d ago
What Andy (Grove) giveth, Bill (Gates) taketh away.
2.
by branko_d 28d ago
Is this a case of of Qualcomm commoditizing their complements? Does Mojo have a potential for disrupting Nvidia's current market position? https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
3.
by branko_d 1mo ago
I feel this could be solved by crowdsourcing, assuming the support from the major phone manufacturers and possibly governments. - After a call from an unknown number concludes, the phone could offer an option to the user to mark it as &quot
4.
by branko_d 2mo ago
Sure, but it can still have hyperinflation.
5.
by branko_d 2mo ago
On a related note: Visual Studio still has dialogs that cannot be resized, even after years of people begging Microsoft to make them resizable. Shouldn't this be a trivial fix for AI? I'll believe in AI when I get to resize my Con
6.
Curative ditched a $600k-a-year Salesforce contract after vibecoding a CRM(businessinsider.com)
5 points by branko_d 2mo ago|3 comments
7.
by branko_d 3mo ago
In OLTP, it's very difficult to guarantee correctness with triggers (very easy to have a race condition in concurrent environment). On a flip side, materialized views tend to lock more than you'd expect, especially when aggregates
8.
In 1973, eight healthy people feigned a single hallucinatory symptom(spacedaily.com)
3 points by branko_d 3mo ago|0 comments
9.
by branko_d 3mo ago
You can have it in one place without using background sync. Our application uses classical "foreground update" paradigm, but each API call automatically shows an error to the user and returns him/her to the same place where
10.
by branko_d 4mo ago
I think a lot of it is down to Windows, not Prism itself. For decades, Windows made it too easy for games and even some application to install drivers. Windows games use drivers for anti-cheat (and historically for copy protection too). Nei
11.
by branko_d 4mo ago
Itanium was arguably not superior. The assumption behind it (that the compiler can bring order to the chaos) was wrong, making it slower, more expensive, and less efficient than x86 in real-world scenarios.
12.
by branko_d 4mo ago
No. Palantir, possibly the most overvalued company on the stock marker, has P/S 63 and P/E 144. Nvidia has P/S 21 and P/E 33.
13.
by branko_d 4mo ago
Sounds like HPE GreenLake.
14.
by branko_d 5mo ago
From https://kristoff.it/blog/contributor-poker-and-ai/ : "Unfortunately the reality of LLM-based contributions has been mostly negative for us, from an increase in background noise due to worthless drive-by
15.
by branko_d 5mo ago
This is just a footnote in the article, but is incredibly important, IMO: ”There’s a risk that codebases begin to surpass human comprehension as a result of more AI in the development process, scaling bug complexity along with (or perhaps
16.
by branko_d 5mo ago
The wording "outside of transaction" irks me. Everything in a relational database is done within a transaction, the only question is whether it's the transaction you think it is, or some other. I believe this is largely an
17.
by branko_d 6mo ago
Dave Cutler and his team are a clear counter-example. They famously shipped Windows NT with zero known bugs, which clearly brought enormous shareholder value. The problem, of course, is that this sort of thing doesn’t bring value next quart
18.
by branko_d 6mo ago
I think this is especially problematic (from Part 4 at https://isolveproblems.substack.com/p/how-microsoft-vaporize... ): "The team had reached a point where it was too risky to make any code refactoring or engine
19.
by branko_d 6mo ago
If memory serves, Windows 2000 was the last version where search worked reliably. It was a simple linear search through files which could take a while on larger folders, but was reliable and predictable since it did not rely on a background
20.
by branko_d 6mo ago
My guess would be bad hashing, resulting in too many collisions.
21.
by branko_d 7mo ago
> often you have to inject data into new tables or columns No tool can help you with that, simply because this kind of data migration depends on your particular business logic that the tool has no way of knowing about. While SQL Server D
22.
by branko_d 8mo ago
> Boolean is rarely enough for real production workloads. You need a 'processing' ... 'retrying'... 'failed' ... If you have more than 2 states, then just use integer instead or boolean. > Saving a few by
23.
by branko_d 8mo ago
Why use string as status, instead of a boolean? That just wastes space for no discernable benefit, especially since the status is indexed. Also, consider turning event_type into an integer if possible, for similar reasons. Furthermore, why
24.
by branko_d 8mo ago
That's true for seeks into the clustered (primary) index because that index includes all fields, so you don't need to "jump" to the heap to get them. However, seeking into a secondary index, and then reading a column not
25.
by branko_d 8mo ago
For inserts, you cannot escape writing into the base table and all indexes. However, my understanding is that for updates PostgreSQL has a write amplification problem due to the fact that each time a row is updated this creates a new row
26.
by branko_d 8mo ago
Yes, and the newest Panther Lake too! https://techtime.news/2025/10/10/intel-25/
27.
by branko_d 8mo ago
On the other hand, if the compiler can prove at compile-time what type the object must have at run-time, it can eliminate the dynamic dispatch and effectively re-enable inlining.
28.
by branko_d 10mo ago
But only if they stand. If they start driving, the situation changes dramatically!
29.
by branko_d 10mo ago
Tragedy of commons.
30.
by branko_d 10mo ago
Is there anything especially hard about decompiling (to) Java? .NET/C# decompilers are widespread and generally work well (there is one built into Visual Studio nowdays, JetBrains have their own, there were a bunch of stand-alone tools

More ›