skysight-inc/HackerNews huggingface dataset:
> not having to deal with sales people.

This aspect does not get nearly the attention it deserves.

Unless your product is an exceptionally well focused developer tool, it will take months, and sometime multiple quarters, to see whether it adds any real value. Exceptions exist but are rare. In practice the generous[TM] 30-day trial period is almost always worthless, and often a gateway to sustained net negative.

Add to that the constant barrage of dark patterny attempts to infest your calendar and the upsell pressure tactics. Every third-party integration is an additional liability for maintenance, and far too frequently an increase in attack surface. Time is your most precious asset and the sales people are trying to rob you of it.

To every sales person on the planet: if you want to sell me a service or product, then sell me NOTHING BUT the service or product. Make useful documentation accessible, and make additional features discoverable, with unambiguous pricing clearly in place where necessary. Then get out of my way.

With OSS product I can install and trial it as long as I need, without needing to give off my contact details or be added to your invasive CRM. If I need additional features that are only available under your more restrictive license offering, I will buy them when I have the need. Your sales quota or bonus thresholds do not factor in, and if you try make them my problem, I will look at migration options.
For many use-cases they are indeed proper alternatives, but Jitsi has a much lower limit when it comes to numbers of participants. So if someone wants to organize a group call (the typical use-case) you come a with a lot more scenarios into trouble using Jitsi. And it hurts me to write this, because I hate how much growth Zoom had in the last year while being dishonest about critical encryption features. I would love to promoted Jisti and have tried so in the past, but I can't recommend something when it doesn't fit the use-case.

Signal, on the other hand, probably comes close to the WhatsApp features (I use neither one) and while I encourage everyone to to switch, I am missing the federation aspect. IMO, communication should be federated by law (which would also solve the network effect problem). Imagine a world where you could not call someone who has a phone number from a different provider? The current state of instant messaging is exactly this.

XMPP solved these problems decades ago and just because the standard didn't catch up with the speed of the mobile revolution, we don't have to reinvent everything from scratch. Properly implemented modern clients work very well (including reliability and battery consumption), the big issue though is that many traditional clients don't support all features and all companies in the business try, to build walled gardens as those tend to driver stock prices.
You forgot the link: https://aira.io/
On platforms that don't allow runtime code generation, such as iOS, generics are actually compiled ahead of time.

It's reasonable to ask if the same is done with NanoFramework.
Sorry, not a roguelike according to the Berlin interpretation [1], and neither IMHO.

At best you could say it's an action roguelike, but it looks like a generic fps, with maybe randomised layout (I hope) and maybe some rpg-like stats.

There's a lot of dilution of the roguelike term, and even while some variety and games that don't fully fit the term could be marginally accepted I don't think a randomised Borderlands could fit the genre at all.

[1] http://www.roguebasin.com/index.php?title=Berlin_Interpretat...
That makes sense.

But every security bug starts as a zero day. But yet some bugs become common malware, yet I others are not.

Why?

And is virtualization somehow special in that regard?
Performance as an afterthought is an interesting approach, after all this analysis actually posting the results would be useful.
I can send and receive messages now
Show HN: Minimal Snow with WebGL and JavaScript
To clarify, I was under-educated on how generics work, rather than being this clever.
I find document stores shine when you have known access patterns and can line your data up to meet those patterns. I find relational stores shine when you have unknown access patterns.
I get it's a glib comment, but serious answer because the answer is "same as every other language". JS is easy to write, has a vast ecosystem, a vast number of developers using it. Subsequently there are a lot more people writing their thoughts about it on the internet. There are lots of "new" frameworks, nobody uses them, but because of language popularity the number of people writing about {shiny thing} as if it's used is relatively high compared to other languages (PHP, for example, had the same issue, if it even is an issue).

1. See {thing}, assess whether to ignore it or keep an eye on it.

2. If {thing} is brand new, wait a year or so, then go to 1. If {thing} is a few years old and/or has [possibly suddenly] gained traction and/or provides immediate, obvious and significant benefits (assessing latter being where lack of experience can cause an issue), go to 3.

3. If {thing} is only starting to gain traction, wait a year or so, then go to 2. If {thing} has gained traction and is battle tested go to 4

4. If {thing} has traction + community + libraries + docs + tutorials then same as before, but more seriously, judge whether usable.

Early adopters using and writing about it are at stage 1 or 2 which could lead to stage 3 and 4. {Large company throwing resources at thing} may push it up ranking.

React/Vue/Angular and probably Ember are at stage 4. Svelte possibly 3 possibly 4. React/Vue/Svelte/Ember use same underlying paradigm. Would expect a developer familiar with one to easily switch productively to another in a few weeks. Not quite much of a muchness, but close enough. Angular slightly different paradigm. Usage of everything else is so low as to be irrelevant.

At first glance this is at stage 1 and is currently fairly useless. That's not a slight on the developer, just how it is. It doesn't affect any perceived "framework churn" because it will only be tried by very few developers. There may come point several years from now where it becomes useful and widely used (this seems unlikely from skimming the linked site, as it seems to provide nothing interesting, but I may be missing something), but now is not that point.
So it's Perl?
There are two possibilities: that Pompey/Trump want to sabotage Biden as you suspect; or that they don’t want this intel suppressed. Regardless, the timing of the release is unlikely to be a coincidence. Sadly, the deep cleavages in US politics are going to make most people view this through partisan eyes.

I am not inclined to dismiss this entirely though:

1) There were concerns about Gain of Function research long before Covid-19. I recall it was discussed on HN even (but can’t find the exact link)

2) There have been outbreaks of SARS linked to labs.

3) China has been secretive and uncooperative with investigations and has turned its wrath against an erstwhile partner (Australia) after that country’s government called for an investigation into the origin of the virus (maybe a coincidence as well though).

I am not inclined to unquestioningly believe the same government that lied/erred terribly on WMDs in Iraq, but I also don’t think we can unquestioningly dismiss the idea that the virus escaped from a lab that was doing experiments that would be expected to produce a virus of this sort, rather than a random mutation that just happened to be in a market in the same city.
Artificial Intelligence in Education: The Future of ‘Smart’ Learning
https://www.sciencemag.org/news/2016/02/will-plastic-really-...

That's not to say that it isn't true, just that the study is somewhat flawed.

To quote from the link:

There’s no question that accumulating ocean plastic is a
problem—but simple factoids can mask the fact that we still
have a lot to learn about what’s in the world’s oceans.
> Google features, such as […] Click to Call, that are only intended for Google’s use

What is this “Click to Call”?
Yes, this is all spot on, though I'd say the majority of developers actually building real things do understand JS, and would have a look at this, and dismiss it for the reasons you stated.
Apple is reportedly prototyping foldable iPhone screens
This is a pretty one-sided take. I think it’s quite possible to lose perspective when working on a large codebase. It’s also possible to have small bits of technical debt accumulate without anyone feeling the total weight of it all. Old code can use whatever fad was most popular when it was written or it can carry the cruft of old dependencies or api changes. Just because something is old it doesn’t mean that it’s good
Or if you do choose to rely on implementation details of specific hardware, you have to take on responsibility for managing breaking changes yourself. e.g. Implementing your own compatibility checks and fallback code paths, or knowing you will have to tweak and recompile for each hardware version.
It would work like it works for email. Most users will pick the default server. Over time other large (popular) providers will emerge and people will start to recognize the choice. Clients with branding will make that choice easy for non-technical users.

We know already it works. Federation and choice is a win for everybody. For this to start though you need either a good client/server combo for people to individually adopt, or a GREAT/POPULAR client with a default server.

I'm sorry to say that Element/Riot fails flat on this. I've used Riot and then Element for a while, and it got worse in usability and features (I genuinely can't stand it). As the reference client, it doesn't support multiple server accounts, which kill the ability to have an independent server. Federation is nice, but what's nicer currently is to be able to use matrix a teams/slack replacement where tech users can drive adoption. The central matrix.org server is slow already, and even with federation you cannot tell your users to switch servers because of this, defeating the point.

The positive side is that on the client side there's already choice. On the user front I've found FluffyChat to be vastly superior. Using Jitsi for audio/video was weird at first, but it works much more reliably than signal (I gave up on signal for audio calls due to the time it takes to establish a connection and the horrible lag it randomly has - to the point I just hang up and call via GSM to finish the conversation, defeating the point).

If I was element I'd get FluffyChat and it's author onboard as _the_ default client. On desktop I can choose multiple clients, and I have none of the "Signal" phone number/pin/central server/electron BS. It works as intended, and it will only get better with time. It's great.
This is pretty good advice and I'm glad I recently did some of the steps at a new company.

On the setup step I found it very helpful that my team has used scripts to rule them all, so setup was a breeze! I didn't know about that before.

Short explanation: https://github.blog/2015-06-30-scripts-to-rule-them-all
Came here to post this classic.

Mitchell and Webb had a moment when most of their sketches were gold.
I've been running freebsd my primary home and work platforms for almost 20 years and the only time I've had crashes that would have dumped to swap were when I was doing some driver development for early flash storage cards and a few times with the early ZFS merges.

None of my FreeBSD systems have swapped anything out in years. Most of the VMs get half gig of "I guess it might by used by something" swap space.

Somewhat ironically NVME would be insanely good for historical swap use cases but anything that cares about performance hasn't swapped in the better part of a decade.
No, it's a negative sign since half of the ~dozen people I got over to Signal are complaining and will probably go back to WA since Signal is still down after almost a whole day. The other half will probably go back if this takes much longer.
European here: 900m makes sense (and I see it a lot, 900 m (space) doesn't. I tried '400 m run' in youtube and all results came back as '400m'.
A simple application to compute working hours
For my side projects I'had to compute the salary and that was not a very happy routine. I create This
I have no idea what Arm’s involvement is in all this, but from the outside it has consistently seemed like Apple launches chips that don’t follow what is documented and then the requirements invariably change soon after. Just off the top of my head, they’ve been shipping their own custom memory compression instructions for a while now, and I am pretty sure their chips dropped support for 4K granules much earlier than the rules claimed this was acceptable. AMX showed up in A13, I believe? Which would be just before the linked article is dated.
The 6th Global Extinction: Insect populations suffering death by 1k cuts
I often think about the Biosphere 2 experiment. The question of how to create a materialy closed but energetically open system where humans can thrive is such an interesting one. And it is already a really hard problem. But the biospherians went one further. They didnt just wanted to build a working biosphere, they also wanted to make it mimic the earth. Like I understand if for some chemical or even psychological reason you need a giant pool to make your humans comfortable, but why spend resources and attention to create a salt mars of varying salt gradient? It just adds more moving parts to an already complicated puzzle. It is as if you don’t only want to build the worlds first aeroplane but you want it shaped like a jellyfish with tinny bells. They had a hard problem and made it even harder for themselves.
Thailand serves up cannabis cuisine to happy customers
How does this protect an individual inventor who invents (for example) a revolutionary new battery but is unable to secure the enormous capital needed to manufacture it? If the cost to maintain the patent is exponential then the existing battery makers need only wait for the inventor to go broke.
Zig does however go a long way towards memory safety, to be fair, and if you wanted to, you could also argue similarly that Rust does not guarantee 100% OOM safety whereas Zig does: https://www.youtube.com/watch?v=Z4oYSByyRak

I would also say that for "very large long lived projects", memory safety is not actually the most important issue, but rather correctness, followed by (in no particular order) safety, performance, explicitness, readability and exhaustive fine-grained error handling, the latter also not found in too many languages besides Zig.
The ‘Common Carrier’ Solution to Social-Media Censorship
After 8 years of writing Golang microservices one observation is comparing the compile times when optimizing for production.

A typical Golang CI/CD pipeline should
- compile without CGO enabled and with go build -tags netgo -a -v so that the binary can run on in a minimal docker image like alpine or scratch
- should be compiled and tested using the race detector
- should be linted using golanglint-ci

All of these flags and linters considerably increase the build time for deployment to production

The rust compiler effectively gives me the same outcome using the type system and the compiler advancements when targeting release musl.

I have seen many Golang projects where the race detector was skipped because the code base was to large or it was flaky.

One the other hand I do miss the code coverage tools. Code coverage for rust seems to only work on Linux
Ungated: https://archive.is/kf5yd .
From the steam page:

"Explore procedurally generated hallways, rooms and biomes!"

"Gain Levels to improve your Attributes and Skills!"

"Collect components and craft new items to improve your chances of survival!"

which along with permadeath and makes it a good match for the action roguelike term.
Not the parent, but I quite like the Kusto query language. It’s Microsoft specific, but the overall concept is nice and could be implemented more broadly. The operations are described as a pipeline, which to me is much more readable (and writable!) than SQL, where it feels like I’m always bouncing my mental cursor around to figure out what a query is doing. I’m sure that’d reduce with more SQL exposure, but understanding Kusto came pretty much instantly for me.

Also, each operation being its own line in the pipeline makes modification an absolute breeze, simply comment out, reorder, etc lines and the result will usually also be a valid query.

https://docs.microsoft.com/en-us/azure/data-explorer/kusto/q...
There are two other versions of the course[0][1], from 2005 and 2009. This 2018 version seems to be the only one without video lectures.

Actually, looks like both versions are using the 2005 videos (but with different UI: one embeds, one links to YouTube).

[0]: https://dspace.mit.edu/bitstream/handle/1721.1/56581/6-033Sp...

[1]: https://dspace.mit.edu/bitstream/handle/1721.1/118791/6-033-...
I don't know the contractual terms myself, but I suspect that if Apple is only doing this internally for their own products, it may well be none of ARM's business. It's only an issue if Apple sells their processors to other companies as components. In that case they are required to comply with ARM's certification requirements, because ARM doesn't want the market for ARM cpus to become fragmented. If Apple are only using these CPUs for their internal products I don't think those requirements apply.

It's a bit like the way the GPL has requirements that apply if you distribute the software (you have to release source code), but if you use your modified code internally the requirement doesn't apply. In this case "distributing" is equivalent to selling the CPUs as components, in contrast to using them in your own products (even ones you sell to customers) which counts as internal use and so the requirement doesn't apply.
Lots of inventions can be discovered by an individual with access to a lab (for example, at a university) yet cannot realistically be brought to market without billions in capital they may not have access to. Licensing is supposed to fix this by allowing these inventors to profit from their inventions without needing to get into manufacturing.
>giving a dose to a vulnerable person in a few days is pretty clearly more beneficial than giving it to a low risk person today

That's not entirely clear to me, if the "low risk" person is in a position to be a superspreader. Vaccinating a supermarket checkout worker now, vs an elderly person (who gets delivery food and never meets anyone) in a few days, could easily save many more lives.
I have given up too - people are complaining to me (via WhatsApp since it just works) because I recommended Signal and they signed up. Now I'm the guy whose recommendations are probably going to be ignored. Signal just isn't suitable as a replacement/daily chat app...
Looks really fantastic. its pretty general, but it appears to be “Unity” engine based. (The other major game engine that starts with “U” and is an English word)
I don't remember it having an outage of 24 hours.
I'm still constantly evaluating Nim, D, and Rust.
And tooling-wise, I think they are production-ready.

Not sure what kind of thing I write in Zig. Will also try it, anyway :)
I think this is a good example of a time when even the “general audience” is best served by using a “foreignization”, or even by just using the original word with some notes as to what that means.
Jwz: I told you so, 2021 edition
Disk is often slower than the network now. You do need to keep an eye on this. However, using tools like gRPC instead of wasteful JSON REST calls makes a huge difference and brings other benefits too.

Typically speaking you're adding submillisecond latency per external call, or you've done something wrong.

Something wrong can include incorrectly organizing your system. Two separate services that constantly chat with one another should probably be considered as candidates to merge into one, for example.

Deployment matters a lot. I see people mocking systems like Kubernetes and tools like service meshes, probably because they don't understand this critical and hugely beneficial capability they bring which is to organize communication on the bases of (amongst other things) locality and system topology automatically.

In the end, most people seem to totally miss the real reason that "micro" services (the "micro" part should really be ignored today) are beneficial. Hint: it's not a technical problem being solved. It's a people problem. Service oriented architectures give very clear boundaries around which a development organization can structure in a way that allows parallel delivery.

The biggest problem any growing organization will face is: they don't pay attention is contention (yes like as in concurrency/locks/etc.) across the development team(s).

I have personally witnessed and worked with a 400+ person monolithic development organization. This was essentially a "unicorn" and an exception that proves the rule. The one and only reason this organization was successful was because they had top to bottom extreme coordination managed by a very small group that worked effectively together. Without that tight central orchestration it would've been a nightmare.

Most organizations can't orchestrate a 7 person team effectively, good luck getting 200 to share a monolith well. So you break up the org and the architecture follows, see: Conway's Law. It goes both ways, too. You break up the architecture and the org can follow.

With that in mind, it's extremely important to get your boundaries right and for the love of all that is sane in a daily job, don't break it up too much. So many organizations would triple or quadruple their productivity breaking a monolith into literally 2 parts. If you can do 3-5 that's cool, amazing! Just because you can see the dotted lines between 25 different potential services doesn't mean your organization will tolerate that.

Anyway that was a diatribe.

TL;DR: "micro" services solve PEOPLE problems, moreso than technical ones, and the price you pay is additional architectural and delivery challenges which you must balance well and plan for
I agree with your desire to draw conclusions only on an evidentiary basis, but technically there is a logical flaw in your way of thinking:

If I isolate a virus from a bat in a laboratory, and then that virus escapes my laboratory (could be due to poor disposal of specimens, inadequate disinfection procedures for employees, etc -- not necessarily intentional), it would be both true that the virus came from bats and that the virus came from my laboratory.

I'm not saying that the virus came from the Wuhan lab. I'm just saying that "it clearly came from bats" does not preclude the possibility that the virus was stored in (or spread from) a particular laboratory.
Women on the Move
When was the last time you tried? My Synapse is stably hovering around 400M RSS with about 10-15% CPU usage. It has about 20 active users, each with 2-3 devices and is joined in hundreds of rooms on the federation.
Archive org link because Jamie has strong feelings about being linked from HN (even down to blocking the folk on Twitter who do so).
PhysURLs: A Physics News Aggregator
I'm using xed for it before reporting. Though I'm on fixed working hours.
The $15,000 equipment is too expensive for your department to purchase
Being retarded enough to shit all over a codebase that you just met means you are a garbage employee who should never have been hired because you're a fucking boat-shaker. So go dickchoke yourself if you think this is reasonable, I have fired people for less than arrogant shit like this.

Btw this is a lightning rod post, anyone who sees this please downvote and report!