bidandanswer
Joined 2 years ago
Joined 2 years ago
LLMs are clearly superior at presenting the information and have tangible room for improvement, whereas Google has regressed over the last decade and is getting more brittle by the day.
Open technology (LLMs) are going to offer much more robust and reproducible solutions to such questions as "here are my symptoms, what's wrong with me?" than Google.
You can nitpick my statements all you want and I will probably agree with you, but the overarching takeaway should be that LLMs are a much better solution, especially for laypeople who cannot use Google effectively.
This should be sung from the mountaintops. This concisely summarizes nearly everything that uninformed reader should take away from the comment section.
I mean, I love eBPF more than most, but this is a practical engineering solution to a logistical problem that didn't really need to exist in the first place.
This is not genius and not an order-of-magnitude improvement to an important computer science problem; it's an improvement to a costly artifact of the Linux kernel.
The point of it is that you can run user-defined programs while avoiding the costly context switch between user space and kernel space.
The kernel already is the kernel. Compiling kernel code to eBPF programs would offer seemingly no performance gains, since you're already in kernel space; there is no costly context switch to avoid.
This is huge for performance-sensitive code that executes against network packets: you don't have to context switch between kernel space and user space.
It's worth pointing out Solana's extreme competitive advantage over other chains is almost entirely due to it running on a variant of eBPF. †
This is an order-of-magnitude leap over other implementations and essentially the way you should do it, if you were to write it from scratch, aside from special purpose hardware fabrication.
† The second reason Solana is so fast is extreme parallelism: all accounts that are used in a transaction must be marked as either "read-only" or "writeable" before sending the transaction, allowing the runtime to parallelize all reads and only solve write contention when necessary.
Psychopath
That's not an argument. Name the problems specifically.
> Oh and while we are at it, remind me how to get majority of customers to pay in crypto who are used to just credit cards or wires
There are tons of off-the-shelf checkout flows that allow customers to pay in cash and companies to receive the funds on chain.
- 2.9% + 30¢ per charge
- Assume net-30 invoices
- Total fees: 2.9% * $250k + 30¢ * 12 = $7,253.60
- Stripe can freeze your money arbitrarily and indefinitely
Standard USDC fees on Solana:
- Less than 1 cent per transaction
- Total fees: < 12¢
What's your argument?
What's your point?
How valuable is 2.9% of $1m+ to you?
Two years ago I had to fend off contracts that paid in USDC.
It's easier to find someone to pay in USDC today than it was then.
Market share and volume will continue to grow.
What do you have against a genuinely useful technology with tangible benefits?
- Cheaper
- Faster
- No arbiter risk
- Built-in escape hatch for political dissidents and enemies of the state
If you want a trusted arbiter for all your financial transactions, you can continue to use the legacy financial system and pay the costs for doing so. I'm not arguing crypto will replace it. Both have their use case.
Post a $$$ price at which you promise to answer questions.
Ask questions with posted $$$.
Upvote and downvote to establish reputations.
Eternalized on distributed file systems.