One had to do some significant hand tuning of config.sys and autoexec.bat to optimize conventional.memory usage for a lot of games in that era (ie. relocating device drivers to extended memory), at least until later versions of MS Dos included the memmaker utility to partially automate the process.
This was tricky enough that folks would pay my barely adult self a consultant's hourly rate to do this for them.
>> and will quite happily "love" one individual of a species while being completely indifferent to the death and suffering of the rest of that species.
Similar to how a significant subset of the human population responds to other humans.
Fruity Loops is written in Delphi. There was a period in time where because of this, the company said there would never be a Mac version, but eventually one happened with the help of ObjectPascal.
Out of respect for Fruity Loops, and contempt of WK Kellogg Co.'s lawyers, I refuse to acknowledge the forced named change. WK Kellogg can accept the reality that there is no conflict of trademarks or other business interests between music software and sugar-pushers, or they can shove off. (>_<)
The replies to the this comment [1] (from 2019) indicate that at Delphi was still used then for FL Studio. They link to a case study at [2], the date inside the pdf says 2015, and that Delphi has a Mac compiler they use too.
If someone made a table of one hundred potential targets and rolled ten ten sided dice to pick a row to target, do we blame the decision on the dice, the table, Wizards of the Coast, or the person who decided this was a good way to choose targets?
You’re conflating who chooses the decision maker with the decision making device.
So AI’s output is not so different than a roll of dice? Definitely the people who decided to put in such an incapable and unreliable tool should be held accountable. No dispute in that.
We put a fair amount of effort into reducing our resource footprint, so I'm curious what you find lacking in our memory management. From a quick test we use a similar amount of memory to Zed.
Hard to compare the two programs over a week of uptime. ST memory usage does get larger as caches get filled over time, but I've had uptimes of months without issue. I'd expect similar results from other editors.
Do you have a specific memory issue where it keeps using more over time?
General issue, have observed it on multiple systems. On a long enough timescale, will grow to farcical amounts of memory usage.
Unfortunately, while this is something I've observed through major point releases and on different platforms, there have always been some plugins in use.
UnUnfortunately not enough commonality in configuration or hours in the day to track down if this would happen on a totally clean install...
I'm sure your roadmap is quite extensive, but it would be great if sublime itself could graph or warn when memory usage increased by some specified percentage, or if any particular plugin spikes resource usage.
Plugins are a frequent culprit of issues like this. Depending on how you're tracking memory usage you may already be able to at least narrow down the culprit by looking at which process is using too much; plugins run on a separate process and may launch additional processes from there.
Unfortunately tracking individual plugin memory usage is not possible without invasive (and slow) tracing. If the plugins are causing big memory usage in the main process it can be hard to nail down due to that state being shared between all plugins.
reply