Not at all. The Volt is great. No major issues. Not sure why your loosing your shit over something you seem to know nothing about.

Over bloan. Software does not age but security does. Other things that do not age well is specialty tech hardware components. Batteries are a question too.

I know my volt at 10 years does not have a viable oem battery replacement (back ordered and nutty price). I can get a reasonable after market battery though.

Yes good analogy. Just my guess. Been a long time since I actually worked in the field.

There are various designs of backlights. They typically have a stack of loose components in an assembly. By loose I mean not totally fixed but not too free. They have to free float enought that temperature changes do not cause issues. They also have to not stick, warp, or buckle over time. Harder to engineer then you might think.

So consider what might happen if for example the top backlight film might buckle some then stick to the back of the lcd. The film might deform which would change its optical properties. Then later thermal cycling might cause release. It might do same elsewhere.

Not saying this is mechanism, but just example.

Edit: Keep in mind the LCD is glass, and the backlight components are plastic. Very different thermal expansion coefficients. Then add LED or CCFL lighting and you have a big changing heat source. Add on top of that humidity changes too.

Backlight I think. Probably film pack warp / buckle / wetout. Just a guess.

Edit: Worst part looks kind of like a wrinkle.

Sounds to me like the backlight behind the LCD. They have components which could potentially sag, stick, or warp. White screen is probably best way to see. Also look at various angles. May be more visible at some angles then others.

Hard to unsee. I know this feeling. I used to work in the industry years ago. Displays are never perfect and hard to unsee things once you see them especially when it was part of your job.

See the edit to my comment. If not sharp, could be warping of films in backlight.

That is an interesting one. LCDs as far as I know do not usually burn in and if it is moving then it is not really that anyway.

I will interested what others come up with?

Edit: Is sharp or gradual. Might be warping of films in the backlight for example if not sharp. Just a thought.

I like Joplin, but it is a note taker not an office suite. So kind of depends on what you want.

You can just use LibreOffice. On Android the app I have is Collabora. The server I use is Nextcloud though it could be anything that LibreOffice and Collabora can work with. I think there is also some sort of web version too of LibreOffice, but I’ve never tried it. Maybe called “LibreOffice Online”?

Common:

• Procedural, preferably Functional. If you need a procedure or function use a procedure or function.
• Object Oriented. If you need an object use an object.
• Modular
• Package/Collection of Modules
• Do not optimize unless you need to.
• Readable is more important then compact.
• Somone said minimal code coupling, Yes! Try to have code complexity increase closer to N then N factorial where N is code size.

Frankly everything else is specialized though not unuseful.

deleted by creator

Go might be a close 2nd language wise but not the others. All of the above have a pretty narrow application range too. Even with a good lamguage, you would have to have the libraries too and pypi is pretty big.

You can get about 10x by compiling Python using PyPy. So compiling is not nothing. Using Numpy alone is about 5x which surprised me. There is a lot of missleading stuff out there about how to make Python fast. Lot of people say CPython is pretty fast or that using a binary library like numpy is fast. No CPython is very slow and libraries are not always that fast.

Edit: Another compiler is Numba which is more specialized. It can get 30x on some code without numpy. Again compiling can help.

We will have to disagree on that. This is all problem spectific, but I have found C code integrated via ctypes, cffi, or by a C extension is over 100x Python alone. Interestingly Python, Numba, and Numpy together which is a more pythonic solution can get to those speeds too.

All of the other approaches I have tried are much slower: Nuitka, Cython, Numpy alone, PyPy, etc.

To get best speeds one has to compile for your specific architecture and enable things like vectorization, auto parallel, and fast math. Most default builds including libraries do not do that.

Depends on what you mean by compiled. Python typically translates to meta code and that is interpreted. True compilation to binary runs about 100x faster. Python is slow though there are faster versions and ways around it.

White space nonsense. Yes and no. I do not enjoy tracking down white space issues until I remember the alternative. Matching brackets, writing begin/end statements, and worst of all looking at code that appears well indented until later you find it is not. and it runs totally differently then it looks. Similar issues with semicolons.

Pretty much everyone uses LSEs these days so frankly matters less either way most of the time.

Typing thing is way over blown. What did suck before Python 3 was indeterminate type result from the / operator. You never know if it would be integer or floating division looking at the code. Now it is floating.

Yes sorry. Wrong thread. Someone was talking about AI somewhere. For Python, I agree with your comment.

Reason I started using Python. C takes too much effort, Excel VBA is nut over 100 lines. Matlab or Python would be the next step. Matlab is nuts too in many ways.