For me, avoiding heap, or rather avoiding gc came when I was working (at work) on backend and web server using Java, and there was default rule for our code that if gc takes more than 1% (I don't remember the exact value) then the server gets restarted.
Coming (back then) from C/C++ gamedev - I was puzzled, then I understood the mantra - it's better for the process to die fast, instead of being pegged by GC and not answering to the client.
Then we started looking what made it use GC so much.
I guess it might be similar to Go - in the past I've seen some projects using a "baloon" - to circumvent Go's GC heuristic - e.g. if you blow this dummy baloon that takes half of your memory GC might not kick so much... Something like this... Then again obviously bad solution long term
The content of the stack is (always?) known at compile time; it can also be thrown away wholesale when the function is done, making allocations on the stack relatively cheaper. These FOSDEM talks by Bryan Boreham & Sümer Cip talk about it a bit:
Different people have different levels of internal monologuing or none at all. I don't generally think with words in sentences in my head, but many people I know do.
Internal monologue is a like a war correspondent's report of the daily battle. The journalist didn't plan or fight the battle, they just provided an after-the-fact description. Likewise the brain's thinking--a highly parallelized process involving billions of neurons--is not done with words.
Play a little game of "what word will I think of next?" ... just let it happen. Those word choices are fed to the monologue, they aren't a product of it.
If LLMs cannot reliably deal with this, how can they write reliable code? Following an instruction like "don't do X" is more basic than the logic of fizzbuzz.
This reminds me of the query "shirt without stripes" on any online image/product search.
Obligatory reminder that we used to live in a world where you could put "foo -bar" into a search engine, ctrl-F for foo on the top ten results and find it every time, and ctrl-F for bar on the top ten results and not find it.
Yeah, I've even had cases where DDG ignored my quoted string in the search. It's literally the whole point of the quotes but especially when it contains things like German umlauts it'll just accept any replacement letter for them. And yes, getting no results is acceptable, in fact it is the only correct outcome.
My eureka moment when I first started using Cursor a few weeks back was realising that I talking to it the same way I talk to my three year old and the results were fairly good (less so from my boy at times).
Yeah it's also kind of funny people discovering all the LLM failure modes and saying "see! humans would never do that! it's not really intelligent!". None of those people have children...
They don't. At least not for the duration that LLMs keep it up. They really don't.
If you want to pretend that being a 3 year old is not a transient state, and that controlling an AI is just like parenting an eternal 3 year old, there's probably a manga about that.
Maybe because none of those people are imagining children to be eternally stuck at that level of intelligence. At that age (regardless of being a parent or not) you can literally see them getting smarter over the course of weeks or months.
That's a great question, we were very concerned about the extra complexity Bazel was going to add to the daily workflows. We were able to hide most of it from most engineers. For the platform team however, the learning curve was brutal. In fact hired external expertise to consult us and answer our questions
That's how I feel about keyboard tilts away from a full pronation/flat and towards a neutral position. Once I switched to having a rotated split keyboard, my forearms and wrists felt incredible, and I hadn't even considered them uncomfortable before.
There was a price increase, but there was also an explicit elevation of Disney+ from a "Pressure Target" to a "Priority Target" of the BDS movement last December.[1]
I know anecdotally dozens of people, including myself, who have made the sometimes difficult decision to cancel Disney+ subscriptions to avoid crossing the picket line. I haven't heard anyone making a fuss about the price increase, specifically.
Many cage free chickens are also free range chickens, where they can roam outside. That massively increases their chances of picking up the bird flu, as opposed to those they are inside all day.
I'm not advocating for one or the other, just explaining. Even cage free chickens will come into close enough proximity where they will all die if just one chicken picks up the flu. It's incredibly virulent.
I'm in a turkey producing area - one of the largest in the country. What helped massively in 2015 was to simply put fine netting over the windows to the turkey barns, keeping other birds and at least some of their excrement out.
This is from Australia, but whatever:
"In Australia, indoor and free-range poultry, are at risk of contracting avian influenza due direct and indirect contact with waterfowl who may carry avian influenza virus in their nasal and eye discharge or faeces, farming and biosecurity practices.
Indoor (barn or shed) systems limit poultry from direct exposure to wild birds, but these are not immune to avian influenza risks due to indirect contact. This is because equipment, vehicles and human movements between farms can introduce the virus indoors, in particular when on-farm dams or open water sources act as a permanent residence for waterfowl.
Birds with outdoor access (free range) are at risk of coming into direct or indirect contact with wild waterfowl. Vegetated range areas may attract waterfowl, in particular if poultry are given feed or water outdoors. In free-range production systems, producers should therefore focus on managing these systems to reduce the risk of avian influenza."
You really, really need to be citing your sources. You have been bouncing back and forth between sounding authoritative and making assumptions or asking questions (or just being plain wrong).
I'm in a major turkey producing area and my wife worked for a national turkey producing company for 10 years. In 2015 it was all anyone heard about around here for months.
Granted, I don't know much about chickens, but a lot of this is common sense. I'm not sure what you think I'm wrong about.
Typical cage-free chickens are almost as cramped, they're just not (cruelly) confined to a cage. They're still sharing the same air. If one bird gets it in either situation the whole flock will need to be culled, as they're all going to die (more painfully) regardless.
It's certainly a real term. The context is often student athletes that intentionally didn't play their sport for a season (called redshirting) to maintain their 4-year eligibility so that they can stay for a fifth year and compete in their sport.
What editor state are you losing when you leave vim?
I run a pretty light vanilla vimrc (60 lines maybe) and with two lines you can enable vim undofiles and returning the cursor to the last location upom reopening a file. For me, quitting vim is functionally equivalent to ^Z?
You may lose LSP state like rust-analyzer's which takes a while to restore. You may lose opened buffers and positions within them (unless you have some session restore logic which may also take time), window layout, copy buffers, edit history and lots of other state.
Retaining positions, buffers, and edit history between sessions is all straightforward in vanilla vim though. Unless you run an autolinter or formatter that edits your target file and wipes the history.
I don't use tabs, sometimes I use split windows (usually only when vim-diffing), mostly I use multiple terminal windows in a tiling WM. I do use multiple buffers but I usually don't care about editing more than one or two at a time and it's easy to re-open these whenever I need to.
That's true for me too but usually my tabs and windows are managed one level higher, by the terminal emulator, or I'm opening vim with -o/-O to open a split window directly.
reply