[HN Gopher] WASM to PS Compiler
       ___________________________________________________________________
        
       WASM to PS Compiler
        
       Author : lokedhs
       Score  : 54 points
       Date   : 2021-07-02 08:10 UTC (1 days ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | Gys wrote:
       | > but none target the untapped potential of the shitty PostScript
       | interpreter your printer has
       | 
       | Maybe because the options for interaction with the output are
       | non-existing ;)
        
         | ithkuil wrote:
         | You just need too hook it up to a prescript scanner
        
       | Tijdreiziger wrote:
       | Thought process:
       | 
       | > WASM to PS compiler. Huh, PS meaning PowerShell?
       | 
       | > Oh, PS meaning PostScript.
       | 
       | > Wait, PS meaning PostScript?!
        
         | Keverw wrote:
         | I was thinking it meant WASM on the PlayStation haha. I seen
         | that there's some project before but haven't been following it
         | to use WASM for the binaries on Linux. So ARM or Intel programs
         | could be compiled to WASM and only the host operating system
         | would need to be compiled natively, which sounds like a very
         | cool concept if it gained more support.
        
         | infogulch wrote:
         | Turing completeness never fails to deliver program translation
         | surprises.
        
         | b33j0r wrote:
         | So it's a print driver only for WASM source code? Yes, I had
         | the same thought, but it turned out to be Photoshop ;p
        
         | jhgb wrote:
         | Am I too old when PS means PostScript to me by default?
        
           | cesarb wrote:
           | I think it's a matter of environment, not age. If you're more
           | used to the Windows ecosystem, you'd think of PowerShell by
           | default; if you're more used to the Linux ecosystem, you'd
           | think of PostScript by default. PowerShell (and dotnet in
           | general) doesn't have much relevance to those who run Linux
           | exclusively, while PostScript doesn't have as much relevance
           | to those who run Windows exclusively (unless you have to deal
           | with certain kinds of printers).
        
           | cogburnd02 wrote:
           | The only thing you are is too correct.
        
       | jackdaniel wrote:
       | Brilliant :)
        
       | tedunangst wrote:
       | Bring back NeWS and we can eliminate the browser entirely.
        
       | spullara wrote:
       | Back in college I wrote some Postscript code to change gnuplot to
       | do some 3D stuff that I needed for a visualization project.
       | Fortunately, I don't remember it at all.
        
       | edgeform wrote:
       | > The so-called compiler implemented uses the dumbest possible
       | implementation
       | 
       | I love remarkably blunt comments in code. The Quake III code that
       | caused the uproar recently with Copilot probably being the most
       | famous example.
        
       | amelius wrote:
       | How to access its ethernet port?
        
       | xbar wrote:
       | Timely. I've been looking for ways to abuse the HP ink-junkie in
       | the corner.
        
       ___________________________________________________________________
       (page generated 2021-07-03 23:00 UTC)