skysight-inc/HackerNews huggingface dataset:
Would it make sense for the AP to report that? No, of course not.

Could it make sense for someone to communicate that idea? Sure, absolutely.

Does it make sense to say the sentence you wrote? It really depends on who is saying what, and in which context!

My main point was: this looks like it was a misunderstanding (which, unless the source was fabricated, or just lying to the journalist, it was). I was presenting a hypothetical context in which that misunderstanding could arise.
Comparing to games isn't particularly great since games are ultimately low stakes and companies have learnt that gamers will tolerate pretty much any bug that doesn't literally stop the game from working. See: Bethesda games.
Look into guanfacine for combatting anxiety especially around task initiation. And if you still have some Ritalin on hand try microdosing it. 10mg tablet dissolved in 1 litre = 10ug per ml. I see beneficial effects on 5-10ugrams.
I've bought cars and houses and never had a problem. If I had enough money I could buy yachts, or airplanes, or entire companies. All of this could be done with the systems we have today. I cannot think of anything that is for sale that could not be purchased with dollars, if I had enough dollars.

What problem does crypto really solve?
Sure, but good code saves time even on really short timeframes.

Every time I've worked on—or seen other people work on—a "we must hurry at all costs project", enough time is wasted on debugging, firefighting and friction that just building a decently clean system from the get-go would have been faster. I've seen this unambiguously on "throw away" data science code meant to produce a single report (or normal science code meant for a single paper), and that's a much shorter-term effort than anything at a startup. The tradeoff is even clearer once you start working in weeks and months, much less quarters or years.
They do both, but right now the technology makes real defense (when you have real users) pretty much impossible. And not because of the NSA.
To be fair, rust at kernel level seems to have way more unsafe code than usual, though I have no experience in that area so I can't say much.
In rust you absolutely can "just take a lock around some shared data", but it is a bit different then other languages. mutexes actually contain the data they guard, making it impossible to modify unless you have the lock. There is another article about muexes by this same author if you want more details: http://cliffle.com/blog/rust-mutexes/
As a Rust monolingual the idea of being forced to use Ada sounds like a ton of fun. (I'm really curious about it)
At what point is it no longer tenable to say it was an honest mistake? What did the source have to gain from leaking the story? How do you avoid being used by some other source to plant a false story in the future? How do you avoid this source picking someone else to plant their next one?

Is there really no way to balance "destroy all sourcing for other news" with "not be a patsy for WMD style propaganda?"
Give kerbal space program a shot. It teaches you hard lessons about this and others.
Gratitude only works when it's serious, instead of a target metric like described here.
I like it, but full the card with something. If the browser can pull a summary and paint the card, that'd be boss.

https://www.linkpreview.net
https://www.peekalink.io
https://scribe.rip/@krthush/how-to-create-link-previews-like...
Yeah, but remote work is difficult enough to manage IN THE US where people are rarely more than a few hours apart and share a common language and culture.

Companies are not going to find it easy to hire Eastern European or Singaporean devs and get them to produce value - at least not any more than they did pre-pandemic.

Remote work has been massively overhyped; IMO it does noticeably make organizations less productive after some time has passed and people need to plan the next big project.

Seeing someone in-person is insanely high bandwidth. It takes an hour to plan a thing that might have taken a day's worth of frustrating meetings and two design docs.

I'm convinced at this point that anyone saying otherwise is either senior enough to be able to browbeat everyone else who has thoughts on their plans (and then design truly awful systems ime) or knows the truth and enjoys the extra free time.
If there are eyeballs, there will be ads. Right now, he cares about keeping the eyeballs and he's definitely doing that.

I barely used Twitter over the past 10ish years and I'm spending more time on it than ever right now.
Windows Subsystem for Linux (WSL) now generally available in the Microsoft Store
There was absolutely no reason to switch from Starship, but I hopped (shell-promt-hopped?) to oh-my-posh and am pleasantly happy with it.

https://ohmyposh.dev/
I saw the news in this tweet: https://twitter.com/shanselman/status/1595177845093183488. Says it's a big deal but I'm still not sure what the difference is.
C needs to bite the bullet and adopt slices as first-class types, so that they can be optimized on ABI level.
Hey! Just following up. We tried to recreate your issue but had no luck. We’d love to follow up with you and get this figured out. You can join our community discord and give us a bell: https://discord.gg/EXEuv2Ym
cmd-p is an absolute must if you use this plugin. Thanks for sharing!
I don't think you can reasonably draw any of the conclusions you've made from the individual statements you've said. User PII being misappropriated is far more likely to come from poor InfoSec practices than from the application layer. Memory safety issues are far more likely to accrete to application layer instability and crashes more than not; now that isn't materially good, but it's apples and oranges.

Then you talk about why "startups need regulation" and the lack thereof is why "the world remains an insecure mess" which is another non sequitur drawn from statements which, while individually correct, would never combine to imply that conclusion.

The world is an insecure mess because some societies have not collectively agreed that it is more expensive to be insecure than secure.

Startups don't "need" regulation anymore than regulation is a cure for any problem. In practice, poorly drafted regulation exacerbates rather than solves the problem it is scoped to solve because it opens the door for regulatory capture based monopolies.

That said, I do agree with parts of many of your individual statements: more effective regulations would be good not just for citizens but for startups and society in general; memory safety oriented code tends to be higher ROI for everyone; the world remaining an insecure mess is a pox on global societies whereupon well deployed investment into secure infrastructure would produced significant ROI compared to the present state of the world.
> I am not on the 'right', but it's clear the left and media have been using twitter as it's coordination and messaging infrastructure

You are not on the 'right' but calling out the 'left' while omitting the GOP (Trump, MTG, et al) and associates (Ben Shapiro, Tucker Carlson, et al) from your assertion.

If those on the right have not used Twitter for coordination and messaging, then they are far behind the zeitgeist. If they are, then you are likely not aware of that, or if you are, intentionally omitted that fact to make a point.
Did I miss it or does the article specify what tools Tremendous uses for their documentation?
What's the point of having an ABI if you can't assume it's being used?

If you don't want to trust any callees, you could use an ABI with all registers caller saves, but I don't think any mainstream ABIs are like that.

There's a balance where having some registers be caller saved and others callee saved means a lot less saving required.
The lifecycle of SARS-CoV-2 – news – Maastricht University
It absolutely blew me away too. I mean I kind of respected those engineers for being good software engineers but clearly their skill sets extended beyond that. Quoting from the investigation of how they blew up their tweeter:

> Assuming a constant resistance (which isn't true but it'll do for now), with the amp at 15.5 dBV, and input at -2dBFS, that's 13.5 dBV = 4.73 Vrms, current at 3.72Ω is 1.27 A. Almost exactly 6 W I was pumping into each tweeter.

> We have τ_Tvc = 3.9 and τ_Tmg = 70, and I think T_sett_vc=104.9 and T_sett_mg=129.5 are the thermal resistances in °C/W. That means that, if I'm mental mathing right, the tweeter voice coil would've reached >600°C after a few seconds, give or take (and longer as the magnet heats up).

> Yeah, no wonder I cooked it.
An ancient Persian way to keep cool (2021)
Here’s what I can think of. Not saying it’s valid, just justifications past “we love money”.

You can’t have an easy to repair iPhone 14. It is what it is. It can be redesigned to be easier to repair, with less glue and more screws and such.

But then it won’t be an iPhone 14 as we know it today. It would probably have to be thicker, etc. And what if customers don’t like those changes?

There are actual repair issues too. Right now there is a simple rule: we (or somewhere authorized) repairs it, or it’s not our problem. How do you adjudicate what’s a problem with the device and what a user broke trying to repair it for warranty purposes? They don’t have to today.

How much does it cost to keep making those parts as required? Do we need to raise prices to cover that? What if the prices of the components are too high and people sue saying we’re trying to discourage them?

If we have to keep making them should we redesign the phones less to keep down our legal supply requirements by reusing parts longer?

What if they go through with all this and almost no one does? Redesigns, new parts, guides, all that stuff. And 0.2% of people do it. That feels like a waste.

What if an Apple goes through all this. Do they make a “NY” version? Again maybe many people don’t buy it. Or do do what people probably want and make the NY the US or world version? All of those have different costs. Should NY be able to dictate a specific path? Is that fair?

What if someone owns the non-NY version but tries to repair their phone with official parts? Is it covered or not? What if they were in NY at the time?

What if CA passes a different, or worse incompatible, right to repair law? Then what?

What if NY required changes make the device unsuitable to some other country due to some odd law, but Apple only wants to make one phone (they do).

What if Google does it and Samsung says “screw that, drive to NJ”? But now Google’s phones are at a disadvantage because they’re thicker/more expensive/whatever?

I think that would be a lot easier on companies if it was a federal law. Obviously that won’t happen first, a state law is much more likely.

There are a lot of possible details. They’re not insurmountable. The answer to some may be “too bad”. But it’s not “there’s no downsides”.
Show HN: Google Form filling made easy via QRCode
Get tired of sharing the google form to email addresses one by one? Response Manager add-on makes the process easier by generating QRCode for the form and share that with your audience!
Wasm3 is already written in the tail-call style. Its IR consists of direct threaded code: a list of function pointers that each load and tail-call the next one. The only improvement on that I could see would be if there are spills because of the calling convention running out of registers.

Running out of registers in tail calls is one of the reasons I avoided that in doing Wizard's Wasm interpreter. One constraint there is that interpretation is done in-place (i.e. the original Wasm bytes). I wrote it in hand-rolled asm and it uses 9 architectural registers.
That's not actually the tradeoff in my experience.

If you're willing to blindly follow the suggestions given you by the compiler about references, and clone() things when it doesn't seem to work, you'll be just as productive as a Python/Java ... programmer. You'll just not be as memory efficient as a Rust programmer who actually groks that stuff. That's the tradeoff: coder productivity versus memory efficiency.
Often American visitors to the north of England are very confused when they are constantly asked 'Alright?' or 'you alright, mate?' - one got very paranoid asking me (because I've been in US for 20 year and I am bilingual American/British!!) wtf was obviously wrong with him causing the concern.

I explained it means, essentially, what's up.

If you bumped into a pal and said 'sup and he then went on to explain his day at length that would be weird, right?

American and English, it's almost the same language.
I had to google "Michael Scott" I'm guessing it's from The Office not the ex-CEO of Apple.
The arguing about Rust seems to miss that Rust protects against more than just security bugs.

If you've ever generated some object out of some factory and then tossed it on a list of things and then gone back to generate a new object out of the factory and found that the first object you put on the list got scribbled over because you forgot to clone it, then that's a category of bugs that rust entirely prevents.

And I thought I was pretty good about reasoning about data ownership in other languages, but the borrow checker is teaching me how to be a lot more careful.
Consciously or not, having rich parents makes taking big risks in life easier. Even estranged and rich parents could be a lifeline if a crazy plan goes sideways.

Very few in the USA have parents who own emerald mines or an equivalent amount of wealth. So they're not losers. They're just not as fortunate and--understandably--more risk averse.

I'm saying that Elon deserves a modest amount of credit for busting his ass in the early days. But not so much fawning praise since luck and birth also played a outsized role in his successes.
That's not the way to see the process. We have been highly successful at little languages already: they are, in essence, why when I write something like "a = a + 1" I can assume it works identically in C, Javascript, and Python. (Semantically, it doesn't! But it is a portable intent.)

You might object and say, "but variable assignment and addition, that's a big language thing." It isn't, though; it's just an infix expression. And infix didn't pop out of nowhere; it had to be invented as part of the gradual creep upwards from machine level "coding" into a more abstract semantics. Infix parsers are small, and while the complete language is larger, what it's presenting is infix-compatible. "Regex" is the same way: there is a general definition of regular expressions, and then there are some common variants of regex, the implemented semantics.

The boundary between "the language needs its own compiler and runtime support" and "the language exists as an API call you pass a string into, which compiles into data structures visible to the host language" is a fluid one. And the most reasonable way of making little languages involves seeing the pattern you're making in your host and "harvesting" it. In the previous eras, there were severe performance penalties to trying to bootstrap in this way, and so generating a binary was essential to success. But nowadays, it's another form of glue overhead. If you define syntactic boundaries on your glue, it actually becomes easier to deal with over time.

Documentation-wise, it's the same: if the language is sufficiently small, it feels like documentation for a library, not a language.
> I think if the reporter knew the missiles were fired by Ukrainian forces but manufactured by Russia, then he's ultimately responsible for…

I agree with this completely.

> In this case though I think it's more likely that his source told him something that wasn't true…

My point was that it could also been that the source told him something that was true, but the thing he understood it to mean was false.

So, source says “a Russian S-300 missile hit Ukraine” (where Russian was just intended to be a clarification about the manufacture of S-300), the journalist misunderstands as “a Russian launched missile hit Ukraine”, and writes the slack message.

Obviously, this is just a hypothetical, but it’s an example of why editorial should’ve waited until they had another source, and taken time to clarify/vet.
Yes, I have no problems with the particulates, it's the temperature that's the problem with the windows closed.
I don't think you really appreciate the scale at which this con occurred. Around this time last year, crypto was literally all everyone ever talked about. My brother, my cousins, their friends, a random bartender, every other attractive woman on Tinder who ended up pushing the pig butchering scam, hell even here on HN crypto was promoted like every other day. Not sure a blame the victim mentality is ideal here when practically EVERYONE got conned somehow. I only lost $1200 due to a pig butchering scam, but I learned from my mistakes and didn't invest any more. Others were not so lucky. Let's maybe have a little more sympathy given how widespread this contagion ended up being.
I would argue that a stronger type system will generally reduce bugs, and some of those bugs will impact users (whether by corrupting their data, or breaking a feature, or even causing a security issue).

Most bugs are from the programmer having a misunderstanding about how the system works as they change it. The stronger the type system, the more potential misunderstandings can be verified statically by the compiler before they reach the user.

Other, dynamically typed languages, will require either having unit tests, or running it in prod to find that user who has a null email or whatever, and results in things going awry. Since we're talking about startups, there are of course no unit tests or users, so this is all largely academic. Like, if there are 0 users to trigger bugs, and a bug that could be statically detected by a good type system exists, does it make a sound?
> advertisers were not sticky on Twitter ad platform since they are so ready to jump ship en mass within weeks.

They were not sticky to Twitter, the platform, alone. But to Twitter, the platform, coupled with Twitter, the organization, and the high engagement of its relevant ad, sales and advertiser relationship teams.

Which is where Musk went wrong, because that was part of the company that he needlessly drove out. The exact opposite of bloat! At least until an equivalent revenue stream was secured.
Yes, that is true.

However, moving a zero to a register does take time. Time that would otherwise be used operating with the zero value already present in the zero register.

The second best is what moto did.
As you point out, there is the instruction fetch, which could be the intended operation, rather than developing the zero itself.

On par with that is having enough registers to just hold a zero, and whether that made sense depended on the need and developer strategy.

I am a big fan of the moto CPU's, starting with the 6809. Just to be clear.
Ok, for some perspective here, that 45 seconds longer is about 50-100 times how long it took to do the one liner in javascript. Extrapolate that to generally 50-100x development time for the development of an entire project and you're looking at weeks to months longer development time to solve the same problem. Rust is slower to develop in by a significant factor than js, python, ruby etc.
Will Bob Iger Stop the Streaming Death Spiral at Disney?
Ransomware payments.
Unclear, but the sources I've read say that's just an Intel issue.

https://www.phoronix.com/review/amd-zen4-avx512/6
This entire affair has exposed the people who police "misinformation" as hacks. Simply suggesting that the missile might not have been Russian was shouted down and would have been banned on Twitter if you-know-who didn't own it.

This is how all the news is handled. It's not an isolated incident. If reporters are bad at handling a situation like this, they must be bad at handling other situations too. And the so-called fact-checkers base their information on stuff like this.
> an ecosystem that prioritizes safety etc.

Idiomatic Rust code is just as cavalier regarding NPEs as Java or Python code. Because the language starts to look really gross when you make your code panic-safe. So you have an `expect` here, an `unwrap` there, and now you're going to have the exact same runtime issues as the more expressive managed languages. No Rust programmer thinks their `expect` will panic, just like no Java programmer expects something will be null. Rust does not force you to "exhaustively match".
Stronger type systems do reduce bugs. But not all bugs are equal. When we talk about "velocity vs. safety" tradeoffs in SAAS software, we're virtually always talking about security vulnerabilities. There, it's much less clear that stronger type systems reduce vulnerabilities; in fact, the evidence mostly cuts the other way. As far as security is concerned, the major win is memory safety, and you can get that with plain 'ol Java or Python.

I'm bringing this up because in discussions like this, people tend to play fast and loose with the definitions of "safety". The kind of safety we're talking about in a decision between Rust and Java is mostly an externality to the SRE team, not to customers --- in other words, not an externality at all. An internality, if you will.
I've seen a pretty clear difference in success with less popular technologies based more on management philosophy and culture than the technologies themselves. Management seeing individual developers as fungible—"lack of fungibility in the engineering team can be a real liability"—is a massive red flag in this regard. I am not surprised to hear Rust didn't work out in an environment like that!
The morons almost caused WW3.
Talking to reporters: on the record vs. off the record vs. on background
As winter gets colder, you could try a G5 PPC :)
Let's remember the level of classification here though - in a usual org an occasional large data transfer might not be worth investigating, but in some contexts within the DoD it's certainly worth investigating.
I've still got a Formac Studio DV which is the perfect device for doing this as well. It's got S-Video and Composite inputs, a Firewire connection for video, and doesn't require any drivers for normal use. I think it's even powered by the FW bus. (It also has a built-in TV tuner, but that required special software. I'd rather use my HDHomeRun for grabbing OTA stuff these days.)

I think I bought all of this back in the mid-2000s when I was thinking of digitizing some video, but the it never happened. All my tests of it went great, though.

Old 2002 overview of the device: https://www.synchrotech.com/support/fomac-notes.html
I'm always amazed when reading about the sheer size of ice age animals that existed. I kinda get how dinosaurs were able to get so large, due to environmental factors at the time, but you would assume that food was sparse during the ice age. How did the ecosystem support large mammals?
As a Rust fanboy, I mostly agree with this sentiment. Theoretically, Rust should prevent “security” issues arising from memory safety issues like heartbleed (maybe not actually heartbleed) but a good GC would too. I do think Rust does push a little harder on correctness via Result types and things like Sync/Send traits, but I don’t have much Java experience to fully compare.

However, type correctness won’t necessarily prevent a DDoS, stolen password, specter, timing attack, phishing attack, etc. Type safety is a nice-to-have but not sufficient for security in SAAS products.
Would you consider money as a form of egregores? Money seems to have a live of its own full of money-live support systems, ie. buyers and sellers.
It seemed like a PR move that went horribly wrong. He got trapped by the offer that he probably thought he could back out of. I am sure he's all for free speech, but he tried so hard to kill the deal it makes me think he never really wanted it.