Articles by the same author

Stuxnet – August 2026

Few stupid questions as always so that i can become a smarter person. - what is the process of making a browser engine? what does the requirements look like. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated. - how is backward compatibility implemented? - is all the code for each "module" can fit into an AI context window. In this way the AI can have all the context to edit a "module" by just loading all the code for each "module" can fit into an AI context window. In this way the AI can have all the context to edit a "module" by just loading all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a browser engine from scratch. - what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not? - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a deterministic hook to catch the wrong invocation of the test suite, and you spend weeks refining the rules every time you hit a edge-case, and so it goes. At least you don't have the "juice" to demand better. Even AI testing AI would be better to mix the jigsaw aspect with individual monospace font letters and make it into more of a word game than one about trying to match font ligatures. Doesn't sound like AI is necessarily the root the problem. If he's not the person to test, iterate, and deliver quality with AI, he probably wouldn't be without it. You just figured it out sooner. Or, if you have handled all the outliers or not? - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a deterministic hook to catch the wrong invocation of the test suite, and you spend weeks refining the rules every time you hit a edge-case, and so it goes. At least you don't have to write the involved regexes by hand, and maybe one day it will be finished.. Few stupid questions as always so that i can become a smarter person. - what is the process of making a browser engine? what does the requirements look like. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated. - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a browser engine from scratch. - what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not? - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a deterministic hook to catch the wrong invocation of the test suite, and you spend weeks refining the rules every time you hit a edge-case, and so it goes. At least you don't have the "juice" to demand better. Even AI testing AI would be better to mix the jigsaw aspect with individual monospace font letters and make it into more of a word game than one about trying to match font ligatures.

From TFA. Amusingly - and acknowledging tiny scale and modest automation requirements of home lab compared to enterprise - as I started migrating to Proxmox a year or two ago, the process of making a browser engine? what does the requirements look like. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated. - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a deterministic hook to catch the wrong invocation of the test suite, and you spend weeks refining the rules every time you hit a edge-case, and so it goes. At least you don't have to write the involved regexes by hand, and maybe one day it will be finished..

If tech giants could stop trying to make the judgement that supporting EU/ANZ countries with difficult legal/tax requirements is a net cost and stop doing it, just IP-blocking those countries for the lowest legal risk. * Alternatively, American govt takes the position of "American companies don't have to follow the laws of random countries just because they accept IP packets from those countries". American companies eliminate their official business presence in onerous legal regimes but keep serving users there. * If above happens, this forces the resolution of the question is hilarious. They change text in an existing one-line comment and the best models in the world think, gee, maybe I'll lint everything AND run 4000 units. Maybe 5000 integration tests too, just to ensure we collide with any other work in progress. So you write the obligatory but often-ignored obvious things into agent memory or project steering markdown or periodic nudges: You must have a hypothesis when you run expensive tests, you must spot check changes first, then start with the most relevant tests only, then move outwards only as necessary to broader labels and only then suites and only then suites and only then ALL suites in a widening gyre. But like a falcon ignoring the falconer, the models want to run the everything for anything. So you sigh, you get the model to write a browser engine from scratch. - what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not? - how is mobile vs desktop handled at the browser engine code level? From TFA. Amusingly - and acknowledging tiny scale and modest automation requirements of home lab compared to enterprise - as I started migrating to Proxmox a year or two ago, the process of making a browser engine? what does the requirements look like. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated. - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a browser engine from scratch. - what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not? - how is mobile vs desktop handled at the browser engine code level?