Fixed a bug on how the browser wasn't closing TCP connections/Motion JPEG video streams properly in a responsive behavior. Took me about 3+ hours reading through various specs and that resulted to around 20 LOC changed. I then wrote a blog post about it[0], which took me about 10 days.
I think it should be "The art of buying single-board computers and never running them once". I think the "once" is needed in the case of computers. They are as machines not directly comparable to books...
A book, like any media, fulfilled its initial purpose after it has been "consumed" - anything else (looks nice, feels nice, smells nice) are physical, subjective qualities attached to it. You might even buy it solely for these physical qualities, but that's besides the point.
A machine has its purpose in its usage, and that usage requires known resources that should not be carelessly wasted. I personally buy them to enable a utility for myself and have fun discovering it. It fulfilled its initial purpose even if it was powered on just once.
Even those single-board computers that were put to "good use", as building blocks for new devices (eg. [0]), are still not in use the whole time.
> If you had a list of all the genomes of all the people in the world, and all their phenotypes (height, eye color, hair type, etc), you could take all their genomes as input variables and treat all their phenotypes as output variables, and make embeddings or other models that mapped from genomes to phenotypes. The result would be a predictive model that could take a human genome, and spit out a prediction of what that person looks like and other details around them (up to the limits of heritability).
Would such a predictive model really be possible? As far as I'm aware there is contradicting research whether a specific phenotype distinctly originates from a SNP/genotype.
I'm honestly a bit confused by this statement, as "React env variables" can mean various things, depending on your setup.
Backend and frontend can be separate runtimes... The backend could be an API-only-server and an OS process with all permissions that come with it (reading env vars during execution as it pleases). The frontend, eg. a React SPA, could just be a bunch of built HTML/CSS/JS-files (type-checked, bundled, minified, etc.), served through a static file server (separate backend, nginx?) and interpreted through a browser engine on the client.
Are you asking for nginx to parse the served HTML/CSS/JS-files and replace unknown placeholders with env var values? If so you are prob asking for a SSR framework[0], meaning a backend that treats a React project similar to template files, and is able to inject env vars?
Correction: you cannot get fired ("Entlassung") without any reason in Austria, you need rather strong reasons to fire somebody[0], but your employment contract can be terminated with a notice period anytime* ("Kündigung")[1]. The notice period is 6 weeks at minimum by law (6-12 weeks is common in startups by employment contract) and includes "Postensuchtage"[2], which allow you to use 20% of your time during the notice period however you want.
Had those in heavy use during my work on a surface grinder[0], I can remember it had an ancient digital interface with 0.0001mm precision. We used the blocks to calibrate our measuring table[1] constantly.
Later in life I got to see the machines to measure the quality of photomasks[2] in the production line of modern CPUs, and I was just blown away when I heard about those tolerances.
The level of noise is the predominant parameter in my selection for a living place. I always consult the noise map[0] before moving anywhere in Vienna/AT. I hope other governments offer the same information.
seems like you already made up your mind, so why bother?
TypeScript is helpful (or at least meant to be) for teams as it aims to block the cleverness of its individual contributors. Especially people only familiar with dynamic type systems are rather fighting a static type checker at first and "it's not helping them". A "strong" type checker should enforce everyone to write stuff in a simpler form and that gets in the way of productivity for some people.
If you can maintain your mindset and write your code in a simple form that could easily satisfy a type checker (coming from rust), then why bother with additional tooling if it won't provide more value to you? Or to phrase it differently: if you can maintain a strong mindset with confidence, bringing in additional tooling for that project later on, when it will be become plausible, won't be that hard. But if you doubt your mindset, it might be a helpful choice to let a type checker look over your shoulder from the beginning.
To add to this, for me personally the difficult part in automated test isn't the definition of expected output, but the retrieval of actual output in an automated way. Test frameworks can and will only focus on a limited set of interaction (Playwright for DOM, detox for mobile etc.).
I think Brendan Gregg's books[0][1] are quite inspiring for an understanding of a system with its inner workings, and provide information about various tools one can use to dissect a system and get some actual output in an automated way.
just patch inputs and outputs to audacity (or your recording software of choice). for pipewire theres helvum[0] or qpwgraph[1]. for JACK there's Catia[2].
was just a poor choice of words here. i understood GP as "the structure of a language influences its speakers' worldview or cognition, and thus people's perceptions are relative to their spoken language"[0]
You're question seems more on the side of "Why use a micro framework when you can use a mature full-fledged one?". I feel a lot if new ideas in the web development space are first available as "micro" packages, so that's just what you use when you want to stay on the edge. I feel there is still so much momentum in the JS/TS community. Would you genuinely pick PHP for anything else besides Laravel?
I would also question you're mentioned frequency to update packages tbh. Just pin a stable version with a lock file, track the required node engine and use an OCI image to provide just enough reproducibility. I never had to do anything more than cd-ing into a directory and run npm ci after coming back to a project for a few years now.
