But control threads like a clock/reset aren't the main idea. Look at the example RISC V core for the design style we're attempting (https://github.com/cjdrake/seqlogic/tree/main/tests/riscv/co...). No async/await or yields anywhere. It's described in a structural way, and a couple layers of Python hide the details.
Correct in this case. In src/seqlogic/sim.py there are four usages of 'yield' keyword that suspend the current coroutine and return control to the event loop.
Slightly related, I wonder what opportunity cost the Israeli tech sector will incur from this conflict. Instead of developing their startups, lots of young people are busy with warfare at the moment.
"31 countries and economies maintained or improved upon their 2018 math scores, including Switzerland and Japan. Countries that did so shared some common characteristics, including shorter school closures during the pandemic and fewer impediments to remote learning, per the report."
Who could have predicted that lockdowns and Zoom class would have a negative impact on education? I'm shocked.
Came here to post this. The headline is yellow journalism. There's no reason to mention Oracle. Forbes used to have a strong brand. Seems like they print a lot of trash these days.
It wouldn't surprise me if we see more of a trend towards content curation that isn't based on AI recommendation engines, but rather humans who are either friends or celebrities/experts.
Some ideas:
* My friends are watching this
* Martin Scorsese's film influences
* Cinemassacre Monster Madness watch list
What a great project! The author should do a talk about his experiences. I searched for something like this on YouTube, and only found this: https://www.youtube.com/watch?v=0_-TRvbo54Y.
Several well-known people in tech are notorious jerks. So I don't think being kind is a necessary condition for career success (though it can't hurt). But I suspect it's necessary to have a happy life.
With all the news lately about Bazel, kind of refreshing to talk about this war-horse.
Consider:
1. Paul Graham recommends to "do things that don't scale".
2. Google designed Blaze when gmake started to scale badly.
Chances are, gmake plus some shell scripts and language-dependent build flows is all you really need. Worry about replacing it with something more scalable when you actually have that problem :).