bouchard

If you wanna share with friends and family; it's way more accessible than setting up access to a VPN/tailscale/etc.

I've been running an older client version (last one before the new UI) on both Android (mobile) and Fire TV Stick 4K. Hasn't been too much of an issue to setup for friends, you just have to make sure to disable auto-updates.

Even on desktop panning is remarkably slow.

The README is in the header file (picophysics.h)

The repository hasn't been made public yet it seems.

What field are you in that you'd actually wait two years, rather than retract your submission and go somewhere else?

Their "technical validation (CFD)" document looks like AI slop...

Rejections from journals are not uncommon and sometimes it's for somewhat questionable reasons.

Uploading the manuscript to a preprint server and/or submitting to another journal, which Adamala is doing/planning to do, is the normal response.

Sending it to journalists beforehand is what I consider an overreaction.

> “It’s an unusual way of doing things,” says Kerstin Göpfrich, a synthetic biologist at Heidelberg University.

That's being kind; it's a complete overreaction, simply put.

> Yes 1-based indexing is a mistake. It leads to significantly less elegant code - especially for generic code - and is no harder to understand than 1-based indexing for people capable of programming.

Some would argue that 0-based indexing is significantly less elegant for numerical/scientific code, but that depends on whether they come from a MATLAB/Fortran or Python/C(++) background.

A decision was made to target the MATLAB/Fortran (and unhappy? Python/C++) crowd first, thus the choice of 1-based indexing and column-major order, but at the end of the day it's a matter of personal preference.

0-based indexing would have made it easier to reach a larger audience, however.

> and is no harder to understand than 1-based indexing for people capable of programming.

The same could be said the other way around ;-)

The approach could be helpful for searching though large 3D model libraries like GrabCAD for some visual placeholder part by just describing it.

The generality of the part descriptions made me chuckle.

> A bevel gear with a circular base and a series of angular, tapered teeth extending radially outward. The teeth are uniformly distributed around the circumference, allowing for meshing at an angle with another gear. The gear's face includes a set of holes, varying in size and symmetrically arranged around the central bore, likely for weight reduction or mounting purposes. The central opening likely acts as an axle or shaft attachment point. The design facilitates the transmission of rotational motion between intersecting shafts, typically at a 90-degree angle.

This is a about Groq, not Grok (Musk's chatbot).

Comments on the claims made by Penn State's PR department in "Student refines 100-year-old math problem, expanding wind energy possibilities"

> https://news.ycombinator.com/item?id=43162544

Meh, depends what's the goal. Exceeding predicted performance is not a screw up, it's just providing a minimum guaranteed performance aka playing it safe (under promise, over deliver).

Also, we don't know by how much the most optimistic predicions were exceeded.

Makes for nice marketing ;)

Depends if you make overly conservative assumptions in your modeling...

Using greek symbols as public-facing function arguments, etc. is definitely not recommended, and not that common (at least in my experience).

It's best used for internal calculations where the symbols better match the actual math, and makes it easier to compare with the original reference.

Never thought I'd see the name LimeWire again, wow

Looking at interview footage of Stockton Rush, it seems he really wanted to be a disruptor and accomplish something which everyone else (i.e., experts) deemed impossible. He thought he could do what SpaceX did for space, but for underwater exploration.

The Netflix documentary has some extra interviews with employees, clients, etc. which are interesting. (1hr 51min runtime though)

"nmi" is also common

No, it's the standard procedure for F35 parts supplied to allied countries. Which is why it's a bit of an issue in the current political context.

But a U.S. Government Accountability Office report in 2023 revealed the rules governing the F-35 parts. The report noted that the parts are the property of the U.S. government until they are installed on another nation’s aircraft.

Understanding Aerodynamics: Arguing from the Real Physics by Doug McLean, a former aerodynamics Technical Fellow at Boeing Commercial Airplanes.

Not really, they're a nice first step though, or if you require something "good enough".

Which can be a bit of a challenge when trying to land, especially for aerodynamically efficient aircraft.

FWIW, I use numba's (experimental) jitclass pretty successfully in my projects.

(Actually a monkey-patched version to be able to set njit arguments)

> (good pointers on speeding up the Python code beyond Numpy listed but not tried or benchmarked)

Damn, it would have been a nice benchmark if they did do a comparison against numba/cython.

From GitHub:

> Some timings for the Shed Skin 'sieve' example (n=100000000) and several Python implementations/optimizers:

  cpython 3.10.6:     13.4 seconds
  cpython 3.11.0:     11.4
  nuitka 0.6.16:      11.4
  pypy 3.9.12:        5.8
  numba 0.56.4:       2.5
  shedskin (master):  1.9

> Note that Numba defaults to int64 as integer type, while Shed Skin defaults to int32. Performance is practically equal when using shedskin --long.

GP is talking about the current homepage which shows the following text over a colored background:

> Since 2001, OGRE has grown to become one of the most popular open-source graphics rendering engines, and has been used in a large number of production projects, in such diverse areas as games, simulators, educational software, interactive art, scientific visualisation, and others.

You can use mamba's much faster solver directly with conda.

  conda install -n base conda-libmamba-solver
  conda config --set solver libmamba