skysight-inc/HackerNews huggingface dataset:
These got a lot of attention a while back. But their use case is limited because they're really short-ranged. These things go all out soon after leaving the tube, make a hell of a lot of noise, and are good only really close in. They're sort of a last resort weapon, a snapshot provided that the enemy shooting at you is even within range.

A modern US Mark 48 can swim out quietly under wire guidance and emit no noise or sensor emissions, steered on an intercept course, then revved up to top speed once it's in close. A torpedo like the Shkval can't close the distance, and that's assuming the enemy even knows where they're being shot from. Just because a Mark 48 suddenly goes active on your stern doesn't mean it was fired from there.

According to the wiki article, this was for intercepting incoming torpedoes. I suppose that could work, though again, the noise I'd imagine would be troublesome. It might mask for you a bit, but your attacker would know where this thing was shot from. Meanwhile, your own sonar is only going to hear this thing, meaning you've lost a solution on the guy shooting you, leaving him to set up again.

I highly suspect the reason we haven't seen an equivalent is because the tactical doctrine doesn't call for one. My armchair two-cents.
Filtering by partial string match on dimensions. It is equally slow on both of them.

For straightforward filters and aggregations, yeah, Clickhouse is faster. However I read a PR by the Druid team where they added a vector engine. If they release that, then the performance gap should be smaller or maybe in Druid’s favor depending on the dataset.

You are right about insertions up to a point.

If you consider data loads as insertions, with Druid I could scale my cluster elastically to speed them up. With Clickhouse I am bound by the query nodes.

Also, Druid can ingest data in real time using a special type of node that wasn’t part of the original distribution. I haven’t done real time data ingestion on Clickhouse. Hourly updates are good enough for my use case.
What would you do with the old text? Delete it?
soon it won't (at least, not on its own- in the wsl2 VM)
https://www.docker.com/blog/new-docker-desktop-wsl2-backend/
One of my main pain points in Windows is that the terminal app options are so crap compared to iterm2 or even the plain terminal app. The app itself is definitely a draw too
> And here’s why I don’t think the Sapir-Whorf hypothesis fully applies to programming languages. When we program we categorize the world in English (or Spanish, or any other natural language), and then we encode that into a program.

I certainly don't "categorize the world in English" before "encoding that into a program".

I've also met dozens of programmers over the years who found it easier to "show code" than to explain in English (or Spanish or any other "natural" language). I would be shocked to discover this is an isolated phenomenon.

In Iverson's book "A Programming Language" (1962) says in §1.1:

Ordinary English lacks both precision and conciseness. The widely used Goldstine-Von Neumann (1947) flowcharting provides the conciseness
necessary to an over-all view of the process. only at the cost of suppressing essential detail. The so-called pseudo-English used as a basis for certain automatic programming systems suffers from the same defect. Moreover, the potential mnemonic advantage in substituting familiar English words and phrases for less familiar but more compact mathematical symbols fails to materialize because of the obvious but unwonted precision required in their use.

So I'm not sure Iverson would agree either.

Maybe just start with something simple like: Why is it important to classify programming as "not a language"?

I had a hard time understanding what the author might think the answer to this question is. The only thing that jumps out at me is this:

> … after seeing what happened with Scala and SBT, where sometimes the project build description ends up written directly in Scala, I’m not sure having one language that encompasses all is something I’d want …

> Is it worth to expose users to an alien configuration format, just so the developers of the project can program in just one language?

If you seek a purely utilitarian answer; an answer to what makes the software best perform the intended function, then yes it is worth it: There will not be bugs in the code you do not write.

However getting people to use your software (i.e. "Sales") means making the software accessible to other peoples expectations and that's a social exercise.

This is a business decision with simple economic drivers, and not a technical one. Some languages are simply better at sales than others; English is the most widely-spoken language in the world, but that doesn't mean English poetry is superior to Chinese poetry.
I have been using multipass very successfully the past few weeks. It's a full fat VM and has an experience very similar to that of WSL. https://multipass.run/
> In your last sentence, you compare future quantum computers to “today’s” non-quantum computers, which might be a false dichotomy.

Ah, good point.

Though I was more thinking of Shor's algorithm and Grover's algorithm that tells us the theoretical expected performance that could be achieved with quantum computers. Normally these are described as showing the speedup provided by a possible quantum computer (in relation to non-quantum computers).

So, when reading the Wolfram Model paper I cited, I read the statement regarding quantum computers as dismissing the possibility of achieving qantum computers capable of realising Shor's and Grover's.

But one could of course read it in a flip-side way, that there are algorithms out there to be discovered that achieves the same lower bound complexities on non-quantum machines.

Considering that the Wolfram Model is all about graphs and cellular automata, the statement should probably be considered not based on a RAM complexity model, but something like PRAM that considers parallelism.
I should write a shell frontend to gcc to warn if I do this…
Right, it's not exactly gaslighting. Rather, it's a fucking strawman made in bad faith.

The stakes are not "my stocks". The stakes are civil society, which as you may or may not know, can't exist for long without a functioning economy.
War.
War never changes.

https://youtube.com/watch?v=C2Pt-LnQ2po
> don't we need a centralized touchstone for these kinds of crises?

This is like saying the governors should be ceding control to the federal administration.
This was the tongue in cheek implication of my comment. I’m a Linux user. But yeah Wine actually already does what I want. :)
I will the moment you give me a mac with a seven row keyboard and a trackpoint.
I’ve been in the opposite boat for a while. I need virtual box so can’t use docker on windows but it seems that has changed since February so will give that a try
> Tools like black and poetry are nice, but are not part of the standard library.

If black does non-PEP 8 formatting, as the article says, then I would not expect it to be in the standard library, since PEP 8 formatting is the Python standard.

> the language itself is increasingly baroque and complicated

I don't find current Python 3 any more baroque or complicated than Python 2.7. In fact I have plenty of Python code that runs just fine, unmodified, under both interpreters. And I have plenty of other Python code that only needs from __future__ import print_function to run unmodified under both interpreters.

That's not to say I think there are no issues with current Python 3; just that I wouldn't describe those issues as "the language is increasingly baroque and complicated". See further comments below.

> Type-annotated, asyncio-enabled Python hardly resembles the language I fell in love with back in 2006.

You don't have to use these features if you don't want or need them. Nobody uses 100% of any language's features, and the subset that is used can be very different from person to person. I don't see that as a problem.

I did see the way the Python 3 transition was handled as a big problem, but that's water under the bridge now and the issues that gave many people headaches during the transition were pretty much resolved by Python 3.3.

The two big problems I see with current Python 3 are memory usage and the GIL. Python 3 objects take more memory than Python 2 objects did; for programs that create a lot of objects that can be an issue. (To be fair, many such programs are numerical simulations that can take advantage of the many optimizations in the NumPy and SciPy libraries.) There seems to be work in progress on supporting multiple interpreters running in the same Python process, which would fix the GIL issue, but it's too soon to see if that will really address the issues surrounding the GIL.
Very nice work! How did you narrow down your search to extract the laptop model specifically, among what must be thousands of 3D assets.
I'd love a breakdown of your process!
This does not surprise me at all.

I worked at a company once where the ceo was enamored by Masayoshi (who had also invested in our company). He asked me to help him with a presentation he was going to give to masayoshi as part of some kind of competition to be his protege or something.

I remember thinking the whole thing was strange: why was the CEO spending his and my time on a personal competition instead of growing the company, but what did I know, it was literally my first few months in the tech industry. So I did my duty, got a thanks, and the CEO left the company a month later to parts unknown.

Him and masayoshi were hype men, and the latter is obviously good at it. But now we will see if he is great - it’s one thing to hype with unknown track record, it’s another thing to hype when you have some large losses.
> He has several tweets that contributed to 25K deaths..

Cut his funding!
But does it justify to cut their funds?

They published a status of non-knowledge, easily misinterpreted. And sometimes later they published more alarmist statuses. It is quite normal to be wrong sometimes, even in science-related establishments.
> The author is making things overly complicated, but it's all self-inflicted.

My reaction exactly.
When I tried VSCode a year ago, I found it to have an input lag, compared to sublime.

Given your comments, I just installed it right now to try it out again. I like the built in terminal & git integration. Code search performance is excellent (w/ code hosted in WSL) due to this new client/server model... and there was no input lag in the editing window.

The only lag I noticed was in CTRL-P selector, but that's a small compromise given the client/server model solves the real time waster.

I think I'm going to try it out over the next few weeks :)
If I was in a knife fight, and my buddy showed up and just hit the guy I was fighting with a SSME, I would be totally impressed and also grateful.
Live CD is ~65MB (the website says the core fits on a 1.44MB floppy). It boots in less than one second (VirtualBox using defaults for "unknown OS"). Mouse and keyboard are working but are not fit for real use.

"If you really want guest addons for KolibriOS to be available, you may offer your help in porting them" http://wiki.kolibrios.org/wiki/Setting_up_VirtualBox
> Nobody uses 100% of any language's features

There are massive differences between languages, though. I think I might use close to 70% of Objective-C's or Java's features regularly, while I can't even hope to use 50% of C++'s.
I always wonder where are all these spoiled kids who have no deadlines and bike-shed ad-infinitum about the spaces around every single token live :-(
> The Chinese populace aren't stupid, and China doesn't have the level of totalitarian control that North Korea has. Flat out denying it happened is a great way to weaken how much trust the population have in the state media.

They're a mix of conditioned (brain washed) and terrified at being disspeared by the CCP.

Make no mistake this is a CCP caused pandemic, and is aptly called the CCP-Virus in Hong Kong: I fear anything short of having the CCP on trial for Crimes Against Humanity in the The International Court of Justice will only exacerbate the problem and will lead to further pandemics, as they never learned from SARS.

They censored the Physician calling out to the World how grave this disease was, and he subsequently died. Citizen Journalists have since gone missing that exposed the decrypted state the hospitals were in and the amount of dead were piling up and left aside.
Things to Consider When Writing Your Next Blog Post
> It was bikeshedding at its worst

It's ironic that discussions about formatting are taking up so much mindshare in the python community. For years all you'd hear was that whitespace significance was a sign of the lowliness of python. Meanwhile, tons of people were ignoring the bikeshedding and getting things done. Now it's one of the most widely used languages in existence.

The kinds of people that are focused on issues like formatting never seem to be focused on the things that actually matter - being productive and being able to get things done. That's what has always mattered about python, and what has always made it excellent.
Ah, Falcon 4.0, I miss you so much. This "beaming" maneuver was in the manual, along with all kinds of other goodies. Most fun a 13 year old could have.
The PEP8 style guide even says don’t use it if

“When applying the guideline would make the code less readable, even for someone who is used to reading code that follows this PEP.”

https://www.python.org/dev/peps/pep-0008/
When would COVID19 be over from a data science perspective?
Implementing AWS Lambda in Node.js
Actually, latter versions of the Mark 48 will do this, running at variable speed. Slow launch, creep towards the target, and dogleg even, then run up to 50+ knots once it's close enough to be heard. With wire guidance, the sub could essentially drive the torpedo to where they wanted it before violent speed and maneuvering would likely cut the wires.

This was depicted somewhat famously in the book Red Storm Rising. By all accounts it was accurate.

Shkval is a really special case and not the supertorpedo some made it out to be. It's a countermeasure really, and it's range is far too short to use against other submarines. It's a last resort weapon, when someone's already found you.

IDAS seems really fascinating to me though, like the "Stinger SAM mast" concepts I'd sometimes hear about. IDAS seems more practical and safe to me though. Coming up to periscope depth to take a potshot at a helo sounds like a risky maneuver to me. IDAS would give better options.
> Type-annotated, asyncio-enabled Python hardly resembles the easy-to-understand language I fell in love with back in 2006.

true.

i am all for types in general and for types annotations in python. but i have seen some heavily type-annotated python code lately and i don't think that's where we want to be.

we are starting to look like a heavily templatized cpp code.
I was in a hurry and forgot to say that they differ from real news reporting in the way that porn differs from a real relationship. Of course, the op-ed/opinion columns in traditional news media are also mostly emotional porn; but the point is that opionating is cheap and while doing it well and entertainingly does require some research and planning each day, when you get down to it it's just a performance rather than painstaking and often slow production of factual data.
> You don't have to use these features if you don't want or need them. Nobody uses 100% of any language's features, and the subset that is used can be very different from person to person. I don't see that as a problem.

The problem is that other people might use those features and you also might have to read the code created by those people.
Our economy has fallen off a cliff, and we have no view of bottom yet. What exactly do you expect anyone to be able to quantify at this early stage?
integration of all the different parts on board in a single base: WIFI with ESP8266 WiFi, brushless motors, 4x ESC last generation BLHeli32 with telemetry and DSHOOT up to 2400 -- FlighControl -- IMU -- baro -- compass -- power system with 1 easily swappable Li-Ion 18650 for maximum flight time -- rangeFinder for accurate low height navigation 0-3m -- sdcard slot for Log -- connector for common RC radio and telemetry + connector for all the external add-ons like GPS, indoor positioning system, optical flow, 8 horizontal rangefinder for collision advoiance,... All these hw connected with the Ardupilot features. Furthermore, for small copter its very hard to have good flight time, ArduBee try to have very good flight time, safe and ready for makers to develop, supported by one of the best Open Source project for drone, Ardupilot.
It has been developed to be used safely for urban swarm robotics application development, education, creativity!

https://ardupilot.org/copter/

ESP8266 with Ardupilot (telemetry and control)
https://ardupilot.org/copter/docs/common-esp8266-telemetry.h...

BLHeli_32 ESC Telemetryhttps://ardupilot.org/copter/docs/common-dshot-blheli32-tele...
> I can see how GitHub wouldn't want a public repo to have objectionable words

I can't. Does GitHub really have nothing better to do than to play nanny cop because I used a naughty word in my code? Are brainfuck interpreters now off-limits? How about drivers for teledildonics hardware? Or libraries specifically for detecting and filtering swear words? Or maybe I just want to vent a bit in a comment every once in awhile because of some annoyance with the language or target platform or problem to be solved?

Fuck that and the horse it rode in on. We're all adults here (well, or possibly teenagers, but let's face it: they've probably already heard much worse at school).

Not that this seems like the real reason why SS13 got nuked anyway; if GitHub really has some kind of anti-profanity rule, they're doing a real bang-up job of consistently enforcing it: https://github.com/search?q=shit / https://github.com/search?q=piss / https://github.com/search?q=fuck / https://github.com/search?q=cunt / https://github.com/search?q=cocksucker / https://github.com/search?q=motherfucker / https://github.com/search?q=tits
The author starts by criticising a bike-shedding mentality and then goes on to make bike-shedding arguments. They complain about the non-pep8 compliance, show what pep8 would look like and then argue that there's a better way..

As another commenter pointed out: This is all self-inflicted.

Personally, I don't care how things are formatted, I just want it to be consistent.
Masayoshi has actually had a known track-record since about 2000 or so. He's been the man who's lost the most money in history since about the same. Seventy-billion dollars!
Interesting that the comments here aren't more critical of the decision.

Does the idea of improving the WHO by withholding money come from some kind of shared "starving the beast" logic or is it just a revenge kind of reflex that doesn't even have any positive expected outcome?

Eg the travel restrictions position[1], taken as an example in the article, appears to have been be defensible and a mainstream position in the field. It may turn out to be wrong or not in hindsight, like many things in this pandemic, but it's no reason to try to harm the organisation.

[1]
"Evidence shows that restricting the movement of people and goods during public health emergencies is ineffective in most situations" in February, https://www.who.int/news-room/articles-detail/updated-who-re...
It can be easier to extend & customize[0] though.

I went with IdentityServer4 on a recent project over Keycloak and Gluu[1] for that reason and because it was in the same stack as the rest of our ecosystem.

[0] See comment from this thread https://news.ycombinator.com/item?id=22871756

[1] https://www.gluu.org/
In some other countries they do, especially in Europe.
I freelance in both python and C#, python used to get the job done in 200 lines vs C# at 500, now its 300|300 and the C# is easier to read
There's a fantastic book, "Clashes" by Marshall Michell all about this subject, which I can highly recommend. All about the air war in Vietnam.

https://www.amazon.com/Clashes-Combat-North-Vietnam-1965-197...
My theory is : no matter the lockdown, the virus will always be there (it will come back) and people who would die from it will die from it anyway, but due to the lockdown they just won't die all at same time. If they won't die from covid19, they will die from another flu or another complication.

The lockdown only buys them time so a vaccine can be developed specifically for covid19

How much economy (including lives that depend on the economy) are we willing to sacrifice to save 0.001% of the world population.... ?

I'm sorry but all of this doesn't make sense in regards to the "effort" made to save elderlies in the past.
Airbnb Raises Another $1B in Debt
It shrinks the VHD automatically??

And yes the \\wsl$ is the 9P server I just tried to explain is incredibly slow compared to normal files on WSL1. I haven't tried WSL2 yet but I don't expect going through a VM would be faster.
The Logistic Map
I think the most depressing thing about all of these is how transparent the con should have been.
Honestly, this is one of the things I really appreciate about the development workflow at $dayjob. Our Python build process is fairly custom for what amounts to historical reasons, but when you create a new Python project, you get automated builds and tests on all the OSes you care about (through our central build and test farm), a way of declaring dependencies (that has nothing to do with pipenv/poetry/etc., but whatever), flake8 enabled by default easy toggles for mypy and black if you want them, a standard way of doing code reviews, a standard way of doing releases, etc. - simply because it's possible to assume shared infrastructure and shared defaults.

When you're writing open-source code, you don't have any shared infrastructure or defaults to assume, so you have to find some infrastructure (e.g. GitHub + Travis) and you have to basically include all the infrastructure configuration in your project, possibly through adding a bunch of dev-dependencies that set things up the way you want. It'd be interesting to think about how to abstract this further so you don't have to think about that many things.

Some possible inspirations:

- https://travis.debian.net/ - if you have a Debian package on GitHub, and you want automated tests, you just grab the .travis.yml file from here and a script written by someone else will set up builds and tests in Docker containers. It does rely on Debian having a standardized way of specifying build rules, dependencies, and tests and a standardized layout of packages, though. But most Python packages have a pretty standard layout, too, and you can imagine having things like isort/flake8/nose/etc. be installed only in CI and not explicitly listed in your code.

- Rust, I think, makes this a little easier because there's a high-quality packaging system, test runner, formatter, and doc generator all in the standard Rust tools. While Rust-the-language has a standard library that's much emptier than, say, Python's, rustc comes with way more developer tools than Python does. That means that you don't need to install custom tools to handle most of this because it's assumed that people are using the standard ones. (This does, of course, rely on the tools actually being high-quality, and as a young language, Rust has an unfair advantage in watching Python and so many other languages try to figure out what works well and what doesn't. You'd have an easier time in Python if you stuck to distutils and easy_install, but on the other hand, you'd have to use distutils and easy_install.)