I’m very happy to not use a general purpose computer anymore, to be honest.
330 karma · joined November 2, 2014
I’m very happy to not use a general purpose computer anymore, to be honest.
Anyway, I manage a few M1 and M3 machines with 256/8 configs and they all run just as fast as 16 and 32 machines EXCEPT for workloads that need more than 8GB for a process (virtualization) or workloads that need lots of video memory (Lightroom can KILL an 8GB machine that isn't doing anything else...)
The 8GB is stupid discussion isn't "wrong" in the general case, but it is wrong for maybe 80% of users.
Confirmed here: https://computer.howstuffworks.com/question299.htm (and elsewhere.)
A year later I was doing bonkers (for the time) photoshop work on very large compressed tiff files and my G4 laptop running at 400Mhz was more than 2x as fast as PIIIs on my bench.
Was it faster all around? I don't know how to tell. Was Apple as honest as I am in this commentary about how it mattered what you were doing? No. Was it a CPU that was able to do some things very fast vs others? I know it was.
I was only allowed to use perl 4 to write this software and I wasn't allowed to use a database, even though the datastructure for a day's publishing batch had tens of thousands of keys and values and required RDBMs style queries. It also features a configurable postscript parser that extracts all kinds of data from completed newspaper pages that informs the publishing system. When I wrote it I was told that it would run for a few months only while we figured out how to get a $5M commercial product to handle the work.
The whole thing was written in perl 4 style OO Perl and came in at about 16k lines of code in the end -- most of the code was for the postscript processor and tons of cruft that I had to write to made a relational DBMS in memory because I wasn't allowed to use mysql. It took me four months to write it. I launched it in January of 2002 and it runs to this day. I know this because I got a call about it last month where my replacement's replacement's replacement asked me a few questions about what OO Perl is because he wanted to make a few changes. Good luck! It still runs and is responsbile for about 80% of what it was originally built to do. It is used by hundreds of people daily, who by all reports absolutely hate it. There are people working at the newspaper today that use it regularly that were not born when I wrote it. I am twice as old as I was when I wrote it.
They have apparently tried to replace it several times over the last 22 years and have failed to do so... this is likely due to the blockheadedness of my old boss (who is still there) as much as the radically insane obscurity of my code, which is exactly how you'd expect 16k lines of 22 year old OO Perl 4 would be.
You are the one that is asserting that 1. All DRM is inherently bypassable, which is simply not at all true. and 2. That anyone pushing for improvement is against lending, which is not true. This is what YOU are saying, not me. I am simply saying that if the IA wants to keep going (and I would like them to) they might close an unused http route. That is LITERALLY all I am asserting. Good lord, why even bother?
Just to rephrase for clarity: the way that pretty much every college student that I know downloads many, many books from the archive is via an undocumented route on the website that isn't needed for the site's published borrowing functionality to work.
If you look here: https://archive.org/details/lexicographyoedp0000unse you will see that downloading is not supported.
Yet if click "Borrow" and then you hit this URL while logged in: https://archive.org/services/loans/loan/?action=media_url&id...
You will download a ADE stub file that is trivially deDRM'd.
IA's "solution" to a previous issue with publishers was to remove this functionality from their site. They pulled the links in the UI but not the functionality... I don't think they operate in good faith.
But... far be it from me to expect any dialogue where to be anything but creator hostile. To my mind that is very much short term thinking. We need to make sure creators are paid for their work because we want them to keep creating -- and for others to also create. Just because things are legal doesn/t make them right and/or for the greater good.
Regarding legality, the media company battle re: DVD-CSS is quite different in quite a number of ways such that it doesn't simply apply here. That said, I'm not making a legal argument -- I am advocating for a system that makes sense to authors (whom we rely on to write the things that we value) and the greater good.
I am for DRM because it could enable something like the IA to host and lend books without violating author's privledge. The IA's implementation is foolish and, I think, carries the intent to allow exploitation.
"Second, we know that HuffPo used both manual and algorithmic moderation in all three phases, but we do not know how the policies changed under the different identificatory regimes."
Given whay I know about Huffpo's moderation system and their statement that they don't have understanding of them I'd say that nothing reported in this study should be considered valid for a few reasons.
One is that Huffpost used many different systems of moderations following many changing standards throughout their days as a big news site (#3 in the US at one point) and the biggest news-based community, which they were for several years.
They started with no moderation, then human moderation with evolving standards and practices that were overseen by a brilliant community team. Then they bought Julia in 2010(? ish) which was a very early machine learning moderation system that was trained on millions of human made moderation decisions before launch and whose training and internals were constantly updated and improved for years. Julia was dropped for Facebook comments later on, at which point Facebook did most of the basica moderation but was still assited by human moderators.
My first critique of this analysis is that the authors have no data or understanding of the moderation actions that resulted in suppression of comments or users. How can an analysis make any claims without this data? So far as they know the comment-flow was more hostile during the periods they observe as more civil, but there were just far more comments suppressed. Just one of dozens of other internal details of the operation that would invalidate their conclusions would be that Huffpost quiet-deleted comments for a significant period of time -- meaning that you could post, and you would see your posts in context when you were logged in but no one else would see them. They also silent-banned users. This and other details of implementation create a great deal of complexity and secondary effects.
I can attest that moderation was very, very active and that lots and lots of comments were moderated down and out of the comment threads... again indicating significantly less civility than any retrospective analysis would be able to discern without all the data.
I also find it interesting that this study chose Huffpost for the analysis. At the site's hights of success and profit the comment threads were the reason for their SEO dominance and were considered to be the most important secret sauce. Huffpost moderation was the best in the business by a long measure. With the methodology presented it would make sense to me to say that Huffpost would appear to be the most civil of the big sites of the time. So it is interesting that this study focuses singly on Huffpost and reports that their theories indicate this differential.
While the authors do cover some of this in their section on Limitations, they don't cover near enough to justify their results... instead this reads as another cherry-picking study where authors had a theory and found a dataset that confirmed it while being unaware of fundamental reasons why that dataset was an outlier, making it impossible for them to build in the needed controls in their methods.
"Premarital sex predicts divorce, but we do not know why."
That last part makes all the difference in the world.
it is funny, really how obvious the angle is in these kinds of analysis. There's no way you could even start to draw conclusions from these kinds of data sets unless you already knew what you were going to report -- there's less than no information in the numbers being used... the only rational analysis would result in nothing but questions and absolutely no conclusions.
I'd also like to see the marriage rate by state for comparison, too. Arkansas has more than 2x the marriages per capita of California (lowest divorce rate), for instance, but only 20% fewer divorces...
Again, this article is a bad conceptual and statistical analysis of the data.
People that authentically hold conservative values work differently. I suspect that the lower divorce rate among this cohort has a lot to do with another statistic: that 65-70% of divorces are initiated by women. Conservative values would seem to inhibit a woman from initiating divorce, resulting in a lower rate.
also: this article is poorly thought out junk top to bottom, imo.
I hadn't noticed the improvements until I started using my apple watch a lot... I had given up on it a few years back, I guess.
But I will relent and acknowledge that your arguments ring very true. How do I get my Messages window back if I accentally close it? Very good point.
The ribbon though? I think your memory is optimistic. It was in my memory ugly, clunky, slow and had some, but few system settings. But I must admit that in my heart OS 7.1 was the high water mark of usability and I resented all subsequent innovations... which it sounds like you might be able to empathize with.
if you find yourself looking for faster routes to an end, MacOS almost always has several levels of shortcuts waiting for your muscle memory.
A Better test would be to set up an intensive real world 20 track project, assess utilization and overhead, and then find a real-world way to increment that stress upward to the breaking point.
Most computer music forum wonks use some kind of test based on softsynths or reverbs or a combination and stack them high on a smaller number of tracks.
I mean... 300 tracks? You're basically testing the DAW's thread management at that point, not the CPU as it would be used.