HN user
for inquiries: tu8s1wx1y@mozmail.com
last month I spent almost 10k USD on tokens. It sounds so insane
It is. That kind of money would change my life and this guy spends it on prompts that "really force him to think".
I use LLMs. So far, 20 bucks per month has me covered. I hit the limit sometimes. I just take a walk. Forces me to think.
C++ compilers do this too, thats why so many to-be-linked symbols start with "Z"
addressing any of the points would require locking the AI down and making it less general and less "agentic". Your concerns make sense if you look at the AI as an information retrieval engine.
- why is single URL crawl with 20+ redirects not flagged as problematic and/or aborted?
- why is a query about a coffee place based on its public URL even seeded with the users' context and confidential information?
- why dont they just look up the coffee place on a trusted source like google maps and continue from there?
- why is the basic "social" engineering style attack working?
- why is the cloudflare impersonation not challenged if the website is clearly not from cloudflare and there are zero references from cloudflare to this website in the training corpus?
Prompt injection (or llm social engineering" is fundamentally unsolvable, though with training its effectiveness can be reduced
the optimal crime rate is non zero and the same goes for traffic death rate, because to bring them to zero would imply a dystopia where personal freedom is seriously limited
:set {:job "Engineer"}
:where |(= ($ :job) "Developer")
Is there a nautical map equivalent of osm or organic maps? One that emphasizes waterways by drawing them thicker when zoomed out like regular maps draw roads thicker? Plan routes over the water? Even google maps lacks a nautical layer.
Because you can deduplicate certain parts of the logic which make the whole thing less error prone, such as
if c
x=1
else
x=2
The ternary expression also takes up much less space so there is less of an emphasis on it, this can be a stylistic tool in a programmer's toolbox
tldw:
- wider wheels are marginally less efficient but almost negligible
- rims with larger diameter have larger air resistance. Probably because the rim patterns intersects the air in weird ways but it's not explained. Tire walls are relatively smooth, so tires with higher aspect are way more aero-efficient despite having more marginally lower rolling resistance.
“I have seen people technically meet the 30% rule and still feel financially strained,” shares Linda Grizely, a certified financial planner and financial wellness speaker. “The pressure isn’t the rent alone; it’s the combination of rent plus everything else in their financial life."
Why would the company pay more when they can just not pay more? The only things I can see happening is they might lower prices as competition ramps up, or in general as there is more supply for the same cost.
Everyone else will be 5% more productive. Then no one is "more" productive. So everyone has a higher output, but the same wages and hours worked. There was only a gap when usable AI first came out, some contractors could do the same quantity of work in less time and enjoy time off or do more jobs. Now the gap has closed or is closing. And using AI now is more about not being less productive than peers who do use it.
I want it to cause a traffic accident. If I'm going down, so is everyone else. I'm already dying anyway. Grok 10000%
The issue is how easy computers make everything, and how well processes scale with computers. Back in the day to heist data you'd have to physically break in or infiltrate, rummage through files, copy them somehow or just straight up take them. In a briefcase?? How many files can you exfiltrate per day like that?
But on a database it's practically a matter of running a copy command and uploading it or exfiltrating it. And there will always be software vulnerabilities.
Computer processes have no inherent rate limiter to them, and they even allow you to run stuff from a distance.
I agree. I tend to use the gnu "asprintf" which simply returns a properly allocated char buffer with the formatted string in it. And on platforms that don't feature asprintf (windows) you can build your own using sprintf!
The accumulator pattern keeps simulations stable in the face of variable frame rate. Accumulate the frame dt into an accum variable. If accum>fixed_physics_dt then step_physics until false. I'm assuming the author did something like that because it's standard practise.
I'll change your mind:
If you pass NULL as the destination pointer, it doesn't write any string. If you combine this with %n at the end of the format string, you can get the exact length that the output string would be. Then you allocate that, then you print again, into the actual destination buffer this time.
what happens when ALL the stocks have been bought back? what is the natural conclusion? you get extra points if you mention dilution i.e. oops we turned on the ~~money~~ stock printer and your stock is now actually worth less!
That's just dividend stocks with more shady. We promise to invest the dividend you would have gotten into ourselves to become more valuable bro. But that will only be reflected in "valuations" that don't directly affect your bank account. It is still the greater fool theory.
The worst is growth stocks that are a wrapper around actual dividend stocks. Beyond number going up, what actual concrete utility are you getting? Beyond waiting for the line to go up to eventually sell it to a greater fool, what can you _actually_ do with it? It's not real.
It is only real because enough people believe it is real. And they believe it because they want to believe it, because they are greedy and want easy money.
Once the market tanks and the greed turns into fear, there will be bagholders and the brokers will be laughing. The people who skim fees and percentages will be cozy.
"Now is the time to invest" they will say, because from here the line can only go up! And it will, eventually, because people want to believe, because they are greedy.
The only thing the stock market makes money on is greed. That is the thing that drives stock value. Not the economy.
not concerned about the actual economy.
Why would it be? Non dividend stocks only have value because other people think they have value (i.e. greater fool theory).
Only dividend stocks have some base value connected to how well the company does. (Higher dividend if it does well, lower if it does poorly.) But they still also have a lot of "greater fool" value.
Beyond dividend, stocks have no intrinsic value. Nowadays you don't even get a piece of paper to wipe your ass with anymore, it's all digital.
HaikuOS got this right. Tabs are a property of the OS side of the window, not the application side
More efficient in terms of bandwidth (not) used. More costly because it has to be stored somewhere instead.
Are C++ concepts not enough?
You wouldn't have spent that time with loved ones, you would have been doing other tasks. Just like now, we no longer need to wait for programs to be submitted compiled and ran on the mainframe, we don't get that time for ourselves.
What does it mean to be friendly to memory bandwidth, and why does C++ excel at it, over, say, Fortran or C or Rust?
In my experience fiddling with compute shaders a long time ago, cuda and rocm and opencv are way too much hassle to set up. Usually it takes a few hours to get the toolkits and SDK up and running that is, if you CAN get it up and running. The dependencies are way too big as well, cuda is 11gb??? Either way, just use Vulkan. Vulkan "just works" and doesn't lock you into Nvidia/amd.
Assemble a navy in space then just airdrop it through the atmosphere?
Is a moral compass something you can teach someone in a short course if they have been lacking it so far in their entire lives?
You say "seems like", can you argue/show/prove this?
As a developer who spent a couple months developing a microservice using aws lambda functions:
it SUCKS. There's no interactive debugging. Deploy for a minute or 5 depending on the changes, then trigger the lambda, wait another 5 minutes for all the logs to show up. Then proceed with printf/stack trace debugging.
For reasons that I forgot, locally running the lambda code on my dev box was not applicable. Locally deploying the cloud environment neither.
I wasn't around for the era but I imagine it's like working on an ancient mainframe with long compile times and a very slow printer.