skysight-inc/HackerNews huggingface dataset:
From a public policy standpoint, you don't want local government authorities taking a quick buck now instead of (on average) more money a few years later.

But to an elected politician that might not even be in office in a few years, money now is worth more at any cost than money later.

A gov agency is best suited to ride these things out because their cost of capital is among the lowest. Generally dumb for a county to sell an asset to a hedge fund: the HF has to pay more in interest than a county does just to pay you money now. There's nothing to do here except wait, nothing to whip in shape and make more profitable.

(Also cities shouldn't own stadiums, that's a gamble on the success of your local sports team and solvency of whomever you sell the naming rights to)
The developer of FlappyBird shared his thoughts on this problem:
https://www.rollingstone.com/culture/rs-gaming/the-flight-of...

> By early February, the weight of everything – the scrutiny, the relentless criticism and accusations – felt crushing. He couldn’t sleep, couldn’t focus, didn’t want to go outdoors. His parents, he says, “worried about my well-being.” His tweets became darker and more cryptic. “I can call ‘Flappy Bird’ is a success of mine,” read one. “But it also ruins my simple life. So now I hate it.” He realized there was one thing to do: Pull the game. After tweeting that he was taking it down, 10 million people downloaded it in 22 hours. Then he hit a button, and Flappy Bird disappeared. When I ask him why he did it, he answers with the same conviction that led him to create the game. “I’m master of my own fate,” he says. “Independent thinker.”
Nicolas Jenson
Try looking at the problem from the other direction:

One of your favorite dogs just died. You need to punish someone for this. Who will it be?

Your options are:

(1) The toddler who fed the dog something that it choked on;

(2) The woman of your household who allowed the toddler to do that; or

(3) Any random person who has absolutely no connection to the events.

All three options look plausible to me, but in particular there's nothing ridiculous about picking (2).
We have a demo of multi-server usage here https://demo.ideastore.dev/multi-server and here https://octothorpedwordpress.com/how-it-works/ and are actively working with people interested in hosting their own ring.
We agree! That's why we don't require this anymore. That was an early approach that we need to remove from the docs. We're currently building out a web-of-trust approach too, but authentication / verification in general is something we want to test in the real world and learn from before a fully public release.
The Onagawa nuclear plant, albeit more exposed, resisted thanks to a single man (Yanosuke Hirai), deciding in conscience, and the Big Complicated System of Central Authority "controlling everything" failed miserably at Fukushima.

Full story: https://en.wikipedia.org/wiki/Onagawa_Nuclear_Power_Plant#20...

What works is local and managed by a few people, any Big Thing is a colossus https://en.wikipedia.org/wiki/Onagawa_Nuclear_Power_Plant#20... feet of clay collapse is all the more painful. This state of affairs doesn't seem to benefit to nuclear (vs. 'renewable sources').
Is a Partition meaningfully distinguishable from especially high Latency?
Of course the opposite is often stated as "Perfect is the enemy of Good"
So, am I to understand that prime beach real estate is to be taxed the same as a plot in a desert or swamp? There is clearly a lot of trouble with taxing land, because an inherent part of its value is what you can do with it. People pay premium for land that is useful and desireable. The structures placed on land and the values thereof are proportional to this desirability and economic utility.

Furthermore, it might be necessary to use land for farming or warehouses when it is more profitably used for residential structures. A free market might eventually sort out higher food prices that can cover the taxes, but I think we can all agree that it's better to not arbitrarily increase taxes on a necessity like food.
Curious how this compares with Meteor.
> QEMU running Windows for x86 on an M1 isn't very fast either.

It seems the main obstacle is in paging where x86 4KB clashes with Apple 16KB (ARM/64 supports multiple sizes), so, 2-level paging canʼt aid and an emulator has to shadow-paging which is, definitely, much slower.

> Apple does it with Rosetta and Microsoft with whatever their thing is called, you don't even notice that an app is running under emulation.

But they still use a vendor-specific TSO support in hardware.
this was the link: https://www.reddit.com/r/WikiLeaks/comments/1fy10k1/tracking...
I edited my original comment. The "It's a bit jank" part is still true though. When you enable running your app on macOS without compiling specifically for macOS with Mac Catalyst, it still uses Mac Catalyst, but transparently. So, you still get all the issues of Mac Catalyst, but without the compiler warnings. Your application may crash or behave strangely.
Thanks for the idea. Basically that's why I'm considering DApp - new stuff. Also new language - Solidity. On top of that new paradigm I'd say. Refreshing. Yet something practical - I mean I could Imagine building a mvp. On the other hand building a gRPC which you suggested is more like system programming with target audience other developers and their software - low level stuff. Guess I'm more on the other side. Did you switch at some point after doing same stuff for years?
Do you have a proper link to the webtransport-p2p idea? I've done a few searches but I think there's some mix of current implementation and deprecated implementation somehow.

What is it that needs reviving?
Repair and reuse would have kept the 30% appstore cut rolling in.

But that's about to change in Europe and USA due to recent rulings.
> The anti-nuclear movement succeeded in Germany

No, the Fukushima accident was decisive. Just before, at the end of 2010, the operating life of nuclear reactors has been extended by law. The Fukushima happened and public opinion reversed, wanting an as-quick-as-possible nuclear phaseout. Not a single political party could save those reactors:
https://x.com/HannoKlausmeier/status/1784158942823690561
I liked the first Belgariad book I got, but after a few more, I felt like reread the same book over and over. Same for Mallorean.

The Black Company is great, especially the first book.
This part of the documentation needs serious cleaning up -- which is one of the reasons we haven't done a public launch yet. This is referring to: https://octothorp.es/docs#anchor-tag which is a bit of an edge case that we may not even launch with. This example anticipates a circumstance where someone would want to link to their own url, such as their own tag page, and at the same time use that term as an octothorpe. This might be something no one wants! TBH I'm not sure if it's even implemented anywhere right now. It certainly shouldn't be more prominent in the docs than the basic anchor-based implementation that got discussed over at Lobste.rs.

> Now it’d be fine to use href if only they had the full URL:

Totally agree. This hits on what we're actually going to ship for how to create in-line octothorpes with plain anchor tags, and the docs should reflect the primacy of this approach.

> Suppose you want to be on _two_ rings, and they use the same keyword, but differently—what do you do? “You can only be on one ring” is a rather unnecessary and limiting restriction.

Also agree, which is why that is not a restriction. We have two live demos of thorping to multiple rings from the same URL.

Term collision is very much something we've been thinking about. For now it has to be handled manually. But because we're building the whole system off of an RDF base, we have a lot of low-level tools to define and process different vocabularies in some powerful ways. The same term having different meanings on different servers is the most immediate application of this, and it's high on our roadmap.
Some more info:

https://en.wikipedia.org/wiki/2012_National_Reconnaissance_O...

They might launch one of them in 2 years:

https://en.wikipedia.org/wiki/Nancy_Grace_Roman_Space_Telesc...
As someone whose name is Zigfrid, I find it amusing to see first Zig, now Ziggy, in the software world :)
Indeed: if cheap (for the consumer, not for the taxpayer...) nuclear electricity was sufficient France industry would thrive. Reality: it (sadly) is dying.
New Traffic Coordination System for Space (TraCSS) Launches Initial Capabilities
Alistair Cockburn wrote about it long ago..

https://web.archive.org/web/20170620234716/http://alistair.c...

And yes, IMO software is very twisted way of communicating (knowledge and/or understanding and/or views) through time&space.. same as poetry :)
> starting with macOS then implementing iPadOS on-top

This would lose the security properties of iOS, which is a big part of the value proposition for iPhones and iPads.

> They can't just make macOS applications runnable on iOS.

Other operating systems can run in _parallel_ with iOS. Hardware support for nested virtualization has shipped on Apple Silicon since M2. Google implemented Android Virtualization Framework. There's no shortage of candidate VM operating systems. Microsoft implemented WSL (Windows Subsystem for Linux) VM. Apple could ship ASF (Apple Subsystem for FreeBSD) VMs.
I think you just fell into the trap.
Big fan of typing improvements in Python. Any chance you can elaborate on the "if let" pattern in Rust and how it would look in Python now? Not sure I follow how it translates.
octo: is an RDFa prefix, and, as comments mention below, is a valid string for a rel value.
> A three legged table will always sit stably on an uneven surface.

But the table surface might not be level, if my thinking is correct.
The fact that they could go from zero to proof of concept in a year and then into production just 2-3 years later is impressive. Given these results I feel the industry will slowly move to Rust once a certified toolchain for safety critical systems exists.

At the same time, let's not forget that this is a highly competent team with tons of experience. It's not guaranteed that other developers can have the same success.
Likely works fine in UEFI boards, using sbi for uart and timers, as long as the rest of the hardware is relatively standard.
Engineering Geology of the BART System (2000)
A nice complement to this post is Mike Culbert’s article about how Apple chose to use 32-bit ARM6 instead of a 16-bit processor for reasons entirely unrelated to maximum memory size. http://waltersmith.us/newton/COMPCON-HW.pdf
I read an illustrious (IMO) Indian newspaper. But their online articles have "continued on page x", infographics are low res images and they insist on yearly subscriptions and dark patterns like a shared web host. They have self imposed the limitations of paper.
Exercising your judgement about how other people exercise their judgement is good actually.
Check out ladybird browser. I look forward to checking out the monthly updates from Andreas.
> The single use drones that operate like kamikaze vehicles may throw a winkle into the mix, but a helo flying at 150knots is going to be very challenging to hit for one of those.

All you're seeing is makeshift COTS drones picking targets of opportunity. If you know that MANPADS can easily take down a helicopter then you are already aware that there is decades-old technology already quite able to take down helicopters, and the only difference between the drones you're seeing today and those that can be easily produced today is the product design requirements.
Or perhaps it’s a meta
comic about dual use :)

A lot of the claimed s&r applications are
really a thin cover for military gear.

I remember trying to mentor a hardware startup on an event, and we just couldn’t find the common language with the girl that was
pitching it. I just couldn’t see how the cases would justify the market.

Only later on I figured out that the cases were absurd, and all of them really a cover for military applications.

Finding survivors in a forest = finding partisans, is the most common one.
Interesting. It reminds me of Leif's reflections on his journey, but with an even darker tone.: https://www.omegle.com
It's true that energy intensive industry has been hit hard in Germany. But is also true that the sector has been heavily subsidized for decades. As the carbon mining sector. That was effectively paying the energy cost of those industries with taxes.

In Spain, where we didn's shut down nuclear energy nor have oil or coal, energy intensive industry is also threatening or shutting down (https://www.miningweekly.com/article/alcoa-threatens-to-shut...). The threats are barely hidden "subsidize our costs or else...".
No value judgment, but he's a good demonstration of why the US does the thing he's accusing the US of not doing.

The US goes out of its way to minimize collateral damage because it gets accused of causing all collateral damage in the first place.
Apple doesn't even have any data plans, do they? I mean Google sometimes plays at being an ISP with projects like Loon or Google Fibre, but Apple has never done that?
Right now I run them as two separate services. Phoenix does all the user signup and management, landing page, docs and vends API keys while I use Rust for the API product itself, which does some cpu bound work where Elixir would have been weaker. They both share a Postgres database where the Rust API is restricted to the api keys table.

There is also Rustler which helps facilitate calling Rust binaries from Elixir directly but I opted to deploy them separately.
Winamp was recently open sourced.
Apple isn't usually the first mover, though. It's not like the Mac was the first desktop computer, or the iPhone was the first smartphone, or the Apple Watch was the first smartwatch. Apple usually ends up with their market position whether or not they're the first mover.
> Lisp also makes use of vectors, where necessary. These languages with managed memory like Java have the same object/reference model as Lisp and the same calling mechanisms. linked lists are only a special case (-> java.util.LinkedList).

You seem insistent on missing my point.

"Where necessary?" is almost always, because vectors almost always outperform linked lists based on cons cells. If your program uses cons cells at all, chances are you made the wrong choice. Lisp doesn't make use of vectors in many cases "where necessary" because "where necessary" is a whole lot more than Lisp's structure, libraries, and community encourage you to do.

Simply pointing out that java.util contains a Linked List implementation means nothing. I wrote Java full time professionally for ~5 years and never saw that used once. If Python or C# ship with linked list implementations I'm not aware of them because they're also never used.

To be frank, if your program uses linked lists at all, it's probably a mistake from a performance perspective. There simply aren't many cases where a linked list is a better choice than a vector. And this is a mistake that Lisp programs make all the time because cons cells are so baked into the language.

> > in most languages it does not entail pointer chasing

> It does, see above. Just not tail pointers in the list.

It is both dishonest and rude to not even quote a full sentence when you're trying to refute something.

Tail pointers on the list being avoided is exactly my point, a fact which you obfuscated by removing context. That is a huge amount of added cache thrashing, even with cache-aware allocation. This is not something you can just pretend is a minor issue.

Are you even capable of admitting that Lisp has serious faults, or do you really think it's completely, 100% perfect? This isn't a rhetorical question: I legitimately would like to hear what serious faults you think Lisp has, because if you can't present any problems with Lisp at all, then you simply aren't capable of participating usefully in conversations about Lisp. Lisp is a human invention which includes human mistakes, and if you can't admit that, anything you say about it is going to suffer from crippling bias and can't be trusted.

And to be clear, I'm not interested in further whataboutism. If your idea of a problem with Lisp is something where you can end with "but every other language has this problem too", stop--that's just further proving your inability to criticize Lisp. I'm happy to describe serious problems unique to any of the languages I've mentioned in this thread, but that's not the current topic of discussion.

Pointer chasing in linked lists is a cause of performance problems in Lisp and it isn't a cause of performance problems in other languages. No, not for retrieving each individual item, I'm talking about moving from one item to the next. Every single thing you've said in this thread has been trying to move the goalposts to make it seem like this isn't a problem or it isn't unique to Lisp. It is a problem. It is unique to Lisp(s).
I don't think you get how powerful Rust's pattern matching is, or how to think of it in terms of a router.

From my example above, check out https://github.com/dakom/dominator-workers-fluent-auth/blob/... and follow it through to https://github.com/dakom/dominator-workers-fluent-auth/blob/...

Do you see that you have static and dynamic parts matching, multiple variable capture, etc.?

I'm not talking from a theoretical perspective. I'm showing you an actual example of a fully baked auth system that does everything on the wishlist (and more) and has no need at all for a router because Rust is itself powerful enough to do all that out of the box
IEEE Roadmap Outlines Development of Mass Digital Storage Technology
I was in Iraq in 2003, so like you said very different. We did take small arms fire all the time, pretty ineffective though. We had one Cobra come back looking like Swiss cheese but it did manage to fly back to the fob.
Well, being dismissed "with prejudice" exists.

https://www.law.cornell.edu/wex/with_prejudice
Yes, though touchscreens weren't exactly an Apple invention either.

I seem to dimly remember that they had some early lead on multitouch. But that one specific nifty technology is a far cry from a general 'first mover advantage' in phones with apps.
I fail to see how the decision was anything less than decisive prudence.

Your cited article makes it abundantly clear that the provenance of said $17 million claim was a default clause entitling Miami-Dade County to three years worth of naming-rights fees.

They sold that speculative claim for $5 million cash---effectively recovering that year's otherwise uncollectible receivables---then immediately turned around and locked in a 17-year, $117.4 million agreement with Kaseya[1]; back-of-the-envelope says that's an implied ~$5.4 million (2023 dollars) per year with 3% annual inflation adjustment baked in.

Call me naive, but I imagine that if you're in the business of running a multi-purpose arena with real opex, you've gotta be the dumbest risk manager in South Florida to allocate expensive legal resources in chase of speculative claims when a mutual opportunity to repair a gapping hole in your balance sheet presents itself and you have a willing long-term replacement suitor lined up.

[1] https://www.miamidade.gov/global/news-item.page?Mduid_news=n...
> The failure was humans

Isn't it always true, for such matters?

As we cannot avoid committing errors it seems better to prefer a way without any risk of major accident (very dangerous radioactive things, difficult to cleanup, travelling long-distance thanks to wind, rain...). No wonder renewable sources quickly gain traction.
> Not serde, but newer version of rust, no?

No, that's a separate issue in 1.80. See https://internals.rust-lang.org/t/type-inference-breakage-in...

Issue was: new type inference caused problems for old version of the time crate. Newer versions worked with 1.80, but many crates weren't updated to the latest.

> Also, the blobiness was never going to be a part of the public facing API - is it really the hypothetical serde’s fault NixOS breaks?

According to Semver - no. According to people affected - yes.

I often state this, but:

Backwards compatibility ⇒ Semver (read: Backwards compatibility implies SemVer, but not the other way around).

Who's right? Is it fine to speed up compilation but disrupt people using serde on Arch? It depends. According to strict Backwards compatibility guarantee - no. However according to them, you need to backport bugs and exploits.
I wonder if this isn't a GDPR violation of a pretty large magnitude? Especially because the way to get removed is this:

> If you want a record removed from the database, please include the BSSID (MAC Address) of the network in question!

There have already been a few wifi tracking cases within the EU where the perpetrators lost. A lot of this was used to track people in things like shopping malls though, so it's not exactly the same, but what came out of them was basically that people have to opt-in rather than opt-out if you want to do any sort of tracking.
In 2004 my boss - I was a one man team technical business development at the Austria Press Agency - came to me and told me "our press release clients want to get better found in that Google".

At that time I saw it as a nice, fun project.

too my knowledge I was one of the first in my market on corporate state who took on this topic. which later came to be called search engine optimization.

I was definitely one of the first who gave corporate lectures, workshop, whitepapers, books about it.

20 years later we screwed up the internet. well at least the part of the internet that shows up in Google.
That's mostly an argument for the law requiring children to be buckled in at most, perhaps.
Done :-) Thank you.
Also updated it to work with the bookmarklet title.
Thanks!
Both 80% and 30% are imaginary numbers, nobody measured it, so all the math is pointless.
I've read that it takes 10 to 15 FPV drones to finish off a "turtle tank".
Presumably it would also run on a Pentium M :).
OTOH current day Russia doesn't have the yoke of communism around their neck. Is the level of corruption worse than the economic inefficiency of communism? I don't know, possibly?

As for nukes, nuclear saber rattling seems to be one of the few remaining reasons the rest of the world gives a f*ck about whatever Putin and his cronies are saying. Without nukes, the West would have massively stepped up support for Ukraine, and the Russian army would be nothing but a breadcrumb of smoldering wrecks all the way to Siberia. So I'd think that Putin has a huge incentive to keep his nuclear deterrent functional, no matter how corrupt and inept the rest of his armed forces are.
I hadn't heard of that before, but it really isn't a counter argument to what I'm saying: when you're targeting civilians themselves, you don't have “collateral damage”.
Show HN: I crafted a macOS app to draw on screen
Skimmed the article and it seemed like a lot of speculation and redacted military communications. From Wikipedia:

On February 16, 2023, US President Joe Biden stated that the downed object was probably a civilian-owned balloon and "most likely tied to private companies, recreation or research institutions".

https://en.m.wikipedia.org/wiki/2023_Alaska_high-altitude_ob...
I think the idea is that padding results in lower storage efficiency, which means fewer rows per page and hence lower I/O throughput. By changing the column order you can reduce the amount of padding required.
Haha, since when is Ukraine even close to defeat?

Defeated enemies aren’t making regular incursions into the ‘victors’ land which the ‘victor’ can’t stop, or launching attacks agains the ‘victors’ capital.

This just reads like Russian delusion/cope.