|
|
I can't speak of Dell's Desktop... but my Dell Laptop of 2011 is still runing perfectly. Back in the day (around 2013, still under warranty) I had a problem with the heat... I called in, it got repaired and never had another issue.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I only buy DELL computers(either desktop or laptop)..
diligent hands rule....
|
|
|
|
|
I found this very entertaining! The guy is a great storyteller!  It's a long vid that's not so flattering for Dell. HTE can they sell a PC at that price point with any standard/discount components?
It makes me laugh when family/friends ask for advice on buying a new PC. They skip right past the lower priced models insisting that they need that i7 (certainly not AMD!) and 32GB ram for email and surfing the web! My current machine is an off-the-shelf mid-priced Lenovo (desktop) with the only upgrade being the SSD. I've built my own in the past but they've all been rather noisy. This thing is whisper quiet and boots quick enough. Unfortunately though it shows as questionable or not compatible with Win11!
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
kmoorevs wrote: The guy is a great storyteller!
But still pretty dim. He complains when the system he wasted all this money on does not have the features he did not order. Which begs the question why does someone who knows so little want a great powerful tower system in the first place?
|
|
|
|
|
I can remember wanting to have a spare desktop system in case my regular system was malfunctioning (this was back before notebooks became both inexpensive and reliable), so I picked a system up on sale at Best Buy that had Windows Vista installed. OH MY, what a POS! 
I bought it just to use while I got my main one repaired (the "repair" was me buying a new motherboard), and once I got my other system up & running, that stayed functioning properly for years. I then got a notebook and put both systems away, and sure enough when I got around to checking them out years later, they were both malfunctioning, so I just took all the good stuff (hard drive, CPU, memory) and threw them away.
|
|
|
|
|
This is a load of BS! Over the years I have bought over a hundred Dell desktops and laptops for personal use, family members and previous employers. I have never had any issues!
Get me coffee and no one gets hurt!
|
|
|
|
|
I have had six Dells at home, and multiple (laptops, desktops, towers) at work. The worst problem I ever encountered was a faulty power transformer, which was replaced (under warranty) in a day. One bad system does not make the entire product line (or the company) worthless.
I always suspect people who do this sort of thing have an ulterior motive.
[edit]
So he spent almost €2,500 on a tower PC and was surprised that it was a big monster, and not a laptop. Obviously too stupid to look at the pictures on the website before putting in his order.
I wonder if he would like to buy London Bridge?
[/edit]
modified 19-Jul-21 4:44am.
|
|
|
|
|
Richard MacCutchan wrote: to buy London Bridge
Nah, I bought it last week and I am not selling it already.
|
|
|
|
|
I am still working on my streaming zip library, and after bouncing between other people's implementations and trying to adapt them I settled on one that was already implemented as a coroutine (which is what I needed)
I worked on it for two days, trying to get it to decompress in chunks. I got it to do a whole buffer at a time but I could not work out how to use this scarcely documented decompression coroutine in the popular minizw.h offering so that it would act like the coroutine it was supposed to be.
So eventually, I googled "tinfl_decompress"
Pay dirt! There's a sample of using it. In the comments I note my output buffer has to be at least 32kB - well that explains a lot. 32kB isn't ideal, but I can work with it if i have to.
In the comments it also notes that one of the necessary component structs its using is about 300kB!
300kB is about the amount of *total RAM* I have available on my system.
That's not counting the input and output buffers I need, and heaven forbid the zip contains a JPEG i need to decompress - I'll have no memory left!
So all this code I wrote around this function is bunk.
Fortunately, I found another implementation of a previous C implementation I was using, only someone had ported it to C#. Yay!
And then I realized one of the reasons that's such a boon. NO PREPROCESSOR. There were pages of macros in the original source. It was one of the reasons I didn't want to touch it.
The thing isn't implemented as a coroutine unfortunately, but the code is something that can be followed and adapted.
I've said it before - I love C#. I don't even use it regularly anymore, but it's nice to have around.
Less is more.
Real programmers use butterflies
|
|
|
|
|
I was expecting a waaay shorter post with that headline... But all good and interesting though 
|
|
|
|
|
I'm about halfway through converting it (in C#) to use a coroutine. God bless C#
I just need to do the state machine for the uncompressed blocks and then I'm golden.
After that, I port it back to C++ =)
Man, I love C#. If you just code such that you don't really rely on the GC the way your code is orchestrated it's cake to port to and from it.
Real programmers use butterflies
|
|
|
|
|
Quote: Man, I love C#. If you just code such that you don't really rely on the GC the way your code is orchestrated it's cake to port to and from it.
This came as a surprise, because I thought C# had more language features (keywords and operators) than C++, and also a richer library. I would have also thought that GC would cause porting problems, but maybe you can just use smart pointers or change reference nullifications (I assume) to delete.
|
|
|
|
|
You'd think so, but if you use arrays for the most part (unless you're using The STL in which case you can use things like std::vector<> instead of List<> and std::map<> instead of Dictionary<>) you don't really need to worry about the GC that much. Just where you use new to make new arrays. You either change those to be fixed size (my first choice) or change them to use malloc/calloc, etc.
Most of the "core" C# stuff (streams and containers) have counterparts in C++.
I don't use "unsafe" mode in C# for this. No pointers, though maybe that would make some things easier to port.
Keep in mind I'm talking about porting algorithmic things, like a huffman inflators, or JSON parser, not apps that rely on a ton of libraries or specialized environments, like some ASP.NET application.
Real programmers use butterflies
modified 18-Jul-21 11:32am.
|
|
|
|
|
If only I could import all of the fancy-free Python SciPy library and etc into C# without too much hassle. That would make my life much easier. I know there is a way but...
|
|
|
|
|
I taught myself enough python recently to snatch some code for loading old windows 3.1 FON files, and in that case I went from python directly to C++. The main issue with Python is all the libraries.
Real programmers use butterflies
|
|
|
|
|
Agreed, it's always something extra libraries for sure. Seems to be a dll hell ting, but I would definitely like to have something like SciPy for C#... But its a lot of work to implement this...
|
|
|
|
|
Write an IronPython wrapper?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
C# is a very good language, I don't think I've done any serious code in C or C++ since I learned it.
It's getting somewhat "committeefied" though ... some folk just can't leave a good thing alone.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Quote: some folk just can't leave a good thing alone
At least some of what they add seems useful, which has generally ceased to be true for C++. 
|
|
|
|
|
Except for the funky way that structs & objects are instantiated differently  , it's a pretty good platform. I never did get the hang of callbacks or whatever they are termed (i.e., function pointers in C++).
|
|
|
|
|
Edit: I may have misinterpreted you. If you meant you don't get how they work in C# then disregard this comment! 
It's a little easier these days with lambdas in C++. If you don't capture anything it decays to a standard function pointer meaning you can declare callbacks inline
the weird thing about function pointers in c/c++ is declaring them
the_return_type(*the_callback_variable_name)(parameter_type1,parameter_type2,...);
so like
void*(allocator)(size_t)=malloc;
That would declare a function pointer called allocator and make it point to malloc.
But once you've declared it using it is basically like using any other function:
void* buf = allocator(10);
There's your "callback"
Now as far as a function that takes one of those monsters as a parameter type - in other words, a function that takes a callback, you can declare that parameter inline in a function like you can in C#, except that you can't capture with it (unless you use std::function which is different):
static void do_my_func_with_callback(const char* sz,bool(*callback)(const char*)) {
callback(sz);
}
and then
do_my_func_with_callback("something",[](const char* sz){ printf("called with %s\e\n"); });
Real programmers use butterflies
modified 18-Jul-21 19:26pm.
|
|
|
|
|
I know how to do function pointers in C++, although I can never remember the exact syntax.
Now that I think about it, I think I can do a single delegate in C#, but there seems to be a way to put such delegate callbacks in a list, and that is where I get confused. I've been retired for a while, so I've not been doing much with it.
|
|
|
|
|
swampwiz wrote: I never did get the hang of callbacks or whatever they are termed (i.e., function pointers in C++)
I think you're referring to C# delegates[^].
Software Zen: delete this;
|
|
|
|
|
Gary R. Wheeler wrote: I think you're referring to C# delegates[^].
Yes, that's the term.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
