[1] https://mikeanthonywild.com
355 karma · joined December 2, 2013
[1] https://mikeanthonywild.com
Thank you!
Could you expand on this?
- Memory leaks (grows from about 1GB to 11GB and starts swapping in a couple of minutes when editing existing IP)
- Single-threaded synthesis is slow (though isn't limited to Vivado specifically)
- Failing after 20 minutes of synthesis because of errors that would be easy to check at the start
- Placing debug cores can result in needing to synthesise, find something went wrong, delete debug core, re-synthesise, re-add debug nets, synthesise again...
- Aggressive caching results in it trying to find nets which were changed and no longer exist, despite re-creating the IP in question from scratch
- Vivado creates a ridiculous amount of temporary files and is a royal pain to use with version control (there is an entire document which details the methods to use if you want to create a project to be stored under version control)
I've been playing around with IceStorm for the iCE40 device and it's an absolute joy to use: fast, stable and simple. I appreciate that there are a lot of complex tools and reports which Vivado provides, but I would much rather use an open source tool like IceStorm for synthesis alongside the advanced tools from Vivado.
Like I said though, it costs us practically nothing to run and it's been a great learning experience so far - I don't see any reason to give up just yet.
Monetisation will come primarily from providing analytics to restaurants. Because of the way the app works, we can go to a restaurant and give them info like "x number of people were interested in going to your restaurant, but they went across the road to your competitor instead". In addition to analytics, we planned to do the usual promoted results and coupons etc.
Here is a brief explanation in a German computer magazine: http://www.heise.de/ct/artikel/2-Klicks-fuer-mehr-Datenschut.... Their implementation: http://www.heise.de/extras/socialshareprivacy/ (which I believe this is a fork of?).
I would really love to see more sites adopt this approach. Tracking users in this was is completely unacceptable.
Does anyone know what's actually going on with this?
[1] https://www.reddit.com/r/pcgaming/comments/4a5edx/psa_window...
[2] https://www.reddit.com/r/pcgaming/comments/4a7bkp/psa_micros...
[3] https://np.reddit.com/r/technology/comments/4a0asv/warning_w...
[4] https://www.reddit.com/r/pcmasterrace/comments/4a59p4/psa_wi...
[5] http://www.cnet.com/forums/discussions/forced-to-upgrade-fro...
[6] https://news.slashdot.org/story/16/03/12/1634229/windows-10-...
It's worth noting that arachne-pnr (https://github.com/cseed/arachne-pnr) is written by a different person (Cotton Seed).
{
"1":"betterthreads provides an enhanced replacement for the an enhanced replacement for the python this isn't actually a true thread instead it uses gevent to",
"2":"the widely-accepted solution is to set a timeout on our blocking functions so we can periodically check a which we set from the main thread to indicate we want the child thread to stop",
"3":"if the thread is still alive the when the *timeout* argument is not present or ``none`` the operation will block until the thread terminates",
"4":"`runtimeerror` if an attempt is made to join the current thread as that would cause a deadlock",
"5":"`join` a thread before it has been started and attempts to do so raises the same exception"
}
That said, I think to summarise that particular would require a certain level of domain expertise, something which a general bot couldn't provide.The best approach I've seen so far is the excellent Nand2Tetris, however it can't run on hardware due to the custom HDL it uses.
I've always been captivated by the Homebrew Computer Club and have been considering putting together a set of tutorials which go through the steps of creating a really basic CPU with an FPGA (perhaps a simple RISC-V core?) and writing a toy OS to run on top of it. A lot of this stuff you learn at Univeristy, but not everyone has that opportunity. I'd like to see a comprehensive guide which walks someone through every step and teaches the fundamentals of computer architecture, hardware design and systems programming in a fun and hands-on way (it's how I've always learnt best).
Would anyone find a 'Retro PC from scratch' resource useful?