Could prompt tools like this use TUI-style features to edit the displayed prompt after releasing it back to the user? So if kubectl, git, or aws cli takes 200ms to finish it doesn't matter, the data from the output of these commands will appear a few moments after the prompt has been released to the user, so the user doesn't feel like they're waiting for the prompt to be ready.
Hurl has been great for testing in my RAD templating web server project. Like dm03514 says itt, 'The hurl-based tests really help to enforce the "client" perspective.' It's packaged for 3 application environments including a docker image (x2 archs, x3 oses) and with Hurl its easy to ensure the tests pass at the client level in all three environments.
It would be nice to have fancy-regex; today I tried to write a regex to match a case like this ~ <link href="/assets/reset.css\\?hash=(.*)" integrity="\\1" rel="stylesheet"> ~ but the regex crate (and thus hurl asserts) can't do backreferences so I guess I'll just live without checking that these two substrings match.
I wish there was some way to test streamed updates / SSE. Basically, open a connection and wait, then run some other http requests, then assert the accumulated stream from the original connection. https://github.com/Orange-OpenSource/hurl/discussions/2636
Pretty sure my commenting pattern is similar. I write a bunch of comments in a short period then none at all and just lurk for a while. All the HN comment data is published, right? (BigQuery?) I wonder if we can find cyclic comment patterns for individual users. It might be harder to find patterns if the user creates a new account every cycle like parent, but maybe just users that have been active for 2+ years.
That’s also occurs with me, but in games! Sometimes, I feel “obligated” to play, the urge of playing that unique game, then suddenly, it disappears.
I’m not a psychologist, but I believe that occurs often, some things just lose that sparkle with the time, and it’s okay, you just need to find a new way to make your task. This article is a good example of how you can do this, and, with some time, change your methods!
I believe that having urges come and go is the natural way human motivation works. Doing something every day, whether you feel like doing it or not, is the artificial thing that you need to be trained to do.
Some things require larger blocks of time. For example, you need several days in line to take a vacation; you can't simply take "5 minutes of vacation" every day. Some things are done much better if you dedicate an entire day, or at least a few consecutive hours to them: whether it is learning something new, writing a blog article, relaxing, hanging out with your friends, etc.
It would be more natural to work 16 hours a day when you feel like it, and then take a day off.
Thanks for clarifying cadmium's status and offering your take on the state of truck and fornjot. So, what happened with cadmium? Is Truck just too primitive to build on top of so far? It looks like both of these kernels are actively being developed, what do you think of their rate of progress?
No idea where truck is going, it'll take me quite some time to tinker with CAD I think, it left me quite a bitter taste...
Fornjot seems to be doing good, I'm donating to them and I get regular updates (you should too!). Still, there's a long, long road ahead
If I were to do this all over again I'd either go the OCCT route (like chili3d or zoo) or solvespace. they're both "lacking" kernels if you compare them to the commercial ones, but I think there's enough "market gap" for makers that would prefer a sustainable CAD format instead of perfect fillets (and IMO freecad is not the solution).
Keep in mind though that my efforts where laser focused on non-math stuff. From what I gathered from my time in cadmium, b-rep kernels are hard in an unsustainable level. Browser level unsustainable. I just hope that out of seer necessity we'll find another way to solve the CAD problem, instead of a b-rep kernel
Burn it with plasma gasification to reduce it to the simple molecules to eliminate all the pollutants. CO2 is a much smaller and easier to manage problem than plastic waste.
> CO2 is a much smaller and easier to manage problem than plastic waste.
By what possible measure? Despite clear, well documented science, including very clear dire economical impact, and all within an extremely clear and short term time frame, with escalating effects already visible literally everywhere in the world, we have had almost 0 progress in combating global warming. The best we've done is slowing the rate of acceleration - as in CO2 release is still accelerating, just not as much.
Plastic waste has environmental impact, especially in the oceans, but nowhere near to the level that 2-3-4 degrees warming will have. And that is what we are currently on track for by the end of this century.
I've recently started rewriting basic process documentation into markdown, which also needs to be printed with a simple header and footer. I found that rendering to html, adding pagedjs cdn, and adding a styled header & footer tags looks and prints great already.
It's surprising how close html & css are to being a pretty good layout system.
You know it's a good post when it starts with a funny meme. Seems related to the recent discussion: $20K Bounty Offered for Optimizing Rust Code in Rav1d AV1 Decoder (memorysafety.org) | 108 comments | https://news.ycombinator.com/item?id=43982238
Because wage stagnation is literally the Federal Reserve policy for the last 20 years.
The fed treats wage growth as a leading indicator inflation -- even though anyone with a brain knows that wages are the last thing to go up in an economic cycle, so if it's anything it must be a trailing indicator -- so when wages start to rise up the fed responds by increasing interest rates. Raising interest rates kills wage growth, as intended.
tl;dr: slam the economy every time wages start to go up for 20 years -> "why haven't wages gone up in 20 years" surprise pikachu face
That doesn't match what the article is talking about, though. According to the article, the 20 years of wage stagnation was '73-'94—not the last 20 years.
This really has been Fed policy for much, much longer than 20 years. It's been known since the stagflation associated with the 1973 oil crisis that it doesn't really work very well, but it's practically the only lever they have, so they keep using it.
I wonder how this compares to KBLaM [1], which also has a preprocessing step to prepare a large amount of reference material for direct access by LLMs. One obvious difference is that it has a modified attention mechanism they call "rectangular attention". The paper was posted on HN a few times, but it hasn't generated any discussion yet.
reply