Readit NewsPeople with titles like
Giga Chad, MBA, CSS, CKAD, XXX, PQRS
are gonna love this.
In no time, HRs will start slapping “10 years of certified Claude Code experience required” on job listings.
I still made it work. I got pretty good at reading the waveform preview, and was able to use that to figure out where to do cuts. I would apply effects and walk through frame by frame with the arrow keys to see how it looked. It usually took all night (and sometimes a bit of the next day) to render videos into 1080i, but it would render and the resulting videos would be fine.
Eventually I got a job and saved up and bought a decent CPU and GPU and editing got 10x easier, but I still kind of look back on the time of me having to make my shitty computer work with a certain degree of fondness. When you have a decent job with decent money you can buy the equipment you need to do most tasks, but there's sort of a purity in doing a task that you really don't have the equipment you need.
https://www.justice.gov/archives/opa/media/1344546/dl?inline
I do, however, notice that I have never used a program that was built with either a web stack or a gc language stack, that wasn't getting slower over time, wouldn't cause strange issues, and wouldn't have crippled UI to match whatever the stack's limitations have been at the time. IMO the right direction is developing (or adopting) modern native languages. If the "price" for that is some web standard being stuck, I personally am totally okay with that.
I am sick of this idea that the web browser is almost an OS. It was supposed to serve web pages.
I could not disagree more
> The more capabilities you add to a interchange format, the harder that format is to parse.
There is a reason why JSON is so popular, it supports so little, that it is legitimately easy to import. Whereas XML supports attributes, namespaces, CDATA, DTDs, QNames, xml:base, xml:lang, XInclude, etc etc. They gave it everything, including the kitchen sink.
There was a thread here the other day about using Sqlite as an interchange format to REDUCE complexity. Look, I love Sqlite, as an application specific data-store. But much like XML it has a ton of capabilities, which is good for a data-store, but awful for an interchange format with multiple producers/consumers with their own ideas.
CSV may be under-specified, but it remains popular largely due to its simplicity to produce/consume. Unfortunately, we're seeing people slowly ruin JSON by adding e.g. commands to the format, with others than using those "comments" to hold data (e.g. type information), which must be parsed. Which is a bad version of an XML Attribute.