New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
https://thedailywtf.com/articles/That-Wouldve-Been-an-Option-Too
https://en.wikipedia.org/wiki/Thought-terminating_cliché
Fossil. Period.
Thanks for the link and more importantly the reminder that there actually is life outside of clouds and "serverless".
Btw. as much as I dislike it but Visual Studio Code is more and more omnipresent. I even know of a couple of (not too exotic) languages, some of whom actually had their own IDE, who pretty much force VSC upon people (because e.g. debugging is available only in VSC). Yuck.
JetBrains IDEs. Period.
Yeah, right, because we all love waiting for java crouching ...
Seriously, I would love them JetBrains IDEs because they are nice and well conceived but frankly, as they are java based and incredibly slow and resource hungry they end up being a pain in the a__. Hell, even VSC which is a monstrous behemoth itself is a racer next to java based IDEs.
Yep, resource-hungry but I feel very productive when using them.
That's why you have at least 16GB of ram
So, f_ck the developers in poor countries who can't afford a fat and up to date system? Sorry, no.
I'm no less productive with VSC or sublime. In fact, I use sublime whenever I can which unfortunately doesn't work out with some of the more exotic tools I have to use (like formal modellers or verification, etc).
Generally speaking I'm wondering a bit how much of the "progress" in editors and IDEs is actually really useful (like syntax highlighting) and how much is frankly driven by companies like JetBrain to provide reasons for ever new versions and "advantages" over competitors ...
And then there's emacs.
JetBrains IDEs have a lot of features. Integration with Git, Vagrant, Docker and so on.
Code completion is very intelligent. I had to refactor an entire project from another developer and I just had to select portions of code and press ALT+ENTER for the majority of the time and the IDE would take care itself of refactoring the code.
This was a huge time saver for me.
Do you need a database scheme because you are new to the project and want to explore it? JetBrains can generate it for you.
Do you need to deploy your site?
It has so many things built in that you don't have to change window.
RAM is cheap, so I don't see the problem. An 8GB stick here is about 50-60€.
8GB of ram will be fine to run PhpStorm (for example) and a VM.
Eight megabytes and constantly swapping! In the same discussion as jetbrains, heh.
"Why are we hiding from the police, dad?" "Because we use emacs, son. They use vi."
interesting OS but it needs a good editor
vim! please!
I just deployed a wild gogs, its fast and just works.
Awesome.
The DBA in me hates you so much right now.
Yes and no. No developer will optimize everything possible on early stage (let's assume Gitea is still in its early stage). The developer maybe started the project to host own side projects, and not a gigantic project like a Linux Kernel. Problems are noticed only when the problem is actually hit on more-edge cases.
A simple story from myself. I wrote a script to read a special index file and do string manipulation. Usually the index file is couple megabytes so I just read everything into a string, modify it, and write it back to disk.
Until one day it started working on a multi gigabyte file and consumed all the memory.
You really don't need to cache anything to use up the memory. Simply an edge use case would push things off the cliff.
A 10GB repository could be that edge use case. Imagine how much memory would be used to do a diff on WebUI if the author didn't check the size.
The keyword here in my original post, that you didn't include in the quote, is "persistently". What you're describing explains memory usage spikes, but not persistent usage.
And what people complain about where Gitlab is concerned, is not that it occasionally spikes up to 2GB of memory usage - but that it does so all the time, while idle.
Gitlab(+CI) is now more than just a git repo. I think the 2GB is a decent idle RAM consumption for the amount of features crammed in.
I really balked at them raising the recommended ram to 8gb (or 4gb+4gb swap).
For a 2-5 users, I figure a 3gb KVM should be enough, in reality, if you're not using all the bells and whistles.
Like I said earlier, "features" in and of themselves don't consume persistent RAM. You can have thousands of features and still have a very minimal RAM footprint.
I just read this. Appropriate!
Installed Gitea a couple of days ago and so far I like it and plan to use for my own personal and work code repository. Only thing is I can't get markdown to work. Does Gitea or Gogs not support markdown?
Markdown should work out of the box, AFAIK. If it doesn't, that's a bug.
I figured it out... When I copied and pasted some code into Gitea, there was a singular extra whitespace at the end of each line that I did not notice. So when using markdown, it would not apply until the whitespace was removed.
oof. smh ...
sed 's/ *$//'all the things ... lol