fpoling

In London in many apartment blocks one can only get wired internet via an old copper cable with speeds like 80mbit/s download in theory but in practice it can be below 30 with ping in 50ms range and much slower upload. And 5g does not help either as the signal can be very weak.

A progressive tax on the size of the company can do this.

Presence of many options directly affect equity prices.

If it will be true, then we should have many superb books by new authors at this point. But we do not.

This is similar to observations that effect of AI on quality of apps in stores is mostly non-existent.

Unfortunately the answer is no. Reading or just owning a book by a certain author can be a matter of fashion or prestige. That allows for really bad work still be published.

The same is in many public toilets in Norway. I suppose holding both a syringe and a source of light at the same time is not that convenient.

EV only this year became comparable in prices to gasoline cars thanks to massive efforts by Chinese companies to reduce battery prices and improve drivetrain.

With that further changes can be very quick as forcing EV no longer requires reallocating money from other things.

Ammonia does not require a plant to generate electricity. While fuel cells running on it require temperatures over 600 Celsius to get to 70% percent of efficiency and not exactly small, with cheap way to produce ammonia they would provide energy dense batteries that could run for months if necessary.

Helion most likely would not work. Even their own optimistic modeling gives very thin margins and even they completely ignore radiation damage to equipment.

Commonwealth and other tokamak designs are too optimistic as well. We do not know how instability in plasma will behave in production volumes.

Stellarator-based designs at least do not have big ifs, but they are way further and even they assume that radiation damage from neutrons will be manageable.

And all of this is ignoring costs. Outside of niche applications it is very hard to sea how fusion even if it works can compete with solar plus storage.

Sodium batteries are cheaper for storage and does not require any rate/expensive minerals, just scaling up production. Then in Scandinavia the main problem in winter is heating and using heated water as a battery is already a thing. Then producing amonia or even carbon fuel from atmosphere for energy-dense storage will be viable option in 10-20 years. And of cause Norway and Sweden can have massive hydro for energy storage.

If solar becomes 2 times cheaper, it will be economical to capture nitrogen from atmosphere and produce ammonia and use that for long-term energy storage and fuel. And with that one does not need massive solar overbuild.

This does not require any magic technology, just scaling up what is available today is enough and will definitely happen within the next 20 years, before small nuclear will have any effect.

Data centers with good load balancing between regions do not need exactly the same power 24/365 so the latest solar-wind-storage is already cheaper in theory. But it would take few years before production of sodium and other batteries will scale up and the mean time a turbine powered by natural gas wins.

And they build a lot of modern coal power station with over 45% efficiency and flexibility in power output.

It can be Russia to limit availability of AI heavy drones for Ukraine. Or it can be a small private organization using the strike as a mean to manipulate market.

Memory orders for the whole 2027 were already reserved. There is little indication that in 2028 situation will be any better unless something drastic happens like AI crash.

And then the opposite can happen like an unknown drone with 100 kg warhead striking memory production facility.

Unfortunately there is nothing that works as nicely as Windows Remote Desktop. Probably the best option is various commercial offerings as Apple Remote Desktop is rather buggy and unstable.

If one needs to dig history, then git log -p and similar are way more useful and reflect the real history rather than LLM inference about it. Comments reflecting the goal are more useful as neither history nor code itself covers it.

Index is just a part of the model. The nice property is that the index for LLM does not need to be updated often so LLM plus index can be static. This even works for the latest news as LLM can fetch major news sites to learn the latest stories and then fetch individual articles for the final answer.

The model just asked the crawler to get a recent copy of relevant pages and used that to give the answer. That is why AI companies experimenting with browsers or at least agentic extensions to browsers as that allows to fetch on behalf of the user directly from the device with a residential IP and ditch expensive to maintain crawling infrastructure.

With SQLite one automatically gets reliable persistent storage. Try to emulate that with a text file with history that eliminates duplicates. It is surprisingly hard to archive.

SQLite gives indexes that makes searching and locating previous entries much faster. This is relevant when the history is over 100K entries and one wants to avoid duplicates in history files.

GN tool that is used in Chromium to generate ninja files has much more restrictive language than CMake or make. And even its more complex features are mostly workarounds or escape hatches to deal with legacy setups.

The article over-downplays the need for sentinel values. Surely Rust has Option that also spreads into C++ these days as std::optional. But for plain C using -1 or negative values to denote sentinels or error code is rather nice idiom.

The argument will be more valid if array indexes will be 1-based like in Fortran/Matlab/Julia as then 0 becomes extremely nice sentinel values. But C is C and needs -1.

Yet Elm due to its simplicity does not need a lot of examples. Language itself is small and blessed way to architecture things consist of few patterns. Then things are composable. This is ideal for LLMs.

The price for that is verbosity. What in other languages are hidden behind async and complicated libraries in Elm has to be done explicitly resulting in boilerplate. But that is never a problem for LLMs.

Then Elm compiler has one of the best error messages. This helps agents a lot.

Then Time Machine debugger is another big help for agents as they have access to the full execution trace of the program. The trace is much smaller than would be necessary for other languages and typically fits into content window.

Java allowed to handle out-of-memory rather well if one wanted to even 25 years ago. Basically one allocated a buffer on a startup taking 5% of memory that the application was supposed to use and made all threads to catch the oom exception. When handling that the buffer would be released, GC would be forced and a special flag would be set asking app to cancel any memory-intensive tasks until enough memory would be released and the buffer can be allocated again. It worked extremely well.

Microsoft just followed VAX/VMS that does not overcommit. And there is a noise on Linux mail lists to implement process builder pattern which VAX had like 50 years ago…

You can also use cgroup to set allocation policy for a particular program.

And in Spain most immigrants are from Latin America with close enough culture and language to avoid most integration problems.

Interesting idea. On the other hand on the latest SSD with hardware encryption the raw disk speed under Linux can be over 5 GB/s so on my laptop with 64 GB of RAM the full restoration from disk takes like 45 seconds. With LUKS it is like 2 times slower. Which is not a problem at all. So I do not see much value in memory encryption in suspend.

On my laptop with Fedora I just configured Linux to hibernate to disk after 15 minutes of suspend. Powering memory off ensures that bugs like this Debian-specific would not matter.

Plus what Debian extension to Linux tooling does although nice in theory, but in practice if one really worries about cold-boot attacks, then all keys and important documents has to be wiped out from memory, not only LUKS keys.

So hibernating is really the only proper way to protect against cold boot.