skysight-inc/HackerNews huggingface dataset:
Pod Save America interviews Kara Swisher at the end of the most recent episode [1] And at the very end of that they discuss TikTok and China.

Swisher is no fan of Facebook, but she also sort of casually describes China as have different “values” than the United States with the implication that the values are not as good and that it is not good for a Chinese-owned TikTok to have so much data on US citizens.

It struck me because the comment went unchallenged by the host. I have my own biases against Chinese “values” due to what I’ve seen in my security work and also from what’s happening with the Uighurs in China now.

Is there contemporary moral superiority of the United States over China? I think most Americans would say yes without a lot of detailed reasons why.

I’d compare it to whether Craigslist has moral Superiority over eBay. Seems possibly obvious but the truth is more nuanced.

However, all historical context is set aside to make this statement. United States’ current and past moral failings are not really held up for discussion.

[1] https://podcast.app/youve-got-no-mail-e109788978/?utm_source...
Tesla's automatic wipers are bizarrely bad. At one point Elon touted a new neural net upload that was going to make them better, but they actually got worse.

My Dodge truck has much better automatic wiper control than my Tesla.
Isn't TikTok just a Vine clone? Social networks have always been derivative and iterative.
So has Honda
Yesterday's discussion:

https://news.ycombinator.com/item?id=24055823
You don’t have to download the internet upon each build.

First, in a corporate environment it’s common to run builds backed by artifact servers that’ll cache just about anything.

Second, it’s easy to place files in a Docker build context (that’s just a $25 dollar way of saying “next to the Dockerfile”) that would have been downloaded from the internet, but are stored locally instead. This is easier said than done for some formats. Source tarballs? Easy. Anything Java or Debian that requires a pesky server which works a certain way? You’re going to have to use a caching artifact server.
*5 years (not to say the next 50 won't be awesome too)
Why Elon Musk is not an engineer
Westinghouse Files for Bankruptcy, in Blow to Nuclear Power (2017)
I recall sometime in the mid 2000s there was a fever for achieving five-9s (99.999% uptime, I think -- it became fodder for a few episodes of Mr. Robot). Not that the metric ever went away, but back then a lot of BigIron(TM) vendors advertised achieving five-9s by replacing hardware while the OS remained running and continuing service. Sun 15K and 25K series (Gilfoyle had a used one in the garage running his network) were behemoths whose mem/cpu boards you could swap out wholesale while the entire frame and backplane was powered on, and while the OS the board came out of remains functioning. There were many caveats around the procedure but it worked. Execs and sales guys loved those demos. These monsters were expensive and banks and energy conglomerates were buying them by the dozens. There was also a big todo about hot swappable drives. The idea that you could be doing hardware maintenance while the machine was still running was a novelty, something like brain surgery while the patient was not only awake, but awake and eating, driving his car, talking on the phone, etc.

A decade later I look back with deep surprise that we didn't think to abstract out the service instead of the hardware. I don't know how many of those behemoths are still being bought, now I work almost exclusively with small server instances that can come and go on the fly. Micro services and AWS have taken five-9s in a different direction. I frequently think of Sun as a failed Hephaestus, in a Christopher Nolan film he would be brilliant but could only turn out clumsy tools because of his deformity, he hates the things he makes so he throws them away before completion. Men find these cast-offs and temper and refine them.
this is not technically impossible, but a slippery slope to go on, I wouldn't risk prison time just to save an embarrassment for sure.
Strong typing over the long term will always produce a more maintainable software product when used correctly. For many applications, you might not encounter enough complexity for it to matter strongly one way or another. Once you do finally encounter that application with 40 different entity types, 12 different business contexts that each of those can uniquely interact within, and hundreds of properties for each, you will be scrambling to find some way to bring order to your chaos.

Dynamic typing is useful if you are forced to develop software before you understand the business model or if you need to expose some DSL to your users. I normally view it as a short term option that is typically reached for when not enough actual engineering has occurred (in more complex systems). It's also mandatory for working within certain domains (i.e. the web). I think this last point is why so many seem to think its a perfectly acceptable way to carry on in any sense.
Well, I honestly don't care enough about non-identifying data being collected to continue this discussion. However, if you really feel that this is illegal under the GDPR, rather than wait for lawyers to get involved (which might never happen), why not open an issue on the VSCode repo and discuss it there?

Even if they dismiss it, it might help matters for lawyers at a later date - as in, they can point to the issue that was opened and say, you cannot deny being aware of this issue because you dismissed people's concerns previously.
Google catches up to AWS and steals a march on Azure introduction of cloudy CA
Sounds like a problem that you could also solve via things like universal rent control. Lock the rent of all units. If you're not happy with the rental income of a unit, you're free to sell it to someone who wants to buy a primary residence.
Instagram is the beta test environment/battleground for Facebook.
Aristotle's Irredeemable Ableism
China slams President Trump's TikTok banned-or-be-bought plan in the US
> ZGC will have a <1ms worst-case latency

In our benchmarks we never saw a GC pause of more than 2 ms on either ZGC or Shenandoah, but the end-to-end latency, the one the user cares about, is impacted by much more than a single GC pause. Sometimes there would be several pauses in a rapid sequence, or just the background GC thread would do too much work at once.

Even after dedicating a core or two to the GC, you still face the issues of cache pollution and RAM throughput stealing that heap walking incurs.
s/copy our products/steal protected IP/g
The stalking thing seems hyperbolic. In my experience as both shopper and employee, many seek to have as few conversations as possible.
Thank you for posting these. Some other links of potential interest:

https://www.wired.com/story/surviving-as-an-old-in-the-tech-...

https://www.linkedin.com/pulse/google-leaders-greyglers-navi...

https://www.amazon.com/Wisdom-Work-Making-Modern-Elder/dp/05...

These are from https://about.gitlab.com/company/culture/inclusion/tmrg-gitl...
>The downside is that it is a very common marketing trick.

"The less you intend to do about something, the more you have to talk about it." However this maxim is not applicable here because compile times actually have been improving.
>assume people can't not form racist views because they can't figure out the context when someone uses the name of a color.

The parent did not do this. It sounds like you've constructed an exaggerated version of a potential assumption somebody other than the parent could make: That a particular person may be feigning "not knowing" what the terms means, which frankly is not surprising, considering how incredibly bitter some people feel about these terms, but of course neither is it surprising to sincerely not know what they mean, since they are new terms, regardless of how explicit they are (you need at least a modicum of context if you've never heard them before). So the person you're attacking surely exists (a person who would make this accusation in every case, with no benefit of the doubt ever given), but that person is not here, nor could we know if they are here given the limited sample size of chances they have in this thread to express such an uncharity.

As for your frostbite example, obviously nobody seeks to control the reality of what color frostbite is. I feel like you may have jumped the gun on that analogy.
I've thought about that a lot recently as I have a double cylinder deadbolt I want to replace our single cylinder one with, since the door has 3 panes of glass that can be easily smashed allowing the single deadbolt to then be easily opened.

Sounds great until you think about a fire situation. I think we're just going to keep an extra key very close by but that solution only works because we don't have kids; I'm not sure I would go with the double cylinder deadbolt if we did.

(And yes I know it's against the building code but I also know people regularly do double cylinders on their own personal homes. You'd never do it in a rental, AirBnB or commercial building of course.)
> and cannot run on the same domain as `widget.com` since it also contains user generated content.

Why not host at usercontent.widget.com? You can pass credentials via a frame postMessage, are protected by same-origin policy, and cookies would be considered first-party
How have you misinterpreted this message to get to that conclusion?
Also nuclear is only weakly dispatchable, something the comment you replied to misses. So it is not suitable for filling the gaps.

A 100% nuclear grid will need dispatchable peak power as well, be it gas or storage.
> you're living in a very small bubble.

Why did you try to make this personal by attempting to insult me?
A Saturn-like world hugging its star
Slack may have discovered a marketing niche, but team chats existed for decades.
I'd just like to interject for a moment. What you're referring to as 'von Neumann architecture'...
> If the government will now give you a monopoly for the rest of eternity on any invention that you label "secret"...

You're misunderstanding it. If you steal a secret's blueprints, the government will come after you. If you reinvent the secret's methods yourself, you're free to do whatever you want.
I really love the out-in-the-open development process. It doesn't cost SpaceX anything, yet they attract lots of internet media where people set up streams, discuss progress etc.

The next year should be pretty exciting as they develop things further. Starship has a number of big innovations, which are:

- the raptor engine. This was developed behind closed doors and is sort of finished. We won't see much of it, but it is the most advanced rocket engine ever made and I'm not aware of any upcoming engine that can compete with it.

- Stainless steel construction. What we're seeing with SN5 is the basic tank structure of the second stage. The hopper that flew last year was a neat demo, but SN5 was pressurized and the design is way closer to what the actual starship will end up having. The first stage tanks will also be a stretched version of these tanks, so that's why you see them focus on this so much right now.

- belly-flop landing. To land, starship will be coming downhorizontal until a few hundred meters above ground when it'll make itself vertical to land. SN5 won't have the fins and cone to perform this, but SN6 will. It might be possible to see this before the end of the year - SN6 (with 3 engines) goes up 20km, goes horizontal to burn off speed, then lands vertically.

- belly-first re-entry. Instead of a heatshielf that withstands a high temperature, Starship will burn off speed with its belly, but do it over a longer time period of time so that while the total heat is the same, the max temperature doesn't rise too much. The stainless steel can't take the temperatures ablative heatshields on capsules can. Don't know if Starhip will be able to perform this meaningfully without a booster.

- in-orbit refueling. Starship is big and heavy and basically can't get anywhere unless it's re-fueled in orbit. I don't think this has been done before, definitely gonna need 2+ starhips and boosters to show this.

- superheavy booster. This might be the simplest part of the whole system - a first stage with 31 raptor engines.

Lots of stuff coming in the next few years.
Thanks for these awesome references!
I wonder if this acqusisition explicitly would remove the monitoring in TikTok, or simply migrate it into Microsoft hands?
Mmm. Worth noting that PHP as a language has been moving pretty fast lately. The 7.x series is something like 2-3 times faster than 5.6 in most benchmarks, plus a lot of developer friendly features have landed, and some useful security features, which has led to a lot of people cutting support for older versions.

I understand the logic behind running Debian until the end of extended LTS, but it's going to have a number of drawbacks. Not being able to use a supported version of Laravel is probably not the biggest one either.

It's not a tradeoff that would be viable for my team, at any rate.
You might say what's unusual with Levandowski is that he made so much money while working for someone else; and while not actually achieving any additional revenue.

If a battery or metals (or self-driving) engineer comes up with a material break through and starts a company they could easily eclipse Levandowski's earnings.
In France, they fixed this by not allowing doctors or drugs to advertise. One of the best decisions ever, for a lot of reasons: you cut care cost, and you avoid that kind of third party profiteering.
What's the hosting story for crux if one wanted to try it out on a side project?
>If you support your "values" only on a reciprocal basis, essentially you renounce them. And you certainly lose the moral high ground when you try to get others to adopt these values.

I can't agree with that at all. I hold non-violence as a value, but I'm also going to defend myself if attacked and I don't think that means I renounce my values or lose any moral high ground.

There are plenty of situations where supporting a high-minded value requires reciprocation.
That’s exactly how I read it as well until I noticed the upper case R.
Anecdotally I have heard of students having trouble figuring out what the terms mean. You're even admitting it yourself -- if you have to rely on looking them up in the dictionary then it's obvious they aren't obvious terms! No one has to look up "allowlist" and "denylist" because they do exactly what they say on the tin.

You have yet to give one valid argument as to how "whitelist" and "blacklist" are better, and indeed, have unintentionally given one argument as to how they are worse.

And yes, they are strictly engineering terms. Merely appearing in a dictionary doesn't mean they aren't. Most technical words are in the dictionary despite not being used outside their fields, e.g. here's one: https://www.merriam-webster.com/dictionary/stator
They are easier to update too with new features and buttons. The parent's point about tactile being better when driving is still valid though.
That’s the case with other compiled languages as the debug and release builds have different optimisations.
10 hours investment for no downtime seems like a good deal for the owner
The Illustrated Transformer – Jay Alammar – Visualizing ML One Concept at a Time
At this point I think we are arguing somewhat subjective things.

I used to be a hard-core zealot for the JVM as the performance platform of the future - and did talks arguing just as you are here why HotSpot outperforms $LANGUAGE in real applications. I feel like I'm hearing myself in your argument..

I wrote a signficant portion of the Neo4j storage engine, which is in Java. Now I'm writing another database engine in Rust (sidenote: not for replacing the Neo4j engine, just because it's interesting). Arguably database engines qualify as "significant applications".

I find - subjectively:

- Maintaining performant code in Rust is easier. I do the same patterns as I did in Java, except it doesn't rely on easy-to-break assumptions of how HotSpot happens to work (ex: stack allocations)

- Like you said elsewhere, the issue is often about fragmentation, ultimately stemming from object churn. I find that Rust makes it, culturally perhaps, easier to maintain low allocation code than Java. (sidenote: I think these two points is also why Go code generally has "better GC behavior"; Go doesn't have a better GC, it has a language that encourages less heap allocation)

- The engine I'm writing in Rust is faster than anything I've written in Java and - critically - runs for days and months without notable stalls.

Come to the dark side!
> the type system is just in the way

That's an usual symptom that you are trying to write untyped code in a typed language.

There are few cases where types do get in the way, but in the huge majority of the cases the types are there for you to explore your ideas on them first, and only mess with the code once they make sense.
Leaky AWS S3 buckets are so common, they're being found by the thousands now
Lower stakes, but ~15 years ago a friend had a Linux box in the corner that had huge uptime. I want to say the uptime started shortly after the kernel patch that fixed the 400-ish day overflow of the uptime counter. He moved to a new home and very carefully moved the running server using it's UPS. He didn't have to worry about keeping networking up though.

I used to be all about long uptimes. I eventually started seeing long uptimes as a negative though. A long uptime probably means patches have not been applied.
Nicholas has been doing yeoman's work on speeding up the Rust compiler. This is the latest in a long line of contributions to tackle what has been one of Rust's most persistent problems: long compile times.

* 2020-08-05: "How to Speed Up the Rust Compiler Some More in 2020" https://blog.mozilla.org/nnethercote/2020/08/05/how-to-speed-up-the-rust-compiler-some-more-in-2020/ (this post)
* 2020-04-04: "How to Speed Up the Rust Compiler in 2020" https://blog.mozilla.org/nnethercote/2020/04/24/how-to-speed-up-the-rust-compiler-in-2020/
* 2019-12-11: "How to Speed Up the Rust Compiler One Last Time in 2019" https://blog.mozilla.org/nnethercote/2019/12/11/how-to-speed-up-the-rust-compiler-one-last-time-in-2019/
* 2019-10-11: "How to Speed Up the Rust Compiler Some More in 2019" https://blog.mozilla.org/nnethercote/2019/10/11/how-to-speed-up-the-rust-compiler-some-more-in-2019/
* 2019-07-17: "How to Speed Up the Rust Compiler in 2019" https://blog.mozilla.org/nnethercote/2019/07/17/how-to-speed-up-the-rust-compiler-in-2019/
* 2019-06-25: "The Rust Compiler is Still Getting Faster" https://blog.mozilla.org/nnethercote/2019/07/25/the-rust-compiler-is-still-getting-faster/
* 2018-11-06: "How to Speed Up the Rust Compiler in 2018: NLL Edition" https://blog.mozilla.org/nnethercote/2018/11/06/how-to-speed-up-the-rust-compiler-in-2018-nll-edition/
* 2018-06-05: "How to Speed Up the Rust Compiler Some More in 2018" https://blog.mozilla.org/nnethercote/2018/06/05/how-to-speed-up-the-rust-compiler-some-more-in-2018/
* 2018-05-17: "The Rust Compiler is Getting Faster" https://blog.mozilla.org/nnethercote/2018/05/17/the-rust-compiler-is-getting-faster/
* 2018-04-30: "How to Speed Up the Rust Compiler in 2018" https://blog.mozilla.org/nnethercote/2018/04/30/how-to-speed-up-the-rust-compiler-in-2018/
* 2016-11-23: "How to Speed Up the Rust Compiler Some More" https://blog.mozilla.org/nnethercote/2016/11/23/how-to-speed-up-the-rust-compiler-some-more/
* 2016-10-14: "How to Speed Up the Rust Compiler" https://blog.mozilla.org/nnethercote/2016/10/14/how-to-speed-up-the-rust-compiler/ (the post that started it all!)

He's also written about tools and concepts for crate maintainers to understand and improve their own compile-times:

* 2019-10-10: "Visualizing Rust Compilation" https://blog.mozilla.org/nnethercote/2019/10/10/visualizing-rust-compilation/
* 2018-11-09: "How to get the size of Rust types with `-Zprint-type-sizes`" https://blog.mozilla.org/nnethercote/2018/11/09/how-to-get-the-size-of-rust-types-with-zprint-type-sizes/
* 2018-07-24: "Ad Hoc Profiling" https://blog.mozilla.org/nnethercote/2018/07/24/ad-hoc-profiling/

He's also contributed to useful profiling tooling!

* 2019-04-19: "A Better DHAT" https://blog.mozilla.org/nnethercote/2019/04/17/a-better-dhat/

All this to say: huge thank you to Nicholas, and if you're interested in learning how to do real-world performance work, these posts are an excellent resource!
my grandfather called this the "asshole quote"
Speaking from experience, you're most likely to be upsold if you don't know what you're looking for. For example, I've been upsold when I was buying a printer. I know nothing about printers, so much of the purpose of going to Best Buy was to see what they had and what the salesperson recommended.

Most HN members are unlikely to be upsold due to high technical knowledge. You are probably more likely to have done research ahead of time and know exactly what you're looking for.
It's not like Tesla doesn't have people who know a wiper stalk is good

It's just their design goals are not "make the most convenient or practical control we can"

They're "make it cheap to manufacture" "make it easy to manufacture" and "make it perpetuate the vague feeling of futurism we go for"

The giant touch screen is at the intersection of all three. It's truly awful, but people convince themselves "this is the future!". And they say stuff like "I can't imagine going back to anything else" because by comparison the buttons feel dreary and old.

Then to keep up other manufacturers start to follow suite and now even pickup trucks are bragging about having 12 inch touch screens in their advertisements and how the competing truck doesn't ...
Already submitted, and on the front page: https://news.ycombinator.com/item?id=24060100
* better GCs (plural)

Probably the best thing about the JVM that, AFAIK, no other platform does is it gives you an option for which GC you use. Not only is that an option, but you are spoiled with options. ZGC, G1GC, Shenandoah, The parallel collector, the serial collector. Pick the right one for the job!

But beyond that, they are infinitely tuneable (Not that you should usually). Again, not something that almost any other platform offers.
I wonder how the interpreter works. In their Performance page they write:

> It’s similar to Lua interpreter in that it’s written in C, but it’s highly tuned to yield efficient assembly when compiled with Clang and latest versions of MSVC. On some workloads it can match the performance of LuaJIT interpreter which is written in highly specialized assembly.

One thing I've been experimenting for my own project, is using tailcalls. All main compilers (gcc, Clang, MSVC) are able to compile that into actual tail calls (i.e. `jmp`, not `ret`, so that the stack doesn't overflow) (with optimizations enabled), even for indirect calls (i.e. dispatching depending on the next instruction). Function parameters (VM state) are assigned to registers, alleviating Mike Pall's main complaint about writing interpreters in a high-level language, that the compiler cannot optimize the huge loop as well as a human can. I need to test this on a full interpreter with 50 or so instructions, to see if the optimizations still apply.