31–40 of 412 posts
Only 16 gigs of RAM? Why do companies still hold that limit in 2018? I was hoping for 32 gigs back in 2015.
I've had so many problems with my XPS 13 that I bought in 2016 that I will never buy another one. Killer WiFi card was utter crap, laptop has issues going to sleep and waking up when closing the lid (sometimes it would hang on the the dell screen when trying to wake up and never recover), etc. Purely anecdotal, but a hard pass for me. Lenovo is my new laptop brand of choice.
The Killer wifi has been reliable for me, IMO atheros or intel is always a good choice for wifi on linux
IMO, it does not make sense to buy any of those new models: whether it's Dell, HP, or else--before we see models with 32Gb of RAM. It's been told here over and over since 2016 when first Touchbar MacBook got released. It's 2018 and all of us, including manufacturers, are locked with 16GB of RAM and those upgrades look like a joke. Within last month I noticed myötähäpeä when someone asks me for laptop advice. Hopefull…
IMO, it does not make sense to buy any of those new models: whether it's Dell, HP, or else--before we see models with 32Gb of RAM. It's been told here over and over since 2016 when first Touchbar MacBook got released. It's 2018 and all of us, including manufacturers, are locked with 16GB of RAM and those upgrades look like a joke. Within last month I noticed myötähäpeä when someone asks me for laptop advice. Hopefull…
Should I hold off on buying a computer until this spectre and meltdown issues are fixed?
That will take a year no?
[1]: By this I mean that in general, our formal systems dump time as a consideration as quickly as they can. The systems designing the CPUs themselves don't, of course, because time is a big deal in making a modern CPU work at all, but otherwise, we dump it as a consideration as quickly as we can, for lots of reasons, like not overspecifying a system and overconstraining it, and because it's really, really hard to keep track of time, and generally doesn't bring value commensurate with that complexity. Having built our stack of software and formalisms without very much thought about tracking time precisely, we generally only once at the very end recapture some time information, when we care, via O() analysis, and generally via the use of a whole crapton of explicitly-approximated values, which for what we care about is almost always good enough.... until timing attacks. Timing attacks suck. I think we're just barely beginning to come to grips with how much they suck.
I've had so many problems with my XPS 13 that I bought in 2016 that I will never buy another one. Killer WiFi card was utter crap, laptop has issues going to sleep and waking up when closing the lid (sometimes it would hang on the the dell screen when trying to wake up and never recover), etc. Purely anecdotal, but a hard pass for me. Lenovo is my new laptop brand of choice.
Earlier quoted context omitted.
Not 100% sure but mostly due to battery life, the more ram you have, the more power you use. 32 gigs probably shaves hour or so off the battery (don't know for sure) and that might be the reason.
I use my laptop almost always with a power supply (either home or office) so I would happily trade some battery life for more RAM.
Earlier quoted context omitted.
Quoting Barton George: > We are definitely looking into the coil whine issue, this has senior management visibility, and pursuing several avenues for the current system as well as solutions going forward. Source: http://en.community.dell.com/techcenter/os-applications/f/46...
That is from June, this is the latest from December: http://en.community.dell.com/techcenter/os-applications/f/46... A motherboard change and a BIOS update (2.4.2) are supposed to lower the noise as much as they can, while still deeming it "working within specification". Users report the 2.4.2 update didn't help much or even made it worse.