> I wonder if the ergonomics or geometry of a bicycle could be modified to better protect a rider’s neck.
There has been a huge trend in this direction in recent years! For example in 2000 the head tube angle on a typical “trail bike” was something like 71 degrees, but today it’s more like 65 degrees, meaning the front wheel is a lot farther out in front of you. Bikes have also just gotten longer, especially in the front end which adds to this effect. This all means that (assuming you don’t ride more difficult terrain to compensate) it’s way harder to crash “over the bars” on a modern mountain bike than in the past.
There are sections of trail that I would almost always OTB (over the bars) on when attempted on my old 1998 hard tail. After finally upgrading in 2018, I almost never go OTB because of the longer and slacker geometry.
One ride on a double black rated tech trail nearby, the air shaft in my fork seized up so I lost all front compression. Even without front suspension, I was able to complete the ride and even keep up with my group, my arms were just toast after that. Modern bikes are just that capable based upon geometry alone.
That said, I now ride at significantly higher speeds and ride much harder terrain. But even still, my crashes are different and more to the side than directly over the bars.
The more downhill oriented a mountain bike is, the more it resembles a dirtbike — more suspension travel (up to around 220mm, where the suspension starts to work against you and makes the bike too mushy for something that light and human powered) , higher and wider handlebars and more space above the seat (nowadays the seats actually move out of the way and come back when needed, operated by a lever on the handlebars).
I'd say that most honest to god OTB accidents happen on slower, gnarly, downhill stuff, where it's easy for the (still relatively light) mountain bike to get stuck and unable to roll over an obstacle in time (before the rider arrives), or for the obstacle to slap your steering to the side, which again suddenly stops the bike.
Dirtbikes are much heavier compared to bikes and the weight of the rider, and you generally ride them a bit faster and not necessarily downhill.
Nothing is published yet. Whatever gecko build might be there might be whithering away on the vine, I don't believe Mozilla cares for supporting it just for the EU.
Interestingly for me on iOS, that instagram link just takes me to the main feed in the app. For anyone else getting this, you have to tap the instagram logo on the top left, then select “following” from there.
This threw me off too. Sure Illustrator is probably a better tool for this than pen and paper, but it seems like far from the best choice. I guess that just makes this all the more impressive.
Wow, I remember noticing this same thing back when I was exploring a lot of different artists. On streaming sites often a bands top songs will be ones that came out recently, or a collab they did with a more popular band, or a track that for whatever reason appealed to a wider audience. But those aren’t what you really want to hear if you’re trying to decide if you like that band. My strategy would instead be to go find either the bands earliest studio album or the oldest album that is well represented in their top tracks and skip to track 7. I never thought about why, but it definitely works.
I’d be curious to hear more about how you’re using F#? I’ve previously used Python for scripting, but just started developing for a company pretty deeply entrenched in .NET. Currently they’re migrating a lot from VB to C#, but I’ve missed having a handy scripting language like Python for small tools or test applications. Do you think F# could fill that roll?
Powershell is probably best fit for that role. You have to learn a new scripting language but since it runs on .Net you can actually bring in .Net Classes if you need a little more power.
It should be able to! F# has "gradual typing" and full type inference which means you often do not need to specify the types at all, and it also happens to be whitespace-sensitive language much like Python is. Both of these aspects should make it feel quite familiar while also giving you full advantages of static typing.
One thing to note is I find `dotnet fsi {some script name}.fsx` taking more time to start than ideal - up to 800ms is just too much, normal .NET applications usually start in a fraction of this.
I recently posted a submission here for "FSharpPacker" written by my friend that lets you compile F# scripts to standalone applications (either runtime-dependent, self-contained or fully native binaries, much like Go), it also has some comments on getting the best mileage out of it: https://news.ycombinator.com/item?id=42304835
Probably the best feature that also comes with scripting (both C# and F#) is "inline" nuget references e.g. #r "nuget: FSharp.Control.TaskSeq" which will automatically pull the dependency from nuget without ever dealing with manually installing it or tinkering with build system in any other way.
https://github.com/dotnet-script/dotnet-script (C# is also a quite productive language for scripting and small programs because of top-level statements, record types, pattern matching and many other functional features though perhaps not as strongly represented as in F#, it's just very unfortunately abused in enterprise world, with teams often going out of their way to make the code far more bloated than necessary, against the language design intentions)
F# is a leap if it's your first functional / ML style language (but worthwhile). Modern C# is good for small tools and scripting, there is the dotnet-script tool for running single .csx files
Edit: The more I read on this the more doubtful I’m becoming that this was actually produced at scale. If anyone has a better source I’d love to see it!
> The process required at least 60 kilograms of coal per kilogram of synthetic butter.[23] That industrial process was discontinued after WWII due to its inefficiency.
Something of note that creators like that of Mothbox might find interesting (if they didn't already know), Haikubox was awarded about $1m from the NSF: SBIR Phase II: Building a Nature Monitoring Network for Birds [0]. More about the awarding NSF "directorate" here [1].
I was using it today, and any day when there are birds around. It correctly identifies birds you can barely hear. It's become as useful as binoculars to me. A great free app.
Honest question: did the crypto hype cycles “lay the foundation for something bigger”?
I suppose there is an argument to be made that it pushed Nvidia to ramp up GPU production and lean into the compute market rather than gaming. Maybe gave the world some extra experience with hosting large GPU farms that are needed for AI training.
I don’t think I’m sold on either of those, but would be curious to see others discussion.
There has been a huge trend in this direction in recent years! For example in 2000 the head tube angle on a typical “trail bike” was something like 71 degrees, but today it’s more like 65 degrees, meaning the front wheel is a lot farther out in front of you. Bikes have also just gotten longer, especially in the front end which adds to this effect. This all means that (assuming you don’t ride more difficult terrain to compensate) it’s way harder to crash “over the bars” on a modern mountain bike than in the past.