141–150 of 196 posts
Earlier quoted context omitted.
I went to a "tech school" to learn computers while in High School in the 90's. The tech school also had classes for 'the trades', it was set up to prepare Michigan kids for careers (Careerline Tech IIRC). Anyway. A big part of that class was learning to clean, repair, and manage printers. Again, it was the 90's, and we were high school kids. We came out quite capable with many computer skills but the printer stuff re…
> The printers of today are awful landfill fodder compared to the Okidata's of the 90's. Pure simplicity and speed vs FULL COMPUTERS, with scanning, faxing, and every other imaginable feature crammed in with zero hope of doing anything other than replacing the toner. The first Laserwriter in 1985 had more processing power than the Macintosh it was sold to accompany. Printers have been full computers for a long time n…
Who does? Who asked for updates blocking third-party ink, 1GB "drivers", full-color "test prints" each time you switch it on, ...?
Printing reliably doesn't sound too demanding, manufacturers reached that point long ago, and since then I haven't seen all that much groundbreaking innovation. Sure, things like wifi were added but that doesn't require cutting-edge technology - consumer devices could handle that 20 years ago, and more reliably than the printers I've used. I also haven't heard of anyone being excited about NFC in printers, and from experience I can say it's not nearly intuitive or frictionless enough to warrant the integration.
Earlier quoted context omitted.
More software is fine IMO. More software on critical path ain't. Have the ECU only do the engine thing. Have the AC control just do AC control. Decouple dependencies and make it as simple as possible. Old cars already do it. Blinker switch send signal directly to light controller, not to some central box deciding what it should do with it. If something needs config in addition to control signals, have it keep it own…
According to the car, the stability control system wasn't working. Cause? Obviously a broken fuel injector. The stability control system talks to the engine ECU to control the torque if there is a lack of traction - it is notified of this by the ABS computer. Broken Injector=No ability to manage torque, hence traction control warning. Sitting here now, that makes perfect sense. In horizontal Scottish rain - less so!
Sure, old carbie with distributor might've just ran with 3 cylinders , but that also might damage something.
Also auto makers don't really want to give user sensible error messages or even just metrics because without experience they might just misinterpret it as different problem.
For example if car have oil pressure gauge it is either nearly fake or heavily filtered. Oil pressure changes according to load but gauge going up and down might cause user to think something is wrong with car...
Earlier quoted context omitted.
Do you oppose running camera software in a separate process? I think it makes sense. Camera process might crash and will be restarted, this should not cause restart of the entire shell. What people should understand is that container in Linux is just a separate process running in powerful chroot (which isolates not just file tree, but also process tree and other things). So the same reasoning which applies to running…
It's not just the camera process though - containers ship an entire OS (except the kernel).
Earlier quoted context omitted.
Lol. Reminded me of this - https://youtu.be/cfTIjuW6SWM Fwiw - I am a kubernetes fan. Just not in cars.
If you're a k8s fan but don't consider it reliable enough to do anything even next to but independent from safety critical systems then that's not exactly a glowing recommendation.
Earlier quoted context omitted.
I agree. Microservices are a great concept for a lot of problems. But now I constantly see way too small services. Every tiny piece of software gets its own service and its own software lifecycle (including versioning and deployment). And what happens now is, that you need a huge effort to integrate all those components. End to end system tests get much more important, but are still harder to do than simple unit/inte…
You are blaming cultural issues on technology. You have the same integration pains with libraries too. In general if your teams are not aligned, it doesn't really matter if they are developing microservices, libraries, or one spaghetti ball mess, its going to be problem anyways
Because technology almost always carries cultural values with it.
Earlier quoted context omitted.
Do you oppose running camera software in a separate process? I think it makes sense. Camera process might crash and will be restarted, this should not cause restart of the entire shell. What people should understand is that container in Linux is just a separate process running in powerful chroot (which isolates not just file tree, but also process tree and other things). So the same reasoning which applies to running…
Containers usually ship their own libraries, which means less sharing, more disk usage and higher memory pressure.
I've done this analysis for lots of software before, Windows has a really nice tool called Process Monitor that I've used to find huge slow downs before. Point it at a process and it'll tell you the every bit of IO that the application does, and at that point you can just start digging and opening bugs.
IMHO almost every piece of software of any significant size horribly misbehaves. Opening the same file again and again, writing out lots of tiny temp files, reading the same key from the registry (or some config file) over and over again , and worst of all, using fixed timeouts waiting for a task to complete instead of doing the work to make things properly event based.
On that last note, timeouts instead of event callbacks (or some sort of signaling system) is the cause of so much slowness across our entire industry. If something you are doing on a computer takes a human noticable amount of time, and you aren't throwing around tens of GBs of data or waiting on a slow network, then you are flat out doing something wrong.
Earlier quoted context omitted.
> The printers of today are awful landfill fodder compared to the Okidata's of the 90's. Pure simplicity and speed vs FULL COMPUTERS, with scanning, faxing, and every other imaginable feature crammed in with zero hope of doing anything other than replacing the toner. The first Laserwriter in 1985 had more processing power than the Macintosh it was sold to accompany. Printers have been full computers for a long time n…
> As we expect them to do more and more Who does? Who asked for updates blocking third-party ink, 1GB "drivers", full-color "test prints" each time you switch it on, ...? Printing reliably doesn't sound too demanding, manufacturers reached that point long ago, and since then I haven't seen all that much groundbreaking innovation. Sure, things like wifi were added but that doesn't require cutting-edge technology - con…
The majority of my printing happens from my smartphone, so my printer needs to be on wifi, and needs to be able to reliably print from Android and iOS.
Accordingly, it needs firmware updates because phones break how they work all the time.
> things like wifi were added but that doesn't require cutting-edge technology - consumer devices could handle that 20 years ago
Not just wifi, multiple protocol for connecting to printers. Also that wifi needs to be 5ghz so I don't have to switch over to a 2.4ghz legacy network every time I want to print (which I had to do with my previous 2.4ghz only wifi printer!)
The onboard touch screen + embedded OS means I don't need to set anything up through a computer or smartphone app.
FWIW I have a black and white laser printer from Brother, I've never had to install a driver, I just plugged it in, typed my wifi PW on to the touch screen, and after a firmware update on first use it has happily been allowing anyone connected to my wifi to print w/o any hassle.
Folding a piece of paper (just like binary numbering) 6 times will provide you with a stack of 64 sheets.
They did not have a performance increase of 64 times.
This is identical to the idea of stating "magnitude" as being the number of times based on 10.
How wrong am I?