1,441 karma · joined May 26, 2013
Specifically, I'm aware that Argonne National Laboratory[1] was involved in the discovery and development of this molecule, and I think we can safely assume there are other public institutions and universities involved as well.
This is just one more reason why people get alienated from the importance of public institutions they fund, and the importance of universities and academia.
[1] https://www.aps.anl.gov/APS-News/2021-11-06/aps-and-imca-cat...
But just some romance languages. Portuguese does not.
So, I bought SoundHound 8+ years ago in a Google Market promotion offering several apps for pennies (10c, I guess?). Tried it without much hope and damn it, it worked well. Sometimes it goofed, but truth be told, it may be my problem.
Also, it had the ability to identify covers in a crowded bar, or non-playback live versions. Shazam, which was very popular at the time, admittedly couldn't do any of that - in their FAQ (which I could not find right now) they even told that if Shazam recognize a live version, it must be either a playback or a player with microsecond precision repeatability.
GP must have confused with the currently better known use of tablet, which is a full-blown computer with touch screen and no keyboard.
There are, however, several limitations to it. Clock cannot be changed, for example, and usually neither can I/O, specially high-speed transceivers. This has been improving (Ultrascale Xilinx allows for reconfiguring I/O), but you still have to reserve area for reconfiguring (meaning literal area, as in a geographic region in the FPGA).
However, I/O versatility as you suggested has very few advantages to it. You need the reserved logic for ethernet to be programmed at when you plugin. Why would you leve it unprogrammed? If is simply disabled, it won't use any extra power resources, and your soft-CPU's won't be able to take advantage of these resources while you are working. Maybe you could use the area for new soft-cpus, but then you'll hit the problem of over segmenting your design and allowing for less optimization. This would inevitably impact timing constraints and area usage.
Also, FPGA programming may take minutes to finish, and always at least a few seconds. This will be very noticeable by an user and not very efficient if it has to be done frequently.
There are, of courses, good uses for that. But there is also a lot of effort on doing it right and you always risk overdoing it.
The version control should keep the code history, not the paperwork history.
What I think you're looking for could, however, use git as a platform for that. That's what GitHub, GitLab and the likes do using a web interface and there's enough extensibility and power on git for command-line or desktop tools to do it.
The internals of git are very much akin to a filesystem, by the way, and the plumbing gives you more enough access to use that in creative ways.
From the top of my head, maybe a system like this could automatically generate tags for code reviews, use merges and branching for answering to these reviews, and hooks for notifying interested parts on particular areas of code. All while the messages and reviews themselves travel on another data layer, which references git but does not mingle with it.
This separation (and even tag cleaning, for example), would be specially useful on huge distributed projects where a company or small team may have whatever development process it needs internally and sharing only the results without having to completely hide the code history.
For a crowd that proud themselves for being objective and analytical, HN has missed the point by a lot here.
I just want to set things straight. Bad mouthing Mozilla for something they have not done does not help discussing the decisions they take.
On tracking, well, you may always look the code. It's all client-side, I guess the most nefarious accident it could happen is you noticing the suggestion again and disabling it again.
Of course, there's some dynamic between the tool chain and the language itself. For example, it doesn't matter if the language has the coolest feature if the compiler does not support it, and the toolchain will help you manage more complex code safely.
The ecosystem is terrible, I agree with you. However, the lock in is restricted for the final synthesis part. Simulation is mostly done with (very expensive) third party tools, such as Mentor Graphics Modelsim, and in professional settings the build is automated to a point that opening the vendor's GUI is frowned upon.
There are some quality open sources tools on FPGA build automation, but most places I had contact with have their own internal tools.
At the time, I actually bought the book and I liked it. It was a bit dense in the beginning, and I skipped the example, but I had some good takeaways, specially on the implementation of the system, which is described in the book.