Someone
IMO, that text is confusing.
“Not nothing” is saying it has some OO features.
“I don't think it's incorrect to say has any more OOP than general purpose languages like Lua or JavaScript in that sense” = I think this language has more OOP than languages like Lua or JavaScript”
So, that more or less says “A, but A”. If so, what’s the “but” about?
A day has 86,400 seconds, so that’s about 11 orders of magnitude.
That makes this a fairly meaningless comparison.
It had most if not all of that.
It had networking from the start with AppleTalk, later Ethernet and internet with MacTCP.
MacOS 9 had a preemptively scheduled kernel.
The problem is having that and supporting the software ecosystem, which depended on cooperative scheduling without having memory protection.
MacOS 9 ‘solved’ that by running the classic OS in a single process. It had APIs for creating preemptively scheduled threads, but those threads were limited in what they could do.
(Examples at https://www.swiftbysundell.com/basics/type-inference/)
I’m thinking that because the text you referenced also says:
“for users who are not accustomed to text editors with separate insertion and editing modes, and includes support for editing UTF-8 text.”
I’m not sure the group “used to editors without visible menus, but doesn’t know vi” is very large, though.
It allow you to pretend a directory is a drive, and thus gives you multiple current directories on a drive.
int foo(int bar[10]) {
…
}
That tooling should be shut off from the internet [1], and if it uses a LLM that should be at least a few years old.
[1] technically impossible if it also has the ability to veto responses, but the surface can be very small.
Shady developers would try very hard to get past such checks, for example by changing that message based on the date, IP address range, nearby WiFi networks, receipt of a payload, etc.
They could introduce an optional string-valued entitlement and check its text. That would be a lot easier but still require them to translate messages.
- The utility-scale market continued underpin growth, with 18 GWh installed, largely supported by seven gigawatt scale projects. Arizona installed over 6.2 GWh of utility scale projects, the largest quarterly deployment for any state in history.
- In the BTM space, residential storage added 657 MWh and commercial and industrial (C&I) added 1.8 GWh, largely on the back of demand from data centers.
⇒ it includes data centers
So, this adds over two minutes of average usage.
https://seia.org/research-resources/energy-storage-market-ou... says total storage now is about 200 GWh, or about 25 minutes of average demand.
Closer to their solar time, for quite a few. As an extreme example, most of Spain lies West of the prime meridian (some parts of it even west of Great Britain, the island), but its time zone is an hour ahead of that of London.
LLMs can do smarter searches, and will likely find proofs for most of them, but are not guaranteed to find a proof.
Your mind cannot live with the idea that you spent many, many hours learning an ugly API, so it makes you think it is better than it is.
“Could be”, but I think the correct way to describe it is “the general public doesn’t know”. It could be any of
- they tried very hard without finding weak spots
- they tried for a while, and gave up because the LLMs didn’t even produce leads
- they tried, found something and kept it for themselves
I think the first is not unlikely. Before LLMs, the likes of the NSA must have looked really hard into these problems, and IMO it’s not likely they found something substantial (if they did, their counterpoints in other large countries likely would find it, too, and some of them would have used that knowledge)
“For most people, tulips, windmills, and bike lanes spring to mind when they think of the Netherlands. But most people would be surprised to learn that the Netherlands ranks first in the world as an exporter of cocoa products, recently overtaking neighboring Germany.
The Netherlands recorded cocoa exports of 12.4 billion euros in 2025”
I would guess that’s a holdout from colonial times. Indonesia used to be a Dutch colony up till world war two. Might even date back to when there was a Dutch colony in Brazil (https://en.wikipedia.org/wiki/Dutch_Brazil), but that page doesn’t mention cocoa, and I wouldn’t even know whether there was cocoa in Brazil at the time.
“Trekschuit (Dutch pronunciation: [ˈtrɛksxœyt] ⓘ; lit. 'tug-boat', i.e. 'tugged boat') is an old style of sail- and horse-drawn boat specific to the Netherlands, where it was used for centuries as a means of passenger traffic between cities along trekvaarten, or tow-canals.
[…]
By 1700, an extensive network of trekschuit- and ferry services linked all of the important cities in the coastal provinces of the Netherlands. Travel by trekschuit was reliable, comfortable, and cheap. The speed was about 7 km/h, which was faster than walking, and more comfortable than by coach. Many foreigners praised the advantages of the system, leading to the introduction of canals, such as the Erie Canal, in the United States. The boats were pulled along by horse on a towpath (in Dutch called jaagpad, named after the jager (chaser) which accompanied the horse)”
I don’t think that ever led to a real product.
That moves the needle back towards “may not be deliberate”.
This was the vote to promote the current proposal to draft standard.
Interpreters and compilers can have bugs. Bugs can cause memory safety issues.
Historically, not true for the “trekschuit” in 1632. For that, the shore didn’t exist before the route was envisioned. https://en.wikipedia.org/wiki/Trekschuit:
“The first trekschuit 'sailed' in 1632 between Amsterdam and Haarlem and could carry 30 passengers. The trekvaart or canal was dug in a straight line to facilitate an easy pulling process and to guarantee the shortest route”
I think the point being made is that users who do not care about Markdown will receive Markdown files, and it should be trivial for them to open and view them.
Yes, the article also states “If I want to see the original Markdown syntax, I should be able to switch to that view just as easily”, which isn’t necessary for that use case, but I still think that’s a point the author makes.