Jump to content

2unlimited

Member
  • Posts

    11
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About 2unlimited

  • Birthday Mar 10, 1988

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

2unlimited's Achievements

  1. As an owner of a bigger brother, SB500, I can say that significant difference in an overall sound quality, as well as the bass, comes from the connection medium. If connected via fiber cable, it really sounds hollow, and monodimensional. On other hand, connecting it via bluetooth, turns it into a whole different speaker. If only you tried the other option. As Lg goes. I had that too, for the bedroom. It's a bloody disaster. Not only its soundbar is merely different from a built in speaker, but its bass module shakes uncontrollably on just any sound. Even the conversation. While Bose's bass module is much more refined. It only picks the waveforms that are supposed to go trough the bass amplifier. Second hand Bose Soundbar 500 is on the market for some time already, and can be found used around 200$. I'd warmly suggest going for that option. Over any low priced Lg. It's just a headache.
  2. Pardon me for reviving an old thread; a friend just asked about this issue and I quickly googled good old LTT hoping that I could just pass a quick link to an answer and that someone already elaborate something that should be a very common behaviour. So I would like to write down something that I learned from my professor many moons ago, lecturing CPU and ram in university. It was regarding L2 and L3 cache but it can be applied to RAM as well. So, cache acts as a waiter, in a restaurant. So let's say one day you come in a restaurant, and order a soup and a steak. You wait for certain amount of time for it to get prepared. You get your steak, leave. Next day, you again order the same. You wait, get your steak, you leave. Third day, the waiter see you at the door, he already figured you will have a soup, and a steak. You sit at the table. You get your food without waiting. You leave happy. The next day, you fancy a fish. But the waiter got your steak ready. You sit and order a fish. Now waiter says to a chef to cook it for you. Now you have to wait again. That is basically the purpose of the RAM (and cache) memory. To intelligently predict what are you going to use next, and have it ready for you ASAP. So if you are just using windows desktop, browsing the web etc. It will allocate as much memory to the tasks it predicted you are going to use next. And it will use the resources it has at its disposal. The moment that cache is required for another task (you order a fish) eg. you load Adobe Premiere, it will flush the amount of memory required by the program. If you really are paranoid about the numbers, you can use some memory cleaner software but it doesn't really do any real benefit. TLDR. Everything works as it should. You should not worry about the percentage of memory used by your idling system. It's supposed to work like that, to help your tasks run faster.
  3. This topic brings me back to early 2000s, when everyone even remotely tech savvy had to make its own version of some kind of free online forum, and fill it with this kinda shit. NOBODY FIN CARES FOR YOUR SONGS ? god, btw hernan cattaneo all the way
  4. Dear god, weird looking, unusable while folded, and it has a notch! All for mere 2000$. I pitty anyone who actually pre-ordered galaxy f-up if that was even an option
  5. Podcasts are bad Idea, sound is too unbalanced between quiet speech and Luke's bombastic laughs... my ears still bleed from Jayz/Louis/Wandell episode.
  6. Anders raised this concern 7 months ago. But it wasn't until google put it to actual work that someone waved the flag and said "this is a problem". You're right, I don't understand the mechanics of Cpu, but I understand the human nature and the "if aint broken dont touch it" philosophy.
  7. Accusation might be strong term. However, if some outsider like Anders Fogh could figure it out, It's a little hard to belive that nobody for 20 years at Intel didn't see this, or even pointed at. Maybe the scale of problem was just too big to deal with.
  8. Everything can be invisible if you choose not to look https://cyber.wtf/2017/07/28/negative-result-reading-kernel-memory-from-user-mode/
  9. Apparently, Apple already addresed this problem in security patch from Dec 6th. Link: https://www.macrumors.com/2018/01/03/intel-design-flaw-fixed-macos-10-13-2/ They called the fix "double map" : From my own expiricence so far, recently I tried to run some React projects in Visual Studio Code on my 2017 mbp, the result is program crash and processor temperature going over 90C. So far I was thinking it might be the VSC issue but now I'm a little bit more affraid. Hope that 10.13.3 resolves some of this scre*up
  10. https://venturebeat.com/2017/08/31/stupid-patent-of-the-month-jp-morgan-patents-inter-app-permissions/
×