Do what I do and use Nano for everything
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
8GB RAM is not for coding!
- Thread starter jake_the_tester
- Start date
- Sort by reaction score
Does it though? I think if you learn the keyboard shortcuts for most GUI editors you can do exactly the same things: quickly go to a certain line by number or next/previous instance of a regex; quickly insert a new line; move the cursor to the start or end of a line, do a quick regex find+replace. I think you can basically replicate a vi workflow almost exactly in most GUI text editors, but because you're not obliged to you might not learn the commands.
What do you think? Am I missing a way you can work in vi that can't be replicated almost exactly in something like BBEdit or Sublime Text?
Yes. Memory on modern MacOS is complicated. There is no simple way of viewing whether or not you are using too much memory. MacOS will use most available RAM to cache frequently used data and applications so just looking at free space isn’t useful. So Apple shows memory pressure as a tool for users to estimate their RAM workload.
I’ve never seen an analysis of how effective memory pressure as a performance tool is though. I’d love for someone to take a stab at it. It would be very interesting.
LOL, when you complain of memory usage issues and Chrome is right there hogging RAM. Use Safari or another better browser
I see plenty of designers building REST APIs, writing database connectors or implementing a database, be it document based or ORDs. It's become a "thing" when studying certain specializations in media design. I'm not saying they're doing a great job at it (just look at unit testing) but it's there. 🤷♂️
I just did an even simpler check on smartmontools.
I wrote files of different size (random text). Ran smartmontools before and after.
16k 64kB files
8k 128KB files
4k 256kB files
2k 512kB files
1k 1MB files
2 512MB files
All showed an increase in Data Units
By the way, if you decide to do this, don't accidentally misplace a 1024 and write 2million 512 byte files. Took a while to clean that up. I didn't even take a record of the smartmontools response so that was wasted effort.
Last edited:
I think the OP was a very elaborated trolling attempt, the likes of which we've recently seen here at MR, a macrumors newbie, apparently knowledgeable, sharing his dismal experience and ending in phrases such as, "I'm better of with a hackintosh", "Apple's getting greedier by the day", "better stay with my 64GB RAM Intel", etc.
It's not just Chrome, he's even running an antivirus while "developing", among a myriad of tasks that wouldn't fly, not smoothly, on 8GB no matter the architecture.
There's a reason these are the lower-end ARM Macs, people needing 64GB RAM and more I/O are better off waiting for the higher-end configurations. Heck, he could have ordered his M1 with 16 GB if he wanted to, but didn't.
I've been using vi since 1995 so I have the muscle memory so that I can do a lot of things faster in vi than a GUI editor, but not everything. If I have to manipulate text files I'll switch over to vi but I'll use an IDE for writing code (primarily Eclipse for Java, but I also do some Python and Node.js)
An example of something I'll do in vi - take a large JSON file that's on one line, pretty-format it, remove all lines containing a particular field, reformat back into one line, save.
Code:
=j (maps to %!python -m json.tool)
:g/"field"/d
=J (maps to %j)
:wYes and no. I think macOS has some great text shortcuts, and mastering the alt/command+arrow stuff as well as any shortcuts your editor has will make you very fast.
I feel very under qualified to answer this as I’m still a total n00b when it comes to Vim, all I can do is relate my experience so far. What clicked for me with Vim was the consistency of the logic of the commands and motions, which rewards investment of time spent learning and practising them. You can build your “vocabulary” of movements as you go and chain individual commands to compose expressions that describe what you want to do to the text (vs. just how far to move left/right/up/down), which is a very versatile approach. Things like, change until the next semicolon (which comes in very handy when changing the right hand of an assignment), or, delete everything between quotes/parentheses/brackets. I don’t think there’s anything like % in GUI editors either (go to matching bracket). A simple one that I love is o/O (insert below / above the current line).
But, there are vim mode plugins for all the editors so this is all kind of a moot point.
I don’t think you need to use Vim to be productive or efficient or enjoy what you’re doing, but I personally like it a lot. I think these days we have lots of good choices and it’s just down to individual preference.
Yeah I did something like that first too but people were still skeptical. I wrote about 500 GB to the disk and watched the TBW from smartctl go up a like amount. I wrote the replacement for smartmontools (not really a replacement since mine does very little) because it was pretty easy to do (about 300 lines of code) and to my mind, leaves no ambiguity. If the values returned by the SMART APIs are wrong, it is 100% on Apple since they designed the hardware and software.
We have had more trolls since the M1's came out on here. And a lot of Intel fanboys who are butthurt and try to use every thing against the M1. It's getting old.
It’s funny to me, there’s just some people desperate enough to try and make the M1 seem like a bad thing despite the overwhelming praise it’s received.
You really have to reach to make the m1 seem unimpressive, like comparing it to the top scoring x86 processors of all time or saying that the gpu performance is bad (when it’s the most powerful igpu bar none).
The fact is that Apple brought a low power, low end laptop chip that’s now beating up on all but the highest end processors, with better graphics than everything in its class, and with x86 emulation on top of that and keeping programs more responsive than on native intel Macs. That’s a home run no matter how you slice it.
Yeah I've been doing active development on the M1 MacBook Pro (16gb) since day 1 and many of my tools were running with the additional overhead of Rosetta for a long time - I'm floored by this machine's performance, battery longevity, and more...
I don't really believe I need 16gb ram, I mostly got it to future proof and help my resale value when it comes time to upgrade.
People who have problems with this computer's performance simply use their tools wrong.
And I keep reminding people but it seems to fall on deaf ears... the M1 is both just the beginning and Apples entry level chip. The trolls and haters think this is the best Apple can and will do....
Sadly, Nano is a bad attempt at a re-invention of WordStar in text editing mode. There are many, many editors that are way, way, way better than Nano -- BBEdit, Geany, Gedit, Atom, even the humble Vi.
If I want to use WordStar I will call up a CP/M emulator and run WordStar.
Nano is the Trabant equivalent of a text editor...
If you think coding "is the most lightweight task you can perform on a computer.". I suspect you haven't done much coding. You certainly haven't tried to build a large C++ project.
Its true that Sublime is a very light weight editor but the popular VS Code certainly is not. Neither are all the other Electron apps developers often use (e.g. Slack). Then if you are doing web development you probably need Chrome.
The well regarded JetBrains IDEs can use several gig. I have seen large C++ projects in CLion use over 8GB of RAM and that is just the IDE.
Then there are virtual machines and local Kubernetes clusters. They aren't exactly economical with RAM.
Well to be fair, Python is a scripting language and can run on machines much less powerful than any modern Mac (e.g. Raspberry Pie) and fast compilation was a design goal of the Go language designers. C is a fairly lightweight language too.
newbies... new term - rest api. Old folks. what.Oh just normal post ,get.
- dependency injection .Oh just inherit class. normal oop long time ago
m
- dependency injection .Oh just inherit class. normal oop long time ago
m