skysight-inc/HackerNews huggingface dataset:
>The internal hard drive uses SCSI with an unusual connector. Adapting it didn't seem straightforward

this was the way:

SCSI is a bus mastering protocol which allows multiple masters to share the bus, which means you can plug two computers into the same SCSI bus at the same time and they will both be able to share access the disk device. You wouldn't want to rely on simultaneous access to the file system, but the entire disk from those days would be just a large file today and you could just dump the whole thing (the inconsistencies in the open file system would be like recovering from a crash, and none of the long term files would be affected)

> and we weren't confident the old file system (HFS) would be easy to read from a modern system.

the nice thing about opensource/New Jersey style is that that old HFS would be completely easy to mount loopback on linux

I still have a complete disk image of my old Mac SE20 from 1988, and I still mount it up from time to time, and I pulled it off my old mac through the scsi bus. I believe the 20 referred to the MHz of the 68020 processor, but it also coincidentally had a 20MB disk, as was the case for the SE30 that came out the following year.

> Deus fax machina: While the laptop has no networking software, it does have fax software ... The first question was how to turn the audio file into something faxable.

this reminds me of an old idea I had that I never pursued. Back in the days of fax there was generally a cover sheet for tracking/delivery of faxes in an office environment, but which seemed like a waste of paper/modem time to me who was never in a big org situation. To cut to the chase for my idea, I thought it would be cool to transmit something like a large QR code on the coversheet, which would be an encoding of the document you were sending in .DOC (ms-word) format. That way, you could fax to a fax machine, but if the recipient was a computer modem it could receive the document in original format, and abort (via handshake) the rest of the fax transmission. I thought it would be a gentle way to transition past "obsolete" fax technology.
He is a red herring not related to the topic in any direct way. In this context he is disingenuous talking point that conspiracy theorists who are detached feom reality bring up.
‘If it’s Boeing, I ain’t going,’ was the decision and last line my friend said when he was planning his travel the other day, and I was playing devil’s advocate with him. But deep down, I would not recommend to anyone I know to fly on Boeing anymore, including myself. So now, in addition to the cost, bags, and stops, I will be checking if the plane is Boeing and trying to find an alternative.
Analyzing text message conversations with my ex-boyfriend
https://dl.acm.org/doi/10.1145/356635.356640

Structured Programming with go to Statements, Knuth, 1974
Haskell would be great for designing the interface of a library like this, but not for implementing it. It would definitely not look like "old-school C++ or Java" but, well, that's the whole point :P

I haven't used ROOT so I don't know how well it would work to write bindings for it in Haskell; it can be hard to provide a good interface to an implementation that was designed for a totally different style of use. Possible, just difficult.
" > you are a clerk at a local grocery store... "
The lab leak theory is still mostly the realm of conspiracy theorists

Apparently including the raving nutjobs at the FBI and Department of Energy (https://www.cnn.com/2023/02/28/politics/wray-fbi-covid-origi...).
A suit of this armor would have been expensive as hell. Combined with the standard palace economy I would image it was rarely seen in combat even if it was used there.
As somebody who recently used Claude Opus to help quickly and affordably solve complex problems in 3D design work (OpenSCAD) while designing a marketable product, I have my doubts about your analogy. Prior to the availability of affordable and accessible AI, I could have taken some Bitcoin and paid somebody smarter than me to help me with this work, but I guarantee it would have been less economically viable, both in terms of financial cost to me and in terms of energy consumption costs.
Ticketmaster historically has had a very unusual architecture – they wrote their own operating system for the VAX, and ran their core application on top of it. When the VAX reached end-of-life, most users had a migration path elsewhere – VMS users went to Alpha, Unix could either go to Alpha or to a competing Unix platform – Ticketmaster didn't have any such path, because when you write your own operating system, porting it to a new platform is all on you. It didn't help that most (all?) of it was written in assembly language. So they ended up writing their own VAX emulator for Linux, and hence their in-house VAX operating system could continue to run as an app under Linux.

And they've been trying for years to get away from all that legacy on to a more mainstream platform. (And for all I know that legacy system is still running today.) But this breach clearly has nothing to do with all that, since it involved a breach of the Snowflake cloud database. So either the legacy system's replacement, or some supporting system.

Side note: Terry Davis was one of the developers of Ticketmaster's OS, before he wrote TempleOS, although they created their OS years before he was hired. He credited working on Ticketmaster's OS as part of his inspiration for writing his own
Not very much then... Tbh I think the existence of "packager" as a distinct job is a huge failing of the Linux software ecosystem.

As is the fact that 99% of Linux software defaults to hard-codes absolute paths and spewing its files all over the system, rather than installing to a single directory that you can freely relocate.
Napster was awesome but Audiogalaxy was way better: it just worked and had a remote interface which was magical at the time.
We've been using Nginx Unit in production for a Python backend for about a year now and it's been working pretty well. Some thoughts in no particular order:

- "Nginx Unit" is an annoying name to google when you have a problem. You get a lot of nginx results that are of course completely irrelevant to what you're looking for, as there is zero actual overlap between the two things. Using quoted search terms is not sufficient to overcome this.

- When it works, the all-in-one system feels great.

- However sometimes the tightly-coupled nature can be slightly annoying. For example, they publish packages for the various runtimes (ours is python) in the various registries, but only for the "defaults. Concrete example: we are currently running Ubuntu 23.04 but wanted to upgrade to Python 3.12. However Nginx Unit only pre-packages a Python 3.11 package for unit on Ubuntu 23.04 as that is the system-included Python. Had to build our own support from source, which was fairly easy, but still more difficult than our pre-Nginx Unit infra, where all I would have to do is install Python 3.12 and I'm good to go (because the python runtime wasn't at all coupled with the webserver when our stack was Nginx + Python + Gunicorn)

- I never properly benchmarked the two in a comprehensive comparison, but Nginx Unit is definitely faster than the aforementioned previous stack. I tested some individual routes (our heaviest/most important) and the speedup was 20-40%.

- Even when I tell it to keep a minimum number of worker processes around, it kinda seems... not to? I haven't properly tested, but sometimes it feels more like serverless, where if I haven't sent a request in a while it takes a bit of extra time to spin up a process, but after that requests are snappier. Definitely need to properly investigate this but haven't gotten around to it yet. It might just be the difference between allocated memory and not rather than spinning up processes.

- It's a shame it doesn't support SSL via Let's Encrypt out-of-the-box, like Caddy. To me that is the biggest (really only) missing piece at the moment.

- I much prefer using the HTTP system to manage config than files, and find the Nginx Unit JSON config much, much more readable than either Nginx or Apache configs I've worked with in the past. I'd also give it a slight edge over caddy configuration.

- That said, managing the config (and system in general) can sometimes be annoyingly opaque. The error messages are somewhat terse when updating config fails, so you need to dig into the actual logs to see the error. Just feels a little cat-and-mousey when you could just tell me what the error is up-front, when I'm sending the config request.

In summary, overall I've liked using Nginx Unit, but wish they would: change the name to something less confusing, add built-in Let's Encrypt support ala Caddy, and make the errors and overall stack feel a little less opaque / black boxy.
I think that this article is very interesting
>what's a good EV with no BS at all? No spyware, touch screens, etc?

Illegal to sell new, at least in Europe and US (see e.g. driver drowsiness detection) and very few people actually want such a car.

The only reason to ever make such a car would be for low cost, production, but in the car industry low cost can only be achieved with high volumes and since such a car absolutely has no mass appeal it is a pretty dead concept.
if anyone was even willing to do this for paid service, it'd be more like at least 150% of the labor costs.

https://www.reddit.com/media?url=https%3A%2F%2Fexternal-prev...

if you can find a good mechanic friend, and pay with beer and pizza, you'd be much more likely to be successful.
Ticketmaster, Santander data breaches linked to Snowflake cloud storage
Many of their defense projects haven’t been going well (notably space launch, refueling tanker, and jet trainer).
The minimum cost of an error is one cold branch. Which is effectively free on the happy path, and as cheap as it possibly can be on the error path.

A well-designed error handling system can feasibly reach this goal, at which point no more optimization is possible.

Edit @hinkley: I am unfortunately in hacker jail, and have used up my post quota, so I have to edit my post rather than reply to yours. Reply follows.

Throwing, the way Java and C++ do it, exceeds the minimum cost of an error, yes. Not that this is some sort of show-stopping problem, I'm discussing the minimum cost, not what level of cost makes errors too expensive.

A branch-not-taken, which is the opposite of processing an error, caught or otherwise, is what I described as practically free. Not always. If the only path forward is, for instance, to reference a pointer, and the error would mean that the pointer is a null pointer, the chip would have to wait for the branch to coalesce, which might mean a minor pipeline stall.

But if the processor can do further work, such as checking for an error on malformed input, where it's legal to speculatively execute the next decode on the predicted branch, it really is practically free. It costs considerably less than one instruction. If the branch triggers, the processor spills all the speculative work and switches. Since errors are expected less frequently than success, more or less by definition, that's the correct tradeoff.

This is why I described the error branch as "cold". The processor should predict and speculate on the happy path.

Zig is an example of a language where errors can be as inexpensive as a superscalar check on a given register while the main path moves forward. This is also possible in C when checking errno(). I can't speak for Rust, but enormous amounts of work have gone into that compiler, and it should indeed be possible to compile a match-on-Result to the same efficient level. Perhaps trickier since Rust doesn't "know" what an error is, but I suspect that in practice it can get this right.

Not that it's even mostly up to the compiler: there are ASM hints for the branch predictor in some instruction sets, but modern branch predictors don't need those to handle the case where 99+% of the time execution proceeds on one branch. It's conventional for compilers to emit "branch on cold, proceed on hot", but it's been a long time since that has mattered for execution speed. You'll get a bit tighter on a chip with no predictor and a shallow pipeline, like AVR, but for anything which can run an operating system it's almost irrelevant now.

I see no a priori reason why Go shouldn't achieve the minimum level either. Languages which use exceptions and try/catch must do some bookkeeping, which imposes a cost on the code whether an exception is raised, or not. That can be minimized, but not to the limit I'm talking about.

You might find this link interesting: https://ziglang.org/documentation/0.12.0/#Implementation-Det...

Note that the costs described are for the ability to generate an error trace, not error handling itself. This cost is only paid in debug and ReleaseSafe modes.
You could copy a book, and sell it. This was a big part of the Protestant revolution; the Catholic church didn't want the common people reading the Bible, but back then they had no legal way to control how people used the printing press.
This is called a "union" where I come from.
The lack of review can be obviated by googling, tho it's exacerbated by lack of publishing in general for this domain, likely cause it's not work done at a classic academic department, and no motive to publish for citation / impact factor reasons.

Also I find it refreshing that it's a very direct and practical approach to presenting results, which is missing in the scientific formula these days.
Good performance is a stretch. It's down 15% on the 1yr and 50% in the 5yr. Arguably it's a safe buy right now, but that's because, given what you say, it is unlikely to fall further. At least under the current administration.
Boeing is not the only US airplane manufacturer, it is the only commercial airplane (airliner) manufacturer.
It loses a lot of data in nuance, as well. I regret never having an SO halfway through my life. But it's easy to gloss over the fact that not all relationships are helpful and can lead to grief and consequences that exceed the cost of being single. So what I'm really saying is that I regret forgoing a very specific case of having an SO.
All statements about what people there wanted is pretty much speculation. And often these statements were later simply asserted by later historians.

The initial invasion didn't actually depopulate the Peninsula. It was reconquered but then new invasion from new Germanic people started again. And of course the Roman Empire is gone try to defend Rome and Italy.

Again, this is only obvious in retrospect and had it worked, we would remember it differently. And it had worked many times in the past.
Yoy produced a context free Link and ignore a ton of realities.

The astrazeneca vaccine the one in the UK did have problems and was still safer than covid! Compare the payout rates to the amount of people vaccinated and try having some nuance. The existence of a solution to a problem doesn't mean the problem was the size conspiracy nutjobs say it was.
For what it's worth, there are some benchmarks of kdb+ (the database built on k) here - https://tech.marksblogg.com/billion-nyc-taxi-kdb.html (it's overall a fantastic series of blog posts).
Keeping things focused to technology, I suppose: Android Auto in my car. Two things that drove me nuts recently, all in a single 10-minute trip:

1. I pulled over and started typing an address. The car screen helpfully displayed a message - as it does every time - that I can use my phone's keyboard. This message completely blocked half of the on-screen keyboard, so I could not type out an address until it faded away.

2. I hit play on the music app, and my phone started playing the music out if its speakers.
If you look at the experiments, they don’t mention observing a single entity of fractional charge, it is always in terms of aggregate behavior under EM fields: conductance(1) inferred from shot noise (2), or density (3)

(1) https://arxiv.org/pdf/0912.4868

(2) https://n.ethz.ch/~marnikm/files/shotNoise.pdf

(3) https://www.researchgate.net/profile/Gerhard-Abstreiter/publ...

Personally, I find it curious that people talk about detecting single photons, but in these fractional charge experiments, nobody mentions detecting a single quasiparticle.

As for the math, nobody says it outright, or even in a single paragraph, but a fractional charge (“filling fraction”) of p/q does correspond to p “normal” charges distributed over q degenerate states (q=2 equivalent locations I used in the naive example)

https://xgwen.mit.edu/sites/default/files/documents/topWN.pd...
Although I don’t disagree with your statement, I think that Fisker’s issue was primarily rush to push something to the market. From what I saw in the reviews, perhaps with a little bit of patience, they could have release a solid product.
Strong disagree.

>it's a poor use of my time.

You state this as a fact, but it's it really true? Is "a years-deep backlog of papercut bugfixes" really that important? I don't think so, the bugs have waited for 4 years already, they can wait another year.

In contrast, good technical blog posts bring actual value to the world. You share your hard earned knowledge with others[1] - imagine how much poorer the world (or HN frontpage) would be if nobody wrote blog posts.

Blog posts also bring marketing value to your company (way more value than fixing the css bug in privacy policy that was filed 3 years ago), and bring value to you (by allowing you to self-promote).

I'm not saying everyone should write - I do it because I like it, and my job is in large part research so I have insights/stories to share. But claiming you don't do it because it's a poor use of your time is - in my opinion - an excuse .

[1] Assuming you have something to write about, instead of writing yet another post about a well covered topic, like "introduction to C++". In this case I agree, that - unless your approach is really novel - it's pointless.
The egg. The parents was very chicken like though.
That's not because of the sandboxing, that's because WinRT required UWP. Microsoft since introduced Win32 sandboxing, which is how the Microsoft Store, most "inbox" apps on Windows, and Game Pass games work.

But sandboxing isn't a requirement on Linux, its an optional distribution method. When you look at a console like the Steam Deck, that system practically requires you to use Flatpaks for third-party software because the OS is an immutable image. If you install anything through pacman it will be wiped on the next OS upgrade.
Centuries ago, cultures tended to be far more rigidly defined and centralized along authoritarian (royalist) and religious hierarchies, and deviations from proscribed norms were punished far more severely. Therefore the premise that morals were more "adaptive" in the past than the present seems specious to me.

Also I don't believe the distinction between what the author considers 'moral fashion' and the natural process of moral evolution exists, the former naturally leads to the latter. Yet they seem to believe there is some objective means by which one can judge the quality of morals and predict their long-term adaptability.
Rather than doubling all income one option would be to make the existing income more evenly spread out.

For instance McDonalds' CEO makes ~$20 million a year[0] and they paid out $6.6/share with 726M shares[1] to parasite shareholders[2] while the average non-CEO employee makes $25k a year[3].

Since there are 150000 employees working for McDonalds that means lowering the CEO salary to $200k and eliminating shareholder payouts would free up close to $5 billion/year.

If that $5 billion were distributed evenly to all employees they would take in an additional $33k/year, more than doubling their salaries.

Of course all these numbers are estimates and there are caveats but the overall point is there's a lot of money out there that's going to a very few people.

0: https://www.restaurantbusinessonline.com/financing/mcdonalds...
1: https://www.macrotrends.net/stocks/charts/MCD/mcdonalds/shar...
2: https://finance.yahoo.com/news/income-investors-know-mcdonal...
3: https://www.zippia.com/mcdonald-s-careers-7238/salary/
Making cars is largely a manufacturing problem and a big company problem. It's not remotely like a software startup, or indeed, any startup.
The way you phrased it indicated that the Romans drew this line. Hence my response.
While this is certainly true right now, the clients will eventually revolt and go elsewhere.
Like I said, I don’t know what the solution is, because I think its a hard problem that we can’t just solve with education. I certainly didn’t propose blind belief. It’s true that doesn’t work. Blind disbelief also doesn’t work. I’m just pointing out that there’s evidence that “question everything” not only is not the solution, it may be feeding the trolls and serving their agenda, as is framing fake news as being suppressed dissent.

I agree some people label dissent as misinformation. I suppose that’s another form of fake news. Maybe part of the solution is to stop discussing politics all the time, stop listening to it, and stop taking sides. We don’t need to decide whether every thing a politician said is true or not, we have better things to talk about.

Yes it would be nice if we could teach people to have the right level of skepticism that fake news wouldn’t work, that’s a good goal to have. It would also be good to find a way to build some trust and stop the cycle of increasing polarization. We do have shared values. Figuring out how to talk about those again would be great. The trend has been in the opposite direction, maybe because gossip and drama and tribalism are easier. On the other hand, I do reserve a lot of optimism that most people are good and aren’t obsessed with politics. This article provides some evidence of that, if the majority of the talking points are spread by a tiny minority. Maybe there is a solution here that can address this tiny minority directly, maybe this isn’t a general populace education issue but one we have hope of fixing because the audience is rather small…
Homebuyers Are Starting to Revolt over Steep Prices Across US
The Bible is not copyrighted. So you could still do that today.

Also I‘m pretty sure the catholic church wanted no one to read the Luther Bible. Neither common people nor others ;)
>It ain’t easy making cars.

Fisker doesn't make cars. They design and develop some parts of cars (e.g. they even bought an existing platform) to be produced by others.

The product was far too late and underestimated how hard it is to just design the passenger facing elements of a car.
The haughtiness is not for nothing. Since Dec 2023, they made a lame excuse that Pytorch didn't support 3.12: https://github.com/taichi-dev/taichi/issues/8365#issuecommen...

Later, even when Pytorch added support for 3.12, nothing changed (so far) in Taichi.
Inventing technology is hard under water, hence octopuses created us to build them spaceships so they can go back home.
https://archive.today/IWVjD
Is that possible? Don't the airlines swap planes at the last minute?
Oh I have which I why I'm surprised that everyone is reading this as the police doing a good job. This is a story of the police failing to do their job 14,999 times and only getting it right on try 15,000 because one of the victims solved the case for them.
Fisker isn't a car manufacturer. They didn't do the manufacturing. They even didn't do that much development on the actual car.
My main argument against this practice isn't performance, it is that it makes error handling more difficult to write, review, and maintain. Treating errors as opaque and passing them up the stack in the general case is automatic and trivial to get right. Wrapping them is not.

I agree with your point about debugging, but I have a different idea how to best achieve it. Rather than wrapping an error at every stack layer, just take a stack trace when the error is created. This works great as long as... you don't design the system to require sentinel errors. Treating errors as rare, exceptional events rather than normal values used for control flow changes how you approach them.