trepetti

The double blind process only requires that this be done during the review drafts. The final camera-ready version for publication can use the first person without compromising the integrity of the review process. I don't think the editors would remove self-referential text from a final draft after the paper had been accepted.

You do not have to censor: you simply refer to yourselves in the third person to make your shared identity plausibly deniable. A work that is worthy of being of publication should largely be able to stand on its own anyway. This may have the effect of reducing minimum publishable unit (MPU) CV spam papers as a bonus.

The title is misleading as written in the article. It should be "The Uselessness of Phenylephrine as a Decongestant". Phenylephrine is a lifesaving medicine in emergency medicine to increase the blood pressure of people with hypotension.

Practical Linux phones cannot come soon enough. I am done with this nonsense. It is abundantly clear that organically developed open source software for critical tasks such as this will always be superior and likely safer due to the informed user/developer-base's ability to deal with problems as they arise.

I'm surprised the article never mentioned War Plan Red: https://en.wikipedia.org/wiki/War_Plan_Red

It also has a proprietary PHY protocol, which always struck me as an major downside to something whose adoption is closing to making it the next de facto standard. DASH7 [1] is an interesting alternative in this regard, good for urban areas, but not quite as long range for very sparse nodes in a rural environment. It does not the same duty cycle limitations that LoRa has and is actually used to complement LoRa even on the same device in some interesting case studies [2] which come from Semtech themselves (the patent holders on the LoRa PHY).

[1] https://dash7-alliance.org/ [2] https://tech-journal.semtech.com/making-the-most-of-the-unli...

Just to calm your nerves: place and route algorithms are often classical AI anyway, the things that is changing is what still is and isn't referred to as "AI". The cool thing about this work is that it is looking at higher level parameters about layout instead of the kind of heuristic algorithms you see in APR. Would be cool to see this in tools one day.

Maybe as opposed to a theoretical treatment? In academia, there is a dichotomy in CS research between systems and theory, which may have been what they were getting at.

A code density prioritizing modern ISA is something that I've thought a lot about too. Would be an interesting possibility in the embedded space. I think that there are certain tricks that can be used to speed up the realignment problem, too.

One of the interesting comments in that article was how they pinned limited width of x86 decode implementations on variable instruction length. There are obvious code density benefits to the x86 variable length approach (especially in immediate encoding), but I guess the need for realignment creates long critical paths on the frontend. I wonder if the more constrained variable instruction length of RV64GC (32- and 16-bit instructions only) will be able to similarly scale up to 8-wide instruction decode like Apple has been able to do with AArch64.

It has really been cascading process delays dating back to 2014 when 14 nm got pushed back when Broadwell was supposed to launch, too.

(I am also biased because the designs I work on are small enough that ECP and presumably upcoming Lattice FPGAs are plenty. I am excited by the Xilinx reverse engineering efforts, too. But there seems to be less official interest than we see with Lattice in supporting the OSS efforts.)

Random ones requiring keep attributes for no reason on larger designs to keep stuff from being inferred away erroneously. Certain issues with limitations on SV interfaces only supporting constructs used in the "IP integration" scripting as opposed to the full language spec. I am sorry if I came off as overly negative, but I really think the FOSS EDA tools are going to lap them unless they open up somewhat.

Yes, and it is also a bug riddled mess that is prone to synthesis errors. I am hoping maybe the AMD acquisition will encourage them to open more things up to get more eyes on the synthesis flow and allow more recourse/debugging when issues are encountered.

Yes, apparently some US plastic recycling programs amounted to fraud in that they would simply export waste without due diligence about the overseas sites they were shipping them to. There's a reason why "reduce" and "reuse" come first in the old adage before "recycle".

Early on, I remember there being concerns about forcing ethanol in gasoline used in maritime applications on the theory that the water soluble ethanol would draw water in at a higher rate osmotically and cause corrosion in fuel pumps. I don't know if there have been any long term studies on it, though.

CadQuery is another good options to do parametric CAD from Python without using a DSL:

https://github.com/CadQuery/cadquery