skysight-inc/HackerNews huggingface dataset:
Are you referring to svchost.exe, the performance hack that allows multiple Microsoft-supplied services to share a single process, or the Service Control Manager[1], the Windows component responsible for starting and stopping Windows services?

If the former, I agree that trading off service process isolation for reduced start time and lower resource usage is an optimization that has probably outlived its usefulness and should not be emulated on systems that aren't severely resource-constrained.

While systemd arguably bundles too much functionality into its own process, AFAIK it doesn't include any mechanisms to support svchost.exe-like behavior in services it controls.

If the latter, I'd argue that the SCM is actually quite minimalistic, especially in comparison with systemd: it's responsible for starting services in the correct order per a supplied list of dependencies, restarting failed services, notifying services of important lifecycle events — service configuration changes, shutdown requests, network interface status changes, etc. — and that's about it.

[1] https://learn.microsoft.com/en-us/windows/win32/services/ser...
Like ComputerGuru said, even the README of the repository mentions both 4.0 and 4.00 as if they are the same.
Even if self-driving is 1% better in the best conditions, that's a safer car than one driven entirely by humans.

Humans right now are the best they'll ever be at driving, you can't say the same for self-driving cars. Even for a mediocre solution currently, it's likely better to use the self-driving in good conditions than drive it manually.

Computers never get tired, distracted, or emotional. What the humans' jobs are is to understand when it is a good condition for self-driving and when isn't it.

I'd venture to guess these fatal self-driving accidents are one of the following:

- freak accidents (ie: not the self-driving cars fault / it would've happened either way)

- accidents due to humans trusting the car too much (ie: we aren't level 5, be available to take over)

- the self-driving just being bad. This is the category a lot of people want these to be.

To get really morbid in my full-throated apology: cars are really dangerous. People die in car accidents all the time. The main reason these get attention is because it is notable. It's unfortunately not nationally notable when an entire family gets wiped out on their way to their child's soccer game in a non self-driving car.
So drug use is OK as long as you can do it off the streets?
The line is a piece of copper or glass that ends in a port in a rack at central point. The ISP is providing the connection from that point in the building to their equipment that does switching, routing, and yes billing you.
I have a friend with a paralysed larynx who is often using his phone or a small laptop to type in order to communicate. I know he would love it if it was possible to take old recordings of him speaking and use that to give him back "his" voice, at least in some small measure.

Unfortunately I have yet to see something that can do this and provide a voice model that you could plug into Android TTS and/or Windows which are what he uses.
4 years later and i'm still trying to get money back from tap portugal from a cancelled covid trip. fuck that company so much.

also, i bought the ticket from priceline, who "expunged" there database for customers from 2 years ago and older...which sounds quite convenient and sketchy.
The important part of this article to me is where the author writes that for some companies or government agencies, their communication practices do not pass muster. I’m very curious to learn more about that crappy government letterhead that the quoted psychologist Pamela Rutledge mentioned.
> for many software engineering positions in Silicon Valley these days

Do US most companies outside of Silicon Valley not use leetcode style interviews? Every single software interview I've done in Canada had at least one round of leetcode programming exams.
i'm still trying to get mine...
They tend to look like something someone who didn’t give a shit made. “I just need a box for people to be in, who cares what it looks like?”

The example brutalist churches in another post here look like someone doing a horrible experiment in the Sims made buildings without bothering to use anything but some default wall texture they found buried in the dev tools that doesn’t even tile very well, because they just needed a place to torture Sims in and don’t care what it looks like.

Yeah, that comes off as oppressive.
I was a developer on the Microsoft C++ compiler team from 1991 to 2006. We definitely didn't purchase someone else's compiler in that time. We looked at the EDG front end at various times but never moved over to it while I was there.

Perhaps the speed-up you remember had something to do with the switch-over from 16 bits to 32, which would have been the early to mid 90s. Or you're thinking of Microsoft's C compiler starting from Lattice C, back in the 80s before my time. There was also a lot of work done on pre-compiled headers to speed compilation in the latter half of the 90s (including some that I was responsible for).
Conservatism predicts aversion to consequential Artificial Intelligence (2021)
I actually think it was just a joke. Acknowledgingthat FSB and autopilot are accident prone and therefore appropriately named.
You don't need it to be government owned. While that is certainly one effective way of doing it, another can be to let whoever wants to build it build it, but require them to give access to competitors for a regulated fee.
Yes, GitHub code search is much better than Googling for the same information.

And ChatGPT can't show you the whole codebase which is important to understand structure - plus sometimes it's easier to surf around a few files than have ChatGPT print at you.
This would break the chain of trust (you wouldn't trust the network's key signing the address for that zone).
"I’ll probably write an elisp function to send the output to GPT and insert the results into the buffer"

I suggest taking a look at my LLM command-line tool. It's great for cobbling together these kinds of things, because you can use whatever shell integration your environment has to pipe things to it.

cat bad-dictation.txt | \
llm -m gpt-4-turbo --system '
You are going to correct for text that
has been produced by voice recognition
software. Rewrite any text provided to
you. The text will not have punctuation,
so please add where needed. If the text
has the word period, then insert a
period, and do not insert another one
just before or after. If the text has
“new line” or “newline”, insert a newline
character and start a new paragraph. If
the text says “comma”, insert a comma. If
the text has a number spelled out,
replace it with the actual number. So
“five thousand” becomes “5000”. Also, if
something seems off in the text, it was
probably due to a misrecognized word.
Please correct for it.' > out.txt

Should be easy to call that from elisp, and you can then install plugins to have it talk to other models like Claude or Llama 3: https://llm.datasette.io/en/stable/plugins/directory.html
Not currently. Someone already did lots of research on this — https://community.bitwarden.com/t/passkey-portability/59177

There’s some hope for interoperability between password managers someday. There doesn’t seem to be agreement on how you can securely export, transfer and import today however.
Bottled water is most often filtered municipal water anyway.
Sony requires that you use their tooling, which you can only get under NDA.
There's no reason to believe that commercial entities would be any less likely to spy on you than a government entity. The government can just pass security regulations that require access to infrastructure with gag orders in place so the infrastructure owner isn't allowed to talk about government access requests or actions.

The trick is simply to ensure you pick a government that isn't going to pass that kind of invasive legislation, or will remove it and retrospectively revoke all access granted under the legislation that they're repealing.

As for Great Firewall of USA, what makes you think it doesn't exist already?
You have to balance the cost of providing continuous, reliable power against the cost of losing power once in a while. The more flexible you are in your needs, the easier you can work around losing power and the cheaper you can make your power/storage system.
I am fully invested in the Apple keychain ecosystem, I’ve got multiple Apple devices (laptops and a phone) and passkeys have been incredible. Haven’t seen any of these issues.

I can understand the frustration from the author’s point of view, but I live with the other side of 2FA through weak SMS every day. My users can easily be tricked into giving up their 2FA code while being social engineered, and passkeys offer me as a developer a way to give them a more secure solution that I don’t have to worry about them reading aloud to someone calling and pretending to be CS. This is a weakness in the core of 2FA via SMS, and the author seems to be just hand waving away from that. No one SIM swaps their way to compromising a passkey, and no user can share their passkey with a scammer as far as I know.
It basically did. Cloudflare rolled out a free feature to enable HTTPS support on every site they served via (not unchecking? Don't remember the opt-in/opt-out detail) a checkbox in 2014, and less than a year later Let's Encrypt became available. Only a couple years later in 2018, Chrome and Firefox started marking non-http sites as "unsafe".
The power of attributes and get/set in languages like C# is similar. It's easy to turn value types into functions. Or to move a value into a subclass and you don't need to do a.b.c (moved c into b) because you can add c => b.c to the a class.
Is that relevant if the forked process only has to save the game-state to disk and then die? I'd think reading the game-state wouldn't require some mutex lock.
Laws and regulation.
Not everything is C, and nothing like that saves you when you move your floppy between computers.
But the article specifically says that the features contributed to the accident in foreseeable ways. Meaning that a human without the feature would not have had the accident. It may well be a power user problem, ie. it makes you better if you use it properly but otherwise makes it worse.
Thanks for this, I didn't realize the true scale of WW1. That's horrifying.

Imagine the industrial capacity of total war today...
> I don't think this is a particularly insightful article.

Data engineering can be lonely. I like seeing the approach that others are taking, and this article gives me a good idea of the implementation stack.
In fact, the opposite is true. While small datasets can be handled on GPU (although there are no good GPU databases comparable in performance to ClickHouse), large datasets don't fit, and unless there is a large amount of computation per byte of data, moving data around will eat the performance.
25Mb doesn't cost any more or less to provide than say 500Mb in reality. If your last mile infrastructure supports those speeds then it supports those speeds. Even the cheapest router possible to buy will do 500Mb.

This comes down to an argument about what "cost", it will cover the marginal cost of an additional subscriber sure (e.g additional customer support, sending a router out, taking a payment each month, 500GB/month across the backbone etc) but will not really be enough to payback the capital cost of the original fibre or coax rollout.
Still interesting though.
>> For whatever reason, 6x7, 6x8, 7x7 and 7x8 are a persistent hole in my ability to memorize

Did you learn them when you were young? Those are completely ingrained for me.
Working with Tailwind made me better at vanilla CSS. And it's a virtuous cycle: the better I get at vanilla CSS the more I've come to appreciate a) how composable Tailwind is, and b) how perfectly Tailwind dovetails into component-based application UIs.
The good thing about this usecase is that they do not need to solve the general problem of forking a multithreades program.

The child process is doing a very specific job that amounts to serializing the contents of memory and writing it to a file. Once that is done is can simply exit, and all the orphans are cleaned up.

While this is admittadly more complicated, it is the same general idea behind fork+exec. Sure, your serialization logic cannot call malloc, but how often do you really need dynamic memory allocation. And if you really do need to, you can use a simple mmap backed bump allocator (or any other custom allocator you want)

For datastructure locks protecting gamestate; just wait until the gamestate is in a consistent state before forking.

Of course, if you try reusing existing code, or forget about the limitations while writing new code; it would be easy to introduce non-deterministic bugs.
Governments already control private ISPs and compel them to have the capability to tap massive amounts of data, IIRC 1%. Were also talking about owning the lines not the actual switching and routing, in either case the taps would likely be placed at the ISPs offices.
For me, the closest language currently is F#.

The open-source ecosystem is not as massive as Go's or the JVM's, but it's not niche either. F# runs on .NET and works with all .NET packages (C#, F#, ...). If the .NET ecosystem can work out for you, I recommend taking a closer look at F#.

F# allows for simple code, which is "functional" by default, but you're still free to write imperative, "side-effectful" code, too.

I find this pragmatic approach works extremely well in practice. Most of my code ends up in a functional style. However, once projects grow more complex, I might need to place a mutable counter or a logging call in an otherwise pure function. Sometimes, I run into cases where the most straightforward and easy to reason about solution is imperative.

If I were confined to what is often described as a "pure functional" approach, I'd have to refactor, so that these side-effects would be fully represented in the function signature.

F# ticks the enums/ADTs/pattern box but also has its own interesting features like computation expressions [0].
I would describe them as a language extension mechanism that provides a common grammar (let!, do!, ...) that extension writers can target.

Because of this, the language doesn't have await, async or any other operators for working with async (like C# or TS). There's an async {} (and task {}) computation expression which is implemented using open library methods. But nothing is preventing you from rolling your own, or extending the language with other computation expressions.

In practice, async code looks like this:

let fetchAndDownload url =
async {
let! data = downloadData url // similar to C#: var data = await downloadData(url);

let processedData = processData data

return processedData
}

I often use taskResult{}/asyncResult{}[1] which combine the above with unwrapping Result<>(Ok or Error).

Metaprogramming is somewhat limited in comparison to Scala or Haskell; but still possible using various mechanisms. I find that this isn't a big issue in my work.

IDE-wise, JetBrains Rider is a breeze to work with and it has native F# support. There is also Visual Studio and VS Code with Ionide, which are better in some areas.

You can run F# in Jypiter via .NET Interactive Notebooks (now called "Polyglot Notebooks" [2]). I haven't seen this mentioned often, but this is very practical. I have a combination of Notebooks for one-off data tasks which I run from VS Code. These notebooks can even reuse code from my regular F# projects' code base.
Over the past years, this has almost eliminated my usage of Python notebooks except for ML work.

[0]: https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...

[1]: https://github.com/demystifyfp/FsToolkit.ErrorHandling?tab=r...

[2]: https://marketplace.visualstudio.com/items?itemName=ms-dotne...
I am french and didn't know about these, thanks for sharing.

Growing up in the north, I remember holes in the forests that were supposedly dug out by shells a century earlier. They were fun to ride on a bike.
I’ve felt for a long time that The Onion is the reincarnation of Voltaire: savage, subtle, clever, culturally relevant, slightly undersold in its time. They will be studied in history books, or whatever the equivalent of books become. Even if you don’t agree with the political spin, you cannot discount the beauty of how they took such a common political phrase and turned it on its head like that.
The funeral potatoes specialty reminds me of Jeanne Robertson's story about 7-up cake: https://youtu.be/-YFRUSTiFUs?si=O3vOnV5Ho8saWMui
If someone experienced in a field of research tells you something is possible, they're very probably right.

If they tell you it's not possible, it's 50/50.

Adapted from:

Clarke's first law: When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.

---

I don't think you need to be elderly - just set in your ways.

---

A valuable conversation would be why they think it wouldn't work. That will give you a lot of surface area to mine for clues to make it work.
My rule for feeds: if it's not reverse chronological, I won't use it.
This Substack article is plagiarized, by the way: https://news.ycombinator.com/item?id=40164077
nope, and that's (currently) by design! from a user perspective, passkeys are supposed to be impossible to duplicate. here are some workarounds:

- you can log into your 1password on multiple devices

- you can sign in by QR code, with the help of whichever phone has the passkey on it

- you can add multiple per-device passkeys to your accounts of interest (for example, log into github on desktop and then add a passkey for your desktop device for that github)

- you can keep all your passkeys on a hardware dongle

- you can set up and keep all your passkeys inside an open-source manager (e.g. KeePassXC)

For first-party systems, passkeys are supposed to be stored in hardware storage (TPM chips, secure enclave, etc). Once it's in the chip, the secret key's never coming out of those pins again (unless you're a nation state with a tunneling electron microscope and a very steady hand).

(The huge exception is iCloud Keychain and whatever Google's doing for passkey sync, but that's importing from account data into hardware storage, not exporting existing credentials from a user's existing device)
Key point here is buffer zone, which Russia has been repeatedly demanding for 30+ years.
Use whisper (or whisperx)
Oh yeah that’s bound to be as equitable as having the government provide it!
> Wealthy people smoke crack too.

Do you mind linking to some data on this?
Sometimes I wish I had gone into materials science like one of my HS teachers suggested. This is pretty dang cool
Ok, do you have a concrete example of this?
"UCS-2 is enough for anyone"
It's just endemic to the industry. Framework-itis
The real question is how many fatal accidents have been prevented by Autopilot.
Are alcohol restrictions combined with this law, or unhinged?
> As soon as games are networked it starts being a problem, and these days non-networked games are pretty rare.

So have your network protocol parser in Rust and the entire rest of your game in whatever the hell you want.

All the practical safety you could desire without any language constraints for the other 99% of the code
12to11 – run Wayland applications on an X server
Seven or eleven?
They (can) have different, less stringent elements, not fewer (state rules vary, but there can be a less stringent fault element than actual malice, though there must still be fault — defamation cannot be strict liability in the US.)
I think the period between having a playable alpha and a polished release is the part people hate.

Or just grinding out content to make the game longer.

I hope you enjoy the process and succeed as a game dev.
Bittorrent, can't negotiate a delta

what do you mean by that? as long as you don't recompress the git storage, bittorrent will only transfer the missing blobs. the only problem is that for each change a new torrent hash needs to be created. but you can stuff a new torrent with the git repo you already have and then bittorrent will only transfer the missing blobs just like git does.
Decades? Are you still talking about British Columbia, Canada?
One Neutrino Under a Groove.
Sure, I'll just log into all 500+ sites I have logins for and update them.
I find it notable that you threw in panhandling and "other nuisances" right up there with doing drugs in public. They don't seem comparable.
> There can only be so many wires running on the poles or under the streets

This seems like saying "there can only be so many condos in a city, so we have to ration them." Hypothetically if you had billions of fiber optic cables running along the same street you could physically run out of space, but that's an implausibly high number. Meanwhile you could easily have hundreds to thousands without any trouble.

> so in return for that privilege, you have to provide this in return.

The point of even wanting to do that is in order to charge a sustainable price for the service. If you had to provide the service below cost, why would you do it at all?
Victoria BC is the only place I've walked past someone smoking heroin out in the open on a busy city street. (Last October.)
It's easier to understand if you see people as divided rather than unified in a single direction. Stuff like this are the compromises between the 2 halves.
Your response to:

>Was it 'unprofitable' as in 'losing money', or 'unprofitable' as in 'not worth
the time'?

was:

>If you can make more money by not doing X, than doing X, it doesnt matter.

It's confusing, because you certainly seem to imply only doing the most profitable things.

>The purpose that they serve is to save your life with drugs. If that doesn't mean anything to you and isn't worth any money then I don't think we will find much common ground.

My point was that if their purpose is only to do the things that make marginally more money (while killing significant numbers of people or allowing them to die) such as the Sacklers and Purdue with Oxy, they deserve to be regulated into oblivion. If you think the heavy marketing and distribution of known addictive drugs into disadvantaged areas of the country is in the public interest, then I don't think we will find much common ground.

Frankly, most doctors, biochemists, and pharma-chemists I know have little difficulty seeing this. It is about helping people not just making money, and doing otherwise while selling it as the former, is unethical.
I'd be interested to hear the author's take on Nim [1], which seems to be better suited for game development than Rust by staying out of the dev's way [2], and supports hot-reloading (at least in Unreal Engine 5) [3]?

[1] https://nim-lang.org/

[2] https://youtu.be/d2VRuZo2pdA?si=E3N62oUJ-clXozCg

[3] https://www.youtube.com/watch?v=Cdr4-cOsAWA
These remind me of styling in Raise by Wolves [0] of the Mithraic [1].

By the way, it's a great sci-fi show and I was very saddened when I heard HBO Max canceled it (during its transition to Max). I unsubscribed from them and I'm boycotting them due to this hostility.

[0]: https://www.imdb.com/title/tt9170108/

[1]: https://raised-by-wolves.fandom.com/wiki/Mithraic
And of course, some drugs are more okay to do in public than others.
Yes, it's sad but I imagine he'd have a very popular blog these days if he could've refrained from blowing innocent people's fingers off...
> Is it not?

I'm not sure I understand the question. Yes, it is often attributed to him. If you mean "is it not true that he said it?", I don't know, but my suspicion, as with many such famous quotes, is that he probably at best said something like, or reminiscent of, it.