HN user

lloydjatkinson

43 karma
Posts0
Comments43
View on HN
No posts found.

Read up on flyback diodes. There are additionally numerous motor driver IC's specifically for this purpose.

A flyback is critical in anything involving a magnetic field, especially a collapsing magnetic field from a motor that stops spinning. The field collapse induces a relatively huge current which will be many many many times greater than anything a normal component is designed for.

Not having one is like driving your car down the highway without any breaks. The only way to stop is to crash.

Anything involving collapsing magnetic fields, eg solenoids, relays, motors, absolutely simply has to have a flyback diode.

So your suggestion is actually introducing a second magnetic field, so now you've doubled the chances of blowing up your Pi and or the MOSFET.

Whether you're using a transistor/MOSFET directly with a motor or instead with relay + motor you need the flyback diode.

privileged spec

I hope this refers to ring-0-like instructions such as x86 STI, and not some kind of OEM/manufacturer "you can only use this set of instructions if you pay us" type privilege?

Then C++ has failed. If it has so many competing standards and subsets, then it is too fragmented. This is why when you see C++ written in one standard it looks like a whole other language when you look at other C++.

If after a decade there are so many details still obscured from you, then that's pretty much again a fault of the overly-engineered and tacked on language called C++.

Other mainstream language work fine and allow you to still write clean and modern code without having literally dozens of subsets and implementations. So why is it that C++ feels the need to have so many?

In the embedded world they're available and not even super new,

I feel you might be understating this! FPGA's and ASIC's have in fact been in use for decades now, they are very much ingrained into many high end products. Any digital oscilloscope has an FPGA, and has done for a very long time, for example. These are often either used in combination with a CPU for the UI part. The CPU might either be an IC on the PCB or what is quite popular is having the CPU be a synthesised one programmed into the FPGA.

ARM, for example, have a whole architecture specifically designed for optimal FPGA synthesis.

There are a number of relatively cheap SBC's out there with an FPGA too. http://linuxgizmos.com/tiny-sbc-runs-linux-on-xilinx-zynq-ar...

Fully agree. No need for the shitty parts of UNIX to be in a new OS. Use full names. I've never used OSX/macOS but I do admire how they've gone about doing the whole UNIX thing, there seems to actually be some standard to it unlike the LSB and from what I gather to uninstall a program you just delete it's directory. Try doing that on literally any other mainstream OS!

Very similar to something I'm working on. Except in my case I have an interface that the consumers implement to be able to talk to their service/database/whatever. It's designed for time series data (e.g., cpu usage, room temperature, that kind of thing). It's meant to only allow for numeric values and strings. But because there is no base type or interface for numeric types I unfortunately can't do something like:

    public Result WriteValue<T>(T value) where T : INumeric/Numeric { }
https://stackoverflow.com/questions/32664/is-there-a-constra...

:(

So instead the interface has an identical method for ints, doubles, floats, decimals, strings...

Rust is also 32bit/64bit. That's totally fine (obviously) for PC-like situations and servers and more powerful embedded systems, etc.

But there are literally billions of 8bit and 16bit embedded systems out there, many of which have a C compiler.

No HN only allow political ideologies or narratives they agree with. The moderator team do not hide that they are SJW's.

As another example, currently HN's narrative of choice is how Uber is literally the worst thing since Hitler and you can't go a week without seeing 3 or 4 top-voted links bitching about Uber. Perhaps some people like being able to conveniently travel from point A to B without caring about what some whiny keyboard warrior hates about Uber this week.

I'm not sure how you can equate a corrupt money stealing government with a genocidal regime in which tens of millions of people were killed, imprisoned, and made refugees; while also drawing all the super powers into a protracted and bloody war, arguably we are still feeling the effects of today.

What are the differences between Vue and React? I use Angular unfortunately, and ideally I'd like to be able to learn some non-SPA stuff too. I've only really looked at React and it seems nice.

I'm not a web dev by choice, I get dragged into it with work. So I'm not that aware of all the options. Would you say Vue and React are even comparable?