We love to #interpret you, sometimes also #compile :D

"Compiled vs. Interpreted Languages: How they work and their pros/cons. Compiled languages offer efficiency but come with overhead. Interpreted languages offer flexibility and smaller program size. #Programming #CompiledVsInterpreted

https://www.freecodecamp.org/news/compiled-versus-interpreted-languages/

pgfplots mit mehreren #Compile-Jobs dauert immer noch länger als manche #cxx Projekte zum bauen. Was hab ich da nur angestellt bei meiner BA? #TeXLaTeX

Me, while trying to #compile an old program from #source:

🎶 I pretend that I'm kissing,
The #libs I am missing,
And hope that my dreams will come truuue.

#DependencyHell

#Compile #Program #Code #Comics

Habe heute ein bisschen mit #Docker auf meinem #Raspberry Pi herumgespielt. #Installation der Containerumgebung und klonen einer App mit Git, die ich dann konfiguriert und kompiliert habe. Läuft das immer so langsam? Der #Compile hat über 30s 🐌 gebraucht (ohne Download). 🤨

On #HuCardHuesday here’s “Seirei Senshi Spriggan”. This 1991 vertically scrolling shoot-em-up was developed by #Compile & published by Naxat Soft. It was originally intended as a sequel to MUSHA Aleste for #Sega #MegaDrive before being transferred to #NEC #PCEngine.
#Retrogaming

The Guardian Legend Shrine
Part of the network of the similarly venerable shmups.com, The Guardian Legend Shrine is nearly the ideal game shrine, a static site crammed full of screenshots, strategy tips, fan art and fiction, and generally just everything of interest to a fan of the NES game.

"BOO!
https://setsideb.com/the-guardian-legend-shrine/
#niche #retro #alyssa #bluerandar #broderbund #compile #fanwork #guardianlegend #mooniitani #nes #niche #oldweb #randar #retro #shrine #zanac

STILL Trying to compile all the appropriate #FFMPEG #libraries statically and then FFMPEG 5.1 on #macOS.

(Please don’t tell me #macports or #homebrew! I want a portable #static build WITH ENABLE_HDR10_PLUS=ON, HDR, and other flags)

Been at it for 3 days and always some other problem with a dependency - or STUPID things like #x264’s lack of a “—disable-shared” flag to the ./configure! 😡

Sometimes it’s #arm64 #compile issues, others it’s the #intel! ARGH!

In #bioinformatics, and #scientific #computing generally, raw #data is never ever in a usable form.

This is one of the many things #Hollywood persistently gets wrong: the #scientist / #hacker / omni-computer-geek opens up the file, stares at a bunch of #numbers or #symbols, and says, “Ah hah! If I #compile the #HTML to reverse the #polarity on the #IP #gateway, I can #deconvolve the #DNA sequence to #backpropagate the #cellular #metabolism of the #alien #plague! Oh, and make #dinosaurs if you want, but that’s extra.”

Bonus points if the screen projects on said scientist’s face and reflects from the inevitable chunky-framed glasses. Scribbling equations backward on a transparent whiteboard may also be involved.

#Scientists, as I have said many times before and no doubt will need to say many times again, are people. We’re pretty good with numbers, yes, as a rule. But what we’re good at doing with those numbers is not reading and understanding them. It’s using them as the raw materials for product which makes sense to the human brain. Words, pictures, and a MUCH SMALLER number of numbers is our goal. Also continued #funding, which is about the kind of numbers everyone understands.

Before we process the numbers, we need to “#preprocess” them. There are several intermediate steps between the really raw data and the cover story for next week’s issue of Nature. Preprocessing is where we turn the glowing symbols projected onto our faces into something that kinda-sorta makes sense. It’s still not really readable, but people looking at it, who know what they’re looking at, can tell what it represents.

Usually this is in the form of one or more #tables: for a familiar example, think of an #Excel workbook with several large #spreadsheets. (In reality, storing data in Excel is a terrible idea, but I’ll stick with that metaphor.) Nobody’s going to read and digest everything in the workbook. You can look at the headers and a few of the values and at least have an idea where to start. Preprocessing gets you to that point.

For most types of data, preprocessing is fairly standardized. You don’t have to write your own code: someone else has already done that work for you. Just pick a #software #package, run the raw data through it, glance at the output to make sure nothing went horribly wrong. Now you’re ready to write the code only you can write, to discover the Secrets of Life Itself. Now is the time for SCIENCE.

Or Nature. Or The Journal Of Obscure Subfield Ten People In The World Know Exists. Or a tech report. You know, whatever.

Careful readers will have noticed the word “fairly” above. In fact there are multiple #algorithms to choose from, and multiple packages implementing those algorithms, and #documentation written at 3:00 AM by an exhausted #postdoc who really just wanted to check the #cell cultures one last time and grab the remaining half a chicken salad sandwich from the break room fridge and go home and crawl into bed for a few hours’ sleep before dragging ass back in tomorrow. Shower optional.

Other exhausted postdocs and their harassed #principal #investigators, who get somewhat more sleep and a somewhat finer grade of chicken salad but are much more worried about upcoming funding application deadlines, may or may not bother to write down which package they use to preprocess their data. Or what specific parameters they tuned. Or if they even know how they’re supposed to use the damned thing: there’s a really good chance they just ran the data through on the default settings, got something that looked reasonable, and called it a day.

Amazingly, most of the time this doesn’t really matter. Data has a life of its own. The bigger the data set gets, and these days nearly all data are “big data,” the more likely it is that any reasonable method will produce similar results. Good thing too, otherwise science (and Science) would grind to a screeching, shuddering, smoking halt.

Sometimes it matters a lot. Careful scientists check, just in case. I try to be one of those, and when I’m not, my coworkers pick up the slack. Luckily for me, for most of my career I’ve found myself in the company of those who live up to that standard, and I can mostly convince myself I do the same. Another item on Hollywood’s long list of sins: science is not a solo enterprise. In fact it’s deeply social, which is one of several reason why the stereotype of scientists as loners is a load of crap. But I digress.

In case you’re wondering if this has a point, yes it does, and here it is: all the above is why my boss recently sent me a message saying, “Woah yeah ok so maybe you do need to process from raw after all. B/c idk wtf that is.”

Without any irony at all: I love my job.

I apparently am missing a bunch of use flags for #rust Yes I know #gentoo provides a binary, but I prefer to have everything compiled.

Guess I'll be back to it in 40 minutes or so. I don't remember how long rust takes to compile but I know it's a while.

#linux #compile #justGentooThings

#writinglife: Writing a novel and #writing a computer program are surprisingly similar. Both use syntax and #grammar. Both have a vocabulary. You make statements of truth. You build the novel or program.

In the case of a #program, you run it. You look to see if you get sensible output. If not, you fix what you wrote and try again to see if you get sensible output until you #publish it.

In the case of a #novel, you create #characters and settings, and #compile them into scenes and chapters, then you write the ending. You look to see if you have a sensible story. If not, you fix what you wrote—whether backfilling #foreshadowing, correcting #plot points, or adding/deleting scenes and/or characters—then you try again to see if you have a sensible story until you publish it.

Writing is an iterative process in logic. I'm writing the ending to a novel right now, the one that goes with this post: https://eldritch.cafe/@sfwrtr/109577332108747664 .

I've figured out where all the threads my characters generated tie up. Yes, by knowing the ending when I start to write the novel (and not all that much more), I experience and record what the characters do as I write their scenes. I corral them as I go, and keep them on-program, but incorporate the revelations.

Then comes the point when the subplots all come to a climax and they must create a sensible story. Last night I jotted down everything that needs to happen in that chapter... and surprisingly, for a #firstdraft, it made sense. For >100K words, thank goodness, right?

That doesn't mean I won't fix up things earlier in the story to make it better. Perhaps cut verbiage, remove inadvertent #redherrings, move some parts around...

The important thing is: It's a sensible story. Better: It will soon be complete.

HowTo build / make latest #brotli Windows 11 #binary
I couldn't find latest brotli binary for Win64 / x64, so here is how to #compile it on Windows, for #Windows
https://gist.github.com/roelds/fabe8489be8f53751310b65c6dd1b11c

@gnome @google @fedora @gitlab @FlatpakApps
See also #pascal #turbopascal
#Lazarus' slogan "Write once, #Compile anywhere"
It promotes open source because the source code can be easily tested and studied by others. Also because it compile to native code, it does not need virtual machine to run https://mastodon.world/@giuliohome/109614691518037654

@gnome @google @fedora @gitlab @FlatpakApps

#Lazarus' slogan "Write once, #Compile anywhere" is similar but I think is better. If you got the source code from someone or the Internet, you can compile it on your computer with little or none of modification even your computer's OS and hardware is different from the author. It promotes open source because the source code can be easily tested and studied by others. Also because it compile to native code, it does not need virtual machine to run

I managed to overcome yesterday’s frustration and had a close look at this article:

Practical Makefiles, by example
http://nuclear.mutantstargoat.com/articles/make/

With additional documentation from https://makefiletutorial.com I managed to compose a decent, efficient Makefile.

I just wish it could be easier.

#cpp #cxx #c #softwaredevelopment #make #compile #build #programming

#compile #programming #coding #softwaredevelopment

AST Explorer

https://astexplorer.net/

#AST #JavaScript #apps #tools #FrontEnd #transpile #compile #syntax #tree

Time for a little #introduction. I started coding on an Brazilian #Apple2plus clone when I was just a little kid, but soon moved to the #msx because of the very powerful #BASIC I used to write my own little programs. Also because it had a great software library from the likes of #Konami, #Compile, #Microsoft and #ASCII. So, after tinkering with computers in all shapes and sizes for a while, I became a software engineer since my other interests are not as marketable as writing software. :-P

A new #blog post appears!

Did you know there's a complete C compiler inside the DMD D compiler? Check it out with me.

https://briancallahan.net/blog/20220704.html

#compiler #compilers #compile #C #D #dlang #Unix #OpenBSD #FreeBSD #NetBSD #DragonFlyBSD #Linux #program #programming #code #coding

A new #blog post appears!

I discuss porting chibicc and kefir, two C compilers, to #OpenBSD.

https://briancallahan.net/blog/20220629.html

#compile #compiler #compilers #C #Unix #FreeBSD #NetBSD #DragonFlyBSD #BSD #program #programs #programming