deniska

We should keep some people around who can read paper maps (and keep paper maps around too). We need to keep doctors around who can keep working without a computer. It's a civilization threatening issue not to. There might be plenty reasons, from natural disasters, to self-inflicted "geopolitics", when we suddenly have to take a technological step back, and it's in our interest to maintain "30-50 years ago" level of tech possible, so that we don't have to start all over from something resembling a bronze age.

Well, there's always… https://github.com/FWGS/xash3d-fwgs

A tool with a monthly subscription isn't a tool, it's a service.

I help my dad run a proxmox setup on a server he's got from a local craigslist analog and put on a co-location in a datacenter. It only uses a single public IP. All VMs are in a "virtual intranet", and the host itself acts like a router (giving local IP addresses to VMs via dnsmasq, routing VM internet access via NAT, forwarding specific outside ports to specific VMs). For example ports 80, 443 are given to a dedicated "nginx vm" which then will route a request to a specific VM depending on the hostname.

Just some more parameters, and it would overfit that specific PDF too.

If you ever wanted to use a modern C and C++ compiler on windows xp, 32 bit version of w64devkit[1] does target it and provides a recent gcc version.

[1] https://github.com/skeeto/w64devkit

At some point, python became the language I use the most. And its IDEs… are frankly not really great. They are doing their best, but given the dynamic nature of the language, the experience of using autocomplete and other similar features is often jarring enough, when it doesn't do what you want it to do, to be annoying.

So I mostly stuck with really simple text editors (first likes of notepad++, geany and gedit, later switched to barely customized vim). You learn the language, you learn its standard lib, you learn the libraries you use often, you learn to navigate their docs. You learn the project you are working on, and remember how things are named. I do use a simple autocomplete (ctrl+n in vim), but it's more of a typo preventer (or a typo propagator, depending on how you look at it). It autocompletes every word in open files. Which might be more handy than it sounds, because it will autocomplete stuff not typically being autocompleted in IDEs, like json keys, or file names in the open directory listings, or even outputs in the open terminal session.

As for navigating unfamiliar code bases and "go-to-definition": it's grep. Just search for a substring in the whole project. You will find the definition. You will also find some other interesting stuff, which "normal" IDE tools wouldn't look into. Heck, you'll find interesting comments, interesting name clashes, interesting usecases for a thing you were looking for. And it's a language agnostic skill. You don't need another bespoke IDE, you don't need to configure some weird LSP to navigate unfamiliar code base even in not so familiar language.

Yes, raylib does support android. I have a slightly incomplete build script I use for my raylib projects (obviously you need to take better care of signing, you probably want to build for other targets besides aarch64, your SDK is probably not installed in /home/denis, and I'm not sure whether I'm adding .so files to apk in a way modern android prefers, but it still works).

https://gist.github.com/deniska/f1ee73e18e1444eb724c01f933b6...

Some time ago many people in Russia wished that Russia will become a normal European country. I guess the wishes were granted, but not in a way we wanted.

Why it's good: you won't get a sudden slowdown if postgresql for some reason changes its plan to something much less performant.

I started with the basic family of languages. VB6, QBasic (yes in this strange order), VB.Net, PowerBasic, FreeBasic.

FreeBasic was probably the most fun of them to me: cross-platform, compiles to fairly fast running binaries, can easily interface with libraries written in C, and has qbasic syntax mode.

Because they come with not-really-multitasking OSes, with restricted access to file system and limited selection of software.

Yes and no.

Modding a game means that you have a specific starting point, the original game, which you are probably a fan of. And you may want your creation to be a part of this original world, share some (or most) of gameplay elements, design elements, story elements etc.

People modded Half-Life not only because modding Half-Life was somewhat easier than making an FPS game from scratch, but also because they wanted to explore the original story from another angle, or they liked how engine feels to play, or for whatever other reason wanted a starting point to be a complete game. Kind of the original asset store: the assets of the game you are modding.

With modern tooling packaging pure python code to be used by other python developers is a relatively painless process.

The main problem with python packaging is that it's often C/C++ packaging in disguise, among multiple OSes and CPU architectures, and that's far from being solved. Building such python wheel is essentially like building a "portable" (aka one you don't need to properly install into the system) linux/windows/macos application. That comes with a variety of caveats and requires some specialized knowledge one wouldn't pick up playing around with just python alone.

We prefer option c: add a new table/column with similar looking name. Then few years later start wondering why there're two almost identical entities, and why one of them behaves weirder than another.

Fine.

launches bittorrent client on the phone

I have a small script ran by cron (well, systemd timers) every 15 minutes which checks the current IP via https://api.ipify.org/ and updates dns entries on digital ocean (its dns service is free) if it differs from what's there.

My favorite kind of web forum engine is the one which keeps discussions threaded, but displays them in a flat list of messages ordered by time, but with quick navigation to parent and responses.

So that your ISP, or someone else along the way, doesn't put a cryptocurrency miner into the page source.

It's not a war, it's the "special military operation". Calling it a war can be considered a lie in Russia.

Gorbachev is 91 and still alive.

I was using Nexus 6 from 2014 in 2019. And honestly I would continue using it if its battery wasn't in abysmal state leading to throttling. Considered buying new old stock or trying to replace a battery in this one. N6 is a 32-bit only device, that's the primary (the only?) reason I switched to something else, it would limit software choice going forward.

Palm IIIe. Great little device I had as a kid. Sim City, Strategic Commander, some other games. BASIC, Lisp, maybe some other interpreters also?

And AvantGo web browser, which primary mode of operation was syncing pages with a desktop computer to view offline.

Sure, but if we're talking about these languages being "socially acceptable" for writing websites, they arrived a bit later to the party than PHP.

Granted, it still happened about a decade and a half ago, so I hoped the sarcasm using the word "new" would come through.

Shared hosts are still there, and are cheaper and much simpler to use than your average cloud based deployment. Some even support these new hipster programming languages ruby and python.

If spinning up a new microservice would be as complicated and expensive, as yeeting fragile scientific equipment to a Lagrange point, you'd see better engineering in the cloud software world.

Apache has mod_wsgi, nginx not so much.

mod_wsgi is a much less flexible setup when it comes to mixing and matching different python versions

Last couple times I started with the word which rhymes with "tennis".

The difference is not having to touch NPM.

The title is pretty much the only part of the article I agree with.

While the industry was largely distracted by various NPM packages, the foundation we are building sites on got really nice. And I believe in some situations there's value in trying to use this foundation directly, not via a plethora of abstractions. Browsers are great, DOM API is great (well, certainly provides some really nice utils we previously had to look for in external libraries like jquery). CSS is great. I will write "display: flex;" multiple times just because it feels nice to type that, compared to the dance we had to do a couple of decades ago to achieve same layouts.

Static sites are great. They are fast to build, and they build fast. They are really easy to deploy as well. And they also work really well on end user devices. No single line of JS required, but if you want to have some liveliness on the page which can't be easily achieved by CSS animations, very few lines of JS are actually required nowadays. And 0 NPM packages.

Modern JS web frameworks do solve problems some people actually have. But they're best suited for big corporate style webdev. For personal projects I prefer something more… artisanal? Dunno, it's like building a piece of furniture yourself instead of buying one from IKEA. Probably less practical, but feels nice. And may actually fit better in this one weird corner you have.