Interests: News, Finance, Computer, Science, Tech, and Living
My first printer in the early 80s was an EPSON dot matrix for $800. The second was an Apple laser printer in the late 80s for $3500. The third was a Brother momochrome MFC laser printer for $500 in the 00s. You can see why they are crap, huge price reductiions. Even more if you consider inflation and capability.
Always look at per page cost. Generally that means monochrome laser.
Edit: The issues I have had with Linux and the Brother MFC is firmware upgade as it wants to use Windows for that. I have had some Postscript compatability issues too. The paper feeder for the scanner is not perfect either. It can skew the paper and you have to watch for double feeds. Not a defect but a missing function, I cannot figure out how to fax from my computer or USB stick. An oddity, it does not seem to maintain time when the unit is off and never has which is really annoying especially for faxing. Mostly like the printer but not the above issues so much.
That is not what they said. They said operationally nothing is changing. However, they are basically in-part ad supported and so with that comes some strings. All of this can probably be configued out but it is a pain.
For me, hard call. Fragmenting into maybe better browsers reduces Firefox popularity and that impacts wheather web developers will test against anything but Chrome. When that happens these other browsers become irrelevent. So using other browers has a consequence.
This is the thing about Chrome and the whole Chromium based ecosystem. Why on earth would anyone use a browser from an Ad company.
By the way. They are planning on putting it in Android apps too. So there one gets little choice. A non-starter like Apple where you cannot even load your own apps and app stores or Android from an Ad company where you can with effort at least choose your own software and even image your own OS.
Keep in mind Python can interact with spreadsheet formats. So it is very possible to input your data in a spreadsheet , load that data into Python, then dump it into a spreadsheet. Easiest is CSV but I have done direct too.
What approach depends. If you know a spreadsheet really well, then taking it quite a ways makes a lot of sense. On the other hand when one gets to the point of writing more then 100 lines of VBA and especially into the 500 range, it may be time to use another approach. Same when execution times are very long or data very large. Working with large VBA code bases is kind of nutty but people often get too deep into the I have a hammer so every problem looks like a nail thinking. I have had to work with code like that myself.
By the way, lot of crap paper out there too. Lot do not mark which side to print on first and this is related to curl and shineyness. One has to guess. If your getting a lot of jams try flipping the paper over.
Our last ream has a deffective narrow page every 4th page too. I had to manually pull those out.