I like the wonky, hand-drawn looking style. I think it fits well beause usually if I use a diagram it's not 100% precise and accurate, but more a high-level illustration. The wonky style conveys the approximate precision of the presented concept.
But LLMs themselves are literally not going away, I think that's the point. Once a model is trained and let out into the open for free download, it's there, and can be used by anyone - and it's only going to get cheaper and easier.
And the reason why is those things must be profitable, and once you accept everything must be profitable, there is no ceiling to exploitation. Whereas with big things like Apollo, we didn't do it because it would make money. We did it because we decided it was the right thing to do.
Stop being a capitalist hellhole, and maybe try being a country that happens to operate under bounded capitalism, and just maybe, maybe, you can see some of that progress.
Does that make it okay? Some websites weren't free enough and their owners not passionate enough, so wholesale destruction of that ecosystem is acceptable?
Traditionally in America, the value of newspapers is predominantly their up to date news, not their archive, which traditionally could be accessed and read for free by anybody that cares to visit the local library. You pay for recent newspapers, the archive is free.
Anyway, intellectual property is a dumb joke. It will never benefit the little man, you don't have the resources to lawyer up like the big corps do, so screw the whole premise. If you're not taking what you want for free, you're a servile worm crawling around on your belly in a futile attempt to earn favor from inhuman corporations that will never notice you, let alone reward you. Stand up, man.
The left are accused of this far more often than the right are, even though the right own think tanks like Heritage, mega churches,mega news channels like Fox, large parts of academia (esp. economics and MBA culture), most of the lobbying machinery, and most of the bot farms.
While I think the suggestion - popular with left wing academics - that society can be engineered towards perfect fairness from a blank slate is obvious nonsense, it's also true there have been decades of active social engineering towards other ends which were deliberate, organised, and generously funded, and have become so pervasive they're experienced as constant background noise.
It will be interesting to see how you handle acces to youtube player settings and cc. This is where other player wrappers fall down.
Plyr did a good job of removing the branding via some clever css, but its annoying you cannot access settings and cc. One idea for a cc button is to always have cc on and then toggle the height styling to show/hide it
Eurisko demonstrated superhuman abilities to play strategy games in early 1980-th, and even used strategies from VLSI place-and-route task in planning fleet placement in games. This is knowledge transfer between tasks.
This won't do anything. They'll just take crypto from now on, and the boxes will start running over a VPN of some kind, I'm sure.
Personally I would never do piracy without both of these protections. It's not perfect but it doesn't matter. You just have to be harder to catch than the lowest hanging fruit.
Like the guy running from a bear said to the other guy: I don't have to outrun the bear, just to be faster than you :)
For a while now cppreference.com has been in "temporary read-only mode" in which it isn't updated. Eventually I expect a "temporary" replacement will dominate and eventually it won't be "temporary" after all. Remember when some of Britain's North American colonies announced they were declaring independence? Yeah me either, but at the time I expect some people figured hey, we send a bunch of troops, burn down some stuff, by Xmas we'll have our colonies back.
The React paradigm is just error prone. It's not necessarily about how much you spend. Well paid engineers can still make mistakes that cause unnecesssary re-renders.
If you look at older desktop GUI frameworks designed in a performance-oriented era, none of them use the React paradigm, they use property binding. A good example of getting this right is JavaFX which lets you build up functional pipelines that map data to UI but in a way that ensures only what's genuinely changed gets recomputed. Dependencies between properties are tracked explicitly. It's very hard to put the UI into a loop.
In fact, pre smartphones more or less, bringing cameras into even an office workplace was generally pretty controlled. Still is under some circumstances.
In general I think there has been (a) too little utilization of the hooks provided by agents for deterministic checks and follow-ups to agentic coding, and (b) too little investment in creating re-usable org-wide monitoring controls and reporting on convention enforcement.
> app review is taking significantly longer, with some people being stuck in review for 3+ days, and some reporting even a week of waiting for review
A whole week? Maybe, developers should stop pushing those incredibly frequent updates with “bug fixes and performance improvements”, and start testing their code in house again?
I think Apple should provide an online service that does basic fully automated testing such as “does the app start” and “does it only use approved APIs”, and, for the real final review, prioritize updates on how long ago the previous review was done. Send an update once a month, and you’ll be reviewed almost immediately. Send one a day after the previous one, and you’ll have to wait a bit.
At this point my dev setup is basically just Neovim, tmux, and a terminal. I ended up removing the usual IDEs because I just was not opening them anymore.
What sold me was not even the editor itself at first, it was the workflow. I can leave sessions running, bounce between projects instantly, and my system still feels light. That matters a lot once you get used to having multiple things going at the same time.
Claude Code also helps a lot with the rough edges. When I run into some niche config issue or weird tooling problem, it is usually fixable in minutes instead of turning into a rabbit hole.
Erm. Why?