2,285 karma · joined December 10, 2011
It's not uncommon to hear unrealistic praise of the M1 on HN.
IMO, you are both wrong. The M1 is fine as a laptop CPU, because what it needs to do well, it does very well - which is power efficiency. However, if what you need is computational power, and you don't particularly prioritize power consumption, then the M1 not only does not obliterate the competition, it significantly under-performs. And this is before you add in a dedicated GPU that solves some of those tasks much, much faster.
Take Cinebench R23, where M1 Pro (10+16) has about the same performance as the top contenders that do not have dedicated GPU cores, e.g. Ryzen 9 5900HX and Core i9-11980HK. Throw in a dedicated GPU for a work task that can properly utilize it, and the performance difference is at least 3x that of the M1.
Now, I'm not saying that the M1 is bad. It's just that.... "Completely obliterates the competition for laptops" is a strange way to describe "yeah, if both systems do very little, the M1 will use much less power!". For many, this results in it being the best laptop CPU for the tradeoffs they want, especially if the MacOS is an added positive.
However, that the M1 competes and outperforms in terms of computation performance, would be just wrong.
But, to just focus on the arguments you had on Linux. Android is only a drop in the water in terms of Linux kernel usage. And we have every reason to believe they chose Linux based on its technical merits. It actually works pretty well for what an operating system needs to do. The top 500 supercomputers, worth billions (the fastest one alone cost 1 billion) don't pick Linux because it is cheaper. They pick it because it does what it needs to do, fairly decently. The NT kernel has a bag of decades old shit stinking up the place, so that's a no go. And MacOS forked Unix is not licensed to run on anything non-apple branded, not that that would matter, since there would be zero incentive to do so.
The argument presented that there is no open source software that is better than the commercial equivalent, is what I gave counter examples to. Which is demonstrably easy to argue against. Which I have done. You wouldn't want to use anything other than Linux for a supercomputer. AWS and GCP run their systems on Linux.
I'm pretty happy with the transition to CalyxOS. Everything works as before, but I can now limit internet access to apps, and there is a much more consumer friendly view of permissions. Not tying the whole phone to system-level user with google services feels great. Specifics that need it still gets it, like YouTube.
I honestly think blender is a technical marvel that in many cases is better than its proprietary counterparts. The bar is quite high for these kinds of specialised and very expensive software. So, if blender is "bad", then perhaps the bar is set so high, that I don't think I can give a satisfactory answer.
"Utopian" in that there is nothing that could be better or improved is a higher bar than what I had in mind. But, just "better or equal than its proprietary counterparts", I do feel there are examples. Linux itself being a very clear one. There is a reason why it's the most used operating system by a mile (something like 90-98%). More contentiously I would also include it for desktop use. Hmm, perhaps AOSP also.
Out of the many tools you've mentioned, I've used most of them as well, and I don't consider any of them particularly great. But, what are the closed source alternatives that are better?
Perhaps also fish, as I cannot think of a better proprietary shell. Powershell and its windows integration is uaf.
Maybe some of my examples are skewed by the value I place on it not being controlled by corporate interests. That my usage isn't profiled, that I'm not exposed to dark patterns for KPIs at some board meeting.
The only thing that causes a comparatively bad experience on Linux is in part software availability or driver related, neither of which is the fault of the operating system itself.
Probably because of which fields you work in. But in software development, I'd say it is almost exclusively the case all over the board.
If you work in digital arts, then Blender is probably the best end-user application example I can think of.
The difference in post-processing when having to decode text is around two orders of magnitude, which is very significant. In the case of the 3MF format in question in this article, I find the tradeoff for human readable files to be a very strange one. The benefit of that at the cost of say waiting a minute to load a file that would otherwise take a second, is a puzzling one. But, it's all a tradeoff after all. If humans work with the files, it is a strong argument work with text. When software stores and loads files, it will likely be a poor choice to store data as text.
But, you are right. The file size consideration is not all that relevant. However, what was mostly discussed was the argument that serializing text that represents numbers is more space efficient. Which as I mentioned a few times, can only be the case when the straight serialization of the numbers is done poorly.
I think what threw me off was the context of this discussion, which was 3MF file format. For such cases, the usefulness of humans opening up the data in text editors is somewhat contrived. I believe that tradeoff for the 3MF format was a mistake, and will likely hinder broad adoption. I'm however mostly concerned with the extra processing required in order to decode the human readable files. We're talking a likely speedup of a factor of 50-100. For models that push this limit, imagine a file that takes 60 seconds to process. This isn't entirely unreasonable for a model with insane level of details. If they instead had gone for a binary file representation, the load time would likely be less than a second. Failing to recognize this tradeoff for human readable text... is unfortunate.
But, if the argument was that text is a more efficient way to store numerical data. Then, there is no need to bring beliefs into this discussion. It is just not the case. Serialisation of numbers have been solved by engineers many decades ago, and there are many to chose from based on extra information on what the numbers should represent. One such representation is actually useful as a lookup table for text. But, to suggest that breaking up a single numerical value into individual lookup table values, is somehow more efficient than storing the original value with the right choice of encoding it... I don't know. I don't care all that much. But, surely you can see my argument?
The whole thing is a tautology. For the sake of silliness, if ascii encoding numbers somehow was the most efficient way of encoding numbers (it isn't, but, let's say it was) then it would only then be exactly as efficient as "choosing the best way to serialize a number". But, surely, whatevever that data was, would then be most efficiently represented by the ascii representation. So, we should store the ascii representation of the bytes that store the lookup table values, as encoded ascii values. Doesn't take more than a handful iterations before you run out of storage space available on the planet.
To reiterate my original point: It is never the case that serializing text that represents numbers is the most efficient representation. The posts here seem to either suggest or think this is the case. And this was only the size consideration. It is even worse in terms of processing. You need to do O(n) operations on the length of text data just in order to decode the values. A step that is entirely avoided with a correct binary format.
Just a anecdotal example here on the computational aspect. Maybe 10 years ago or so, I used an OBJ loading library that would straight up decode 3d models represented as ASCII text. I wrote a simple de/serialization program, just 70 lines of code, to both dump and read dumped data. The load speed for a complicated scene went from 38 to 0.7 seconds.
This isn't to say there aren't good use cases for text formats. However, it is always a tradeoff for human readable data, at the expense of efficiency (storage and computational). The former is much less so when using a simple compression step. Very often this tradeoff is acceptable.
> Text compression of number data is extremely efficient
Of course it isn't. It is arguably one of the worst there is. It can only ever by more efficient when representing a very low subset of values and the alternative binary representation is exceedingly poor. But those constraint would make the whole discussion kinda silly.
Serializing text, is after all binary encoding data. If you follow this with compression algorithms, you'll likely not end up too far away in either case.
Just take the example you gave. "A 5 digit integer is 3 bytes less than the double to store it". Yes, true. However, a 5 digit integer can also be represented by 12 bits.
And you can even pack them if this is all you really care about (there is a good reason why you wouldn't want to do this, as word alignment is much more important, as you would be able to directly map data to memory allocations, but let's for argument sake say that storage was king). For each 5 digit numbers as a text file, you'll need another byte to encode the line break or delimiter. I.e. 6 bytes instead of 12 bits, or 4 times wasted space. For a million values, 5.7 MiB instead of 1.4 MiB.
And therein lies the rub. If you can throw more computational power and resources at your problem, then you should absolutely go for something with simpler abstractions that make better use of your time.
The problem is however not with C or C++, but rather inexperience in how to manage the control/flexibility these languages allow. You now have 50 ways to shoot yourself in the foot, instead of the otherwise handful. And, you also get the choice of a few bazookas.
> I have no idea how people write whole browsers and operating systems in this language.
They use best practices that avoid all of the aforementioned 50 ways.
Having a tool on a resume, or listing experience with tools, should certainly not be interpreted as someone being a rust zealot, evangelist, "pratting on endlessly", and all the rest of the examples you gave. So, maybe you initially wrote something different to what you actually meant.
I tried PopOS at one point, to see what it was about. And, I honestly don't understand what it adds to the table. It felt like many minor things were changed to be different, but overall it had the same things I wanted. After being annoyed for a couple of days, I installed Ubuntu, removed snap, and everything is pleasant again.
I really missed the old days of Opera, which for a long time was superior to Firefox and Chrome in so many ways. Up until they changed the web, and Opera dom/rendering engine couldn't keep up.
Vivaldi is the successor to Opera in many ways.
This isn't even remotely true. Computers are really good at doing more than one thing at a time. I find it mind-boggling that there is such a focus on the performance of a single core. This hasn't been all that relevant for the last 15 years. As for what this matters, the difference for single core isn't all that big regardless (one M1 core performs about the same as one 5980HS thread). When you want to know how powerful the computing power of a CPU is, how about comparing .. you know... what it can do?
And, what it can do when it is asked to do everything it can, I can reiterate that the M1 is nowhere near the competition. The 5980HS mobile CPU will get the same multi-threaded job done in half the time, which is a huge difference. Which is why discussion threads like these feel... chilling. Like as if I stepped in to a cult meeting, where we praise normalcy as revolutionary. It's not even close to the last generation of CPUs in terms of compute power. It just a step up from the Intel CPUs apple used in the previous MBPs.
And, it's not that the M1 is a bad CPU. It's actually pretty good for what it does, and it is exceptionally good at power efficiency. The 5nm and low thread count does contribute significantly to the power performance, so it will be interesting to to see how future M1 processors perform.
Imagine if the M2 doubled core count, and thus doubled multi-core performance compared to the M1. It would then be just as powerful as the current 5980HS. Another revolution no doubt.
So, it's not that the title is wrong. Just that it seems misleading.
This discussion also comes up again and again on HN on the M1. People say weird things like that the never experienced such a jump in computational power from one generation to the next. And what they tend to mean is from older apple hardware to newer hardware.
Now, power consumption may be the end all be all for some people. If your work tasks actually don't require a lot of computational power, then I can see it being much more valuable to have the flexibility of a cool laptop with a long battery life.
But, touting the M1 as revolutionary, because all that matters is power consumption, feels like a disconnect to me. I'm all for people liking stuff they like. But, I don't get what's revolutionary at all. I was interesting in hearing what people thought about it though.