Page caches are nice, but you would see meaningful reduction in load times for the OS and applications by getting data in order on spinning disks. Especially games that used most of your ram and loaded reasonably large level files.
fat seemed particularly prone to spreading files into very small chunks across the disk surface; it's not so big of a deal when fragmented files are made up of large contiguous chunks.
Steve Krug's other book, Rocket Surgery Made Easy, got me into usability tests with real users, and how to get it in place in a corporate environment. It's shocking to watch real users use software.
This is so important. One of the things that kills company culture before the company even takes off is getting the sense that the founders are just trying grift people into working for them for below-market money. The startup that actually work have the philosophy "find great people and pay them a lot" and if you are unable to do that, then you are simply not well-capitalized enough and should drop the project.
Yes? Read about their water rights lobbying and lobbying against plastic recycling regulations. Our descendents have to deal with Coca Cola’s externalities. You can’t see these second order effects immediately, which is understandable, but coca cola is massively extractive.
I am, too, and you can't seriously be arguing that LLMs fall into the same category.
Intellisense and language servers basically act as memory aids and adjuncts to compilers. They don't substitute for thinking the way LLMs do, and if you've been in the industry as long as you say, surely you can see the difference.
In ~2017 I ditched FreeNAS when my FreeNAS Mini died from the Atom C2000 hardware failure. iXSystems was great about getting me a replacement board, but I decided when I rebuilt the system to just use FreeBSD and get used to command-line only administration. That directly lead to me learning pf, jails, bhyve, etc. Yeah, I don't have any fancy web UI, but I've had a rock solid system for almost 10 years with Samba + NFS running without issue.
I agree the root cause here is the lack of a primary key to begin with. But as far as I know, DDL is always replicated as just a statement, regardless of session binlog_format. So I believe the only real fix here is the general approach suggested in the manual [1], i.e. create a new empty table that has the auto_increment PK added and then populate it from the old table.
The article also mentions that typestates can be cumbersome:
> Typestate improves code faultlessness and testability, but comes at the cost of more boilerplate code and can degrade readability.
I have noticed this in my own code. `Ticket` with an internal variable tracking the state makes using it simpler. I just have to store one object in my struct `struct MyData { ticket: Ticket }` and call its methods in the correct order.
Typestate `Ticket<T>` is not as simple. I have to wrap it in my own enum: `enum TicketState { Ticket1(Ticket<Func1Done>), Ticket2(Ticket<Func2Done>), }` to store in my struct: `struct MyData { ticket: TicketState }`. Then every time I call the methods, I must extract the correct variant value first. That degrades readability and creates extra run-time cost.
What RISC-V extensions is this built for? There is a target triple of riscv64-unknown-linux-gnu listed so i assume the baseline RV64GC that the Linux kernel is built against.
It makes sense to be conservative with a new architecture but new high performance RISC-V cores such as from SiFive[1] are going to meet RVA23. That standard has vector and bit manipulation extensions that could be used to improve performance with a python interpreter. I guess more testing needs to be done to see if raising the bar is useful.
I think there’s two separate things here that you seem to be conflating - absurdly rich and unethical. I’d argue Newell is mostly the former; though many or most billionaires align on both those metrics.
Much better at satisfying formal specifications (what they were trained for), but not yet good at long term maintenance.
For long term maintenance you need to throw features out / delete code, which requires a deep understanding of the balance between what the code can survive and what is really needed in reality while not growing the code base too much (which neither LLMs nor humans can handle)
Your body has an excellent mechanism for keeping you hydrated, which is thirst. If you drink water (not soda, coffee, tea, or anything else) when you’re thirsty, you’ll be fine.
Most people don’t drink 68-101 oz of liquid a day, but you also get a surprising amount of water from food. Cooked chicken breast is 65% water, for example. Fruit and many vegetables are even more.
Eating water is also better for overall hydration. Drinking more than you need just results in peeing it out and possibly unbalancing electrolytes.
No, they are not. That wont stop an enlightened anarchist or antifascist from insisting that they are, and lying about this to as a pretext for their violence.
They do not give all of the code. If you have an object, and don't have everything needed to reproduce the object, then you have not been given the source to the object.
And with BSD licenced code this is their right.
And it's my and anyone else's right to observe all of this and criticize it.
> much worse at producing artifacts that are comprehensible to humans
This has always been the case. Just try making sense of the output of any assembler/compiler/transpiler. Why do we think differently about generated source code?
fat seemed particularly prone to spreading files into very small chunks across the disk surface; it's not so big of a deal when fragmented files are made up of large contiguous chunks.