|
... is when they stop responding to the needs of their users.
I work on little IoT platforms, and I have a heavy favorite (Espressif for their ESP32 line) for a number of reasons, but as a company they seem to be on a trajectory of getting a little too big for their own good. Less responsive to changing times, less agile in the face of user feedback.
I'm far from ready to abandon them, but I'm concerned about the direction of their supporting software framework, particularly as it pertains to driving LCD screens. They seem to be corralling their users to a single graphics library solution for their entire platform line, and I'm over on their github making feature requests trying to put a stop to it.
This isn't to dish on their products, or anything. They make great gear. And like I said, I'm more at the concern phase. They could very well pull out a win and surprise me on this front. It's still early, this change in the air I sensed. We'll see how it plays out.
But I don't like thinking of even the idea of this line being one I have to abandon. I've invested a lot into it, and I've become rather attached.
Which way are you headed, Espressif? Don't be Microsoft.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Are you maybe too much focused on displays?
|
|
|
|
|
No.
For starters, the display is the central way the user will interact with a typical project. This is especially true when it's a touch screen.
It is also the single biggest code sink (where all the code takes most of the project time), and the single biggest hardware bottleneck in most cases to boot, so it's where your CPU will spend most of its time.
Such that typically, projects are literally designed around their screen, both in terms of coded to the actual hardware, and structured such that the UI interaction with the screen directly dictates the overall structure and flow of the application.
It is *the* central point of most real world IoT projects that have a screen.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Completely agree
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Your 'over' reaction tells me, I was something right. While I'm working for years now with visually handicapped peoples I 'see' that something different 
|
|
|
|
|
Well, IoT devices if they're designed for people that are visually handicapped, they will be specialized for that in hardware. These are not general purpose PCs.
To err is human. Fortune favors the monsters.
|
|
|
|
|
honey the codewitch wrote: when they stop responding to the needs of their users ...
corralling their users to a single graphics library solution for their entire platform line
It sounds like there are multiple graphics solutions now available. Maybe customers were asking for a single solution, to ease porting from one platform to another?
Software Zen: delete this;
|
|
|
|
|
It's not that simple, and it's why I used the term corralling.
The latest bits have a new feature, called the LCD panel API.
It really only works well with LVGL.
Every other offering you're seeing is not using the LCD panel API, which is again, new.
By other offerings I mean, TFT_eSPI, Lovyan_GFX, htcw_gfx, and the various Adafruit libraries.
There's a technical reason they only work well with LVGL, which I can get into but it's quite a discussion, and has to do with the *unique* way in which LVGL is designed compared to other libraries.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I find this gadget on amazon.
I think it will work on 5 inch floppy disk drive, but not sure...
from specs, it may work...
diligent hands rule....
|
|
|
|
|
|
this is great info! I will buy this one for myself!
diligent hands rule....
|
|
|
|
|
This.
It seems like a lot of people, at some point in time, have started misremembering floppy drive connectors as IDE. They're not.
|
|
|
|
|
Both signal plug, signal specs and power supply plug are different from IDE.
|
|
|
|
|
|
It's been over 30 years since I needed a 5¼ floppy drive.
Do you actually need one  ?
Software Zen: delete this;
|
|
|
|
|
I am assigned to new role now: review peers' code.
do you have any good books or documents to recommend on this topic?
diligent hands rule....
|
|
|
|
|
How to Win Friends and Influence People - Dale Carnegie
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
thanks for this great book! I bought it right away as my thanksgiving gift for myself...
diligent hands rule....
|
|
|
|
|
“Your Code is Crap” - by Never Make It Personal
“Only A Moron Would Write Code Like This!” - by Offer Alternatives
Good luck. 👍
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Once upon a time there were a bunch of coders that were given some incomplete requirements. They sat is a dark room with an illuminated white board and tried to figure out what the requirements were supposed to be. Then they sat in a dimly lit pub and worked out the architecture on beer-stained napkins. Then they sat in front of glowing monitors and LED illuminated keyboards and pounded out the code.
One day, a shining knight was added to the project to review their code. He discovered that his "peers" had decided to use to twelve incompatible frameworks, eleven coding styles, ten unit test frameworks, nine different databases, eight different REST API styles, seven different TypeScript versions, six back-end languages, five UX tools, four different CI packages, three bug trackers, two ticket managers, and one partridge in a pear tree that nobody knew was part of the requirements.
The knight, now with dulled and dented armor, went to management and recommended the whole thing be rewritten. Management went to marketing with the bad news that the product would be delayed for another year. Marketing went to the CFO with the bad news that the product would be $1,000,000 overbudget and cost the customer 10 times what they had planned for the street price. The CFO went to the CEO and suggested an illegal inside trader move before the stock price sunk.
The CEO told marketing to ship the product and advertise the bugs as features the customer must have. The CEO told the CFO to freeze all hiring and fire half the developers. The CEO told the managers to outsource the remaining work. The managers told the programmers they would be in maintenance mode only.
One dark and stormy night, the remaining programmers took the peer review knight out to a lonely field where the crows crowed "nevermore" and declared the knight to be a heretic of the all the dogmatic religions in the programming world, the Vue-ites, the React-ians, the Angular-ons. The knight was burned on the stake with much functional language incantations. It was all done with svelt discretion.
The competition lived happily ever after.
THE END
|
|
|
|
|
That's the best code review story I've heard  .
All my code review stories are drab tales of rolled eyes and ignored comments.
Mircea
|
|
|
|
|
|
Southmountain wrote: I am assigned to new role now: review peers' code.
Your organization has a special role for that? 
At my company, every dev is required to take Andrejs Doronins' course Code Review: Best Practices[^]. It's brief, to the point and IMHO very effective.
/ravi
|
|
|
|
|
Hi there!
I created a website and put it on a free hosting site to which I uploaded my files, and it appeared to me well on the computer, and when I minimized the width of the browser window, the response was good exactly as I designed it, but when I open the program on the mobile, the site is very bad and not as I designed it at all and the elements Overlapping ...
Likewise, when someone else opened the site for him on his Macintosh computer, he had errors that I do not have when I open the site from my computer, even though he has the same browser as I have, which is Chrome. My operating system is Windows 10.
What is the reason and what is the solution?
Note that I have provided the required formatting codes:
meta charset="UTF-8
meta lang="en-US
meta http-equiv="X-UA-Compatible" content="IE=edge
meta name="viewport" content="width=device-width,initial-scale=1.0
Please I prefer replying from people who have experience or any successful experience in raising a site on the Internet and its appearance well on the mobile, as well as who can point me to a source where I can find the solution.
Website link:
Thanks to any replies! Much appreciated.
|
|
|
|
|
Madi - you're asking sort of a programming question - go check out the Web Development forum.
That said, this is the specific reason I gave up doing any sort of web development. FWIW, your title is incorrect. Your issue has nothing to do with a different OS. You are dealing with display geometry and perhaps browser differences.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
