Very good point. For IoT widgets and perhaps even wearables, I'd rank things by power, size and cost coming in a bit later. The old way had cost first but people are seeing the light.
Newbie question: why isn't releasing beam source files for an existing popular rtos(e.g. Freertos) an easier path to take? Is the issue posix support by the underlying rtos combined with tool chain headaches?
Interesting comment on being called fat. I'm a bit, shall we say, big boned. And I experienced two odd instances where a Chinese person I barely knew casually remarked how fat I was. It was otherwise a pleasant conversation and had me a bit confused. If a stranger said that to you in America, it would certainly be considered mean.
Not in the rest of America (I.e Latin America) where that would be common and even a term of endearment (gordita). It's common in South Asian cultures as well.
To me Americans are focused on being PC while not dealing with the root cause. In the case of "fat" the root problems is that Americans tend to shame & hate those who are fat. It has become a negative stigma, but instead of attacking the root cause we have removed fat as an adjective and think that by removing the hateful term (hateful by usage not by definition) we have solved the problem.
You would be surprised to learn that in some impoverished countries like Nepal being called fat is a compliment. People use same word to describe someone who is fat or muscular. It is a compliment because being fat means you are rich enough to have more than enough to eat.
I've been anti hw problem given it requires no investment of time by the potential employer. If it was a short hw .. say max of an hour or two followed by a discussion of it (where discussion was the interview) I might be okay with it. I'm definitely not okay with the hw being step 1 of the usual shit process.
It used to work that way before Google messed it up. Microsoft was known to have a "difficult" process .. a cakewalk by today's unreasonable standard. Companies didn't try to emulate Microsoft in those days .. I don't know why everyone wanted to copy Google.
Same reason many wanted to emulated Microsoft — they don't know any better. Many claim "it works for Google" without giving it much thought (not a surprise in today's world) but does it really? Google, among others, is a hot mess and precisely for this reason — they hire people who are great in passing tests but can barely function socially and professionally.
But hey — it keeps them busy and removes them from competition, so it's not a bad thing.
The parent is right. A lot of people in Toronto are dabbling in real estate .. especially condos. Some builders are offering a mgmt company which rents for you. In a previous building I was renting in, it was surreal to see people pick their keys from one person and handing it over to the mgmt office people right across. These were crazy priced, super fancy condos.
I just started learning about opencores and various buses (wishbone, axi, etc.) I am surprised many designs say spartan 3 or some vendor specific Fpga. I thought an Fpga is an Fpga. Yet, I see logic analyzers, open source softcores, etc. target specific devices. What gives?
Agreed. It is crazy. I have a strong dev background and got a PhD. I love to learn .. any free time I get, I further my knowledge. Since I don't do it to improve skills, I have freedom to learn whatever I want. For a few months, I was obsessed with semiconductors and MEMS. These days, I love hacking FPGAs. Before that, I was playing with deep learning with torch. Point is .. you do not need to quit your job for learning. Agreed with parent poster .. save cash, attend meet ups/events to find like minded people ... the coding/hacking culture is awesome but it is a treadmill. There will always be new stuff coming out. You need to focus on concepts more than specific software or middleware. Have you heard of "papers we love"?
