What scientists must know about hardware to write fast code
“The aim of this tutorial is to give non-professional programmers a brief overview of the features of modern hardware that you must understand in order to write fast code.”
It's OK you are #unnatural. Hail BSD - the little #devil. Ghosting in the machine? #Coast and #Surf baby!
More Lobster tips:
1. Fear, fire and fury is a big #bug
2. Bring back #compiling time to #relaxation
3. Insecure apps are the new #open sauce
4. #Crypto daddy O! Spooky ... bwanks
5. Be the #Kernel, #cosmos, differential ...
♾️ :3843-blobiloveu: :4817-blobbottleflip:
@profoundlynerdy Yes, that might be a bit thin. For comparison:
i7-2600, 16 GB, dev-lang/rust-1.71.1: about 90 minutes
i7-6700, 32GB, dev-lang/rust-1.69.0-r1: about 50 minutes
Xeon W-2255, 64 GB, dev-lang/rust-1.71.1: about 30 minutes
EPYC 7352 24-Core, 128 GB, dev-lang/rust-1.66.1: about 15 minutes
Dear social search; we've recently started compiling with C++20 and we're getting a ton of warnings for lambdas. While I'm not in a position to fix them, I need to suppress those warnings so I can see actual errors.
Problem is, google's #search is just bad and keeps giving me results for "how to make warnings into errors" which is not what I want.
Edit: -Wno-deprecated is in the docs. But not how to use with cmake.
Do you know?
Do you want to compile programs for AVR microcontrollers (or Arduino systems) on the command line using a Makefile?
I am developing a tool for that: ucmf - microcontroller make framework. You create a simple configuration file for your project with all source files and then call ucmf. You get a Makefile where you can just execute "make" followed by "make upload" to compile and upload your program.
Project page: https://codeberg.org/ncc1988/ucmf
#unity #unity3d really shat the bed, and speaking as a full-time #panda3d simp, now seems like a good time to simp hard and get some people to see the light. It's battle-tested for #MMORPG and #VR by #Disney back in the day (#BSD3 now). Use #python to write your #3D games so you don't waste another minute on #compiling. Has -all- the features, from skeletal animation and glsl to a robust shader pipeline to collisions and physics. Not to mention amazing community! #gamedev http://panda3d.org
I managed to get half life 2 running natively on the m2 macs. I did not expect having to compile the source engine to do so.
Which brings this into question: if a rando like me can port fucking half life 2 to the m1 macs, why can’t #valve do it themselves? Just compile once and that’s it.
@Linux_Is_Best I’m gonna respectfully disagree about EndeavourOS being good for newbies. #EndeavourOS is a terminal-centric distro that primarily compiles packages from source repos. Yes, you can install #Flatpak apps, but installing apps from source is kinda’ their thing, and unless you’re using a recent computer, #compiling a large app can take upwards of 30 minutes or more.
It’s still a great distro, but newbies may find it frustrating compared to Kubuntu or openSUSE.
Running nomic-ai/gpt4all-13b-snoozy takes a while to do inference; it's the new "compiling."
James Higginbotham has heavily influenced my approach to collaboratively designing distributed applications and API programs. I had a chance to sit down and discuss his methodologies in the first episode of the Compiling! Podcast. We then launched into a discussion that affects just about everyone in tech - back health and the importance of physical therapy. Give it a listen!
The recent #Gradle 7.6 release supports #compiling, #testing, and running on #Java19 - https://docs.gradle.org/7.6/release-notes.html#:~:text=Added%20Support%20for%20Java%2019
Anyone can compile open source code in these three simple steps… It’s a part of open source’s heritage, and is quite liberating
You don't need to know how to write or read code to compile it. There are many ways to install software, but you get an option not available elsewhere with open source: You can compile the code yourself, and it only takes three standard commands.
I don't have to do this very often myself (with the ease of one-click installs from repos included with distros today), but I must say it is a liberating feeling knowing you can do it, and that you have the ability to examine or change the source code if you wish, and to compile it yourself. It is the essence of what open source is all about.
See Anyone can compile open source code in these three simple steps
> There are many ways to install software, but you get an option not available elsewhere with open source: You can compile the code yourself. The classic three-step process to compile source code: $ ./configure $ make $ sudo make install Thanks to these commands, you might be surprised to find that you don't need to know how to write or even read code to compile it.
If and when I do replace it, you can expect a flurry of activity, but until then, I'll mostly only be available in short bursts. I can still do things like #research and #audio #recording, that's not an issue, but everything else is kinda on hold.
Keep calm, and Soldier on - as they say.
I wanted to show you all what a programmer's desktop looks like, I've made an interactive map you can hover over things! The power of SVG on the web.
#Linux #Compile #Compiling #Sourcecode #Pinephone #Pinetab #RaspberryPi #UNIX #GCC #GNU Howto: Compile from sourcecode. Many times package binaries are not available. In those times, when we really want to run something, we must compile from sourcecode. Here is how (user request): https://youtu.be/JDJJP0Wzg4M